This is more of an observation rather than answering your question but using alternative delimiters in your substitutions can make the code much easier to read. Also I find that it is easier to use the hex value for a backslash rather than the character itself, e.g. converting to Unix-style paths ...

johngg@aleatico:~$ perl -Mstrict -Mwarnings -E 'say q{};
my( $path ) = qw{ C:\Users\fred\file.txt };
say $path;
$path =~ s{\x5c}{/}g;
say $path;'

C:\Users\fred\file.txt
C:/Users/fred/file.txt
[download]

Going the other way, I would use a lookahead, the chr function and the e modifier in a substitution to do escaping.

johngg@aleatico:~$ perl -Mstrict -Mwarnings -E 'say q{};
my( $path ) = qw{ C:\Users\fred\file.txt };
say $path;
$path =~ s{(?=\x5c)}{ chr 92 }eg;
say $path;'

C:\Users\fred\file.txt
C:\\Users\\fred\\file.txt
[download]

It seems easier to my eyes. I hope this is helpful.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.