Today it behaves differently. Now it is only allowing me to create one directory with no subdirectories under it. All of the following work:
 $diss = "\\bleen\\";
mkdir $diss,0777 or die "can't make dir: $!";

$diss = "\\bleen\\";
mkdir "$diss",0777 or die "can't make dir: $!";

$diss = "\\bleen\\";
mkdir ($diss,0777) or die "can't make dir: $!";

$diss = "\\bleen\\";
mkdir ("$diss",0777) or die "can't make dir: $!";

[download]
If I extend my directory structure, it fails. For example 
$diss = "\\bleen\\duh\\";

[download]
fails.
I know that there is more than one way to do it. I usually go the least terse route. I could test for the directory and create it if it doesn't exist. Then I could change into the directory and test for the sub directory and create it if it doesn't exist, but that seems like the long way home to me.

In reply to Re: Re: mkdir on NT by fmogavero
in thread mkdir on NT by fmogavero

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.