Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid

Re: Why cant regex parse this string?

by moritz (Cardinal)
on Jul 12, 2012 at 13:57 UTC ( #981404=note: print w/replies, xml ) Need Help??

in reply to Why cant regex parse this string?

$filename is a string, but if you use it in a regex, it is interpreted as a regex. So all sorts of characters (like parenthesis, for example) have a special meaning. To prevent that, use s/\Q$filename\E//. See perlre for more information.

But, you are already using the URI module, why do you do all those path manipulations yourself? $url->path gives you the path, which is the URL without schema or domain name, so you don't have to manually remove that from the original URL. Or path_segments, which gives you the different parts of the path delimited by slashes:

# untested: my @path_chunks = $url->path_segments; pop @path_chunks; # remove the last one, which is the file name my $dir = $song{dir} = join '/', @path_chunks;

(Updated to use $uri->path_segments, daxim++, and s/shift/pop/, johngg++)

Replies are listed 'Best First'.
Re^2: Why cant regex parse this string?
by jayto (Acolyte) on Jul 12, 2012 at 14:08 UTC
    Thank you, that is what I suspected the problem was, but i wasn't sure how to fix it. I also used URI->path() instead of those lines of regex that i had before. Thanks again!

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://981404]
NodeReaper sorts his collection of toe tags, by difficulty

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (4)
As of 2017-12-12 07:08 GMT
Find Nodes?
    Voting Booth?
    What programming language do you hate the most?

    Results (327 votes). Check out past polls.