You forgot to chomp. If, as 1st line in a while block, there's chomp $line;, then you are OK. +You'd better die $^E instead of just die.

OTOH (digressing, I know), if instead of code after the "#1" line you do

use Win32::LongPath;
testL 'e', $UserDataReadFromFile 
    or mkdirL $UserDataReadFromFile 
    or die $^E;

[download]

there's no need in chomping, previously. It may look as a nice free bonus, but it's misleading. See 5 lines, comment says "strip off volume", but effectively it strips newline too, because a dot doesn't match newline there. There can be ways to bypass that fragment, therefore unaware user will be bitten. Thus, always chomp.

In reply to Re: Utf-8 path from file by vr
in thread Utf-8 path from file by Anonymous Monk

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.