Thank you,
tye, for the insight and advice.
I met this problem recently while working on the original version of
this script, from the module
Pod-Tree-1.06. Path strings containing
'\' were passed to the script as arguments by the user (me), and the script hit the error while doing the substitution
$dir =~ s/^$PodDir/$HTMLDir/o;
I did not understand the problem at the time, but I found that I could fix it by inserting
# fix up the Win32 paths
$PodDir =~ s( \\ )(/)gx;
$HTMLDir =~ s( \\ )(/)gx;
Now you explained the nature of the problem and showed two ways to make similar scripts more robust:
- Apply quotemeta or \Q\E to a user-supplied string before using it in a regex.
- File::Spec provides platform-independent operations on path strings, notably splitting, catenating and converting absolute paths to relative, and should be used in portable scripts.
Rudif
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.