I was doing something like this on win32 (win2k), and I found that if you simply use forward slashes in single quotes, the code becomes easier to read, and DOS still understands it.Such as:

$dirname='c:/dir/textfile.txt'

I eventually wanted to convert the slashes to backslashes for logging (so that I could copy log output directly to a command prompt). I inserted this little bit into the end:
('/' to '\')

foreach (@files){ s/\//\\/g; }
conversely '\' to '/':
foreach (@files){ s/\\/\//g; }
and your answer('\' to '\\'):
foreach (@files){ s/\\/\\\\/g; }

I would still simply avoid this and use the forward slash if you can...

-ozzyosbourne


In reply to RE: Converting all occurrences of \ to \\ oddity by OzzyOsbourne
in thread Converting all occurrences of \ to \\ oddity by dmtelf

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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:
    & &amp;
    < &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.