On this occasion, it appears that the problem is internal to Perl--with caveats.

The problem occurs in these two lines from win32\win32.c (line numbers are approximate (5.8.4) because I've added debug code): 

1222:         pwbuffer = PerlDir_mapW(wbuffer);
...
1228:         path = PerlDir_mapA(path);

[download]

Prior to these to lines the vars; path / wbuffer contain the bad paths being tested ( ' ', ' . . ' etc. ), but after they contain the fully expanded current working directory. They should not.

So, the problem is in the routines PerlDir_mapW() / PerlDir_mapA(). The stat being returned for non-existant directory paths is that of the current working directory.

But there, my trail grows cold. These functions are not functions, but #defines.

One path through the #defines in iperlsys.h has these resolved to: 

#ifdef WIN32
#define PerlDir_mapA(dir)        dir
#define PerlDir_mapW(dir)        dir
#endif

[download]

But that can't be right because then they would be unchanged and the problem wouldn't occur.

The other branch of the #if defined(PERL_IMPLICIT_SYS) in iperlsys.h resolves them to entries in a vtable. 

#ifdef WIN32
#define PerlDir_mapA(dir)                    \
    (*PL_Dir->pMapPathA)(PL_Dir, (dir))
#define PerlDir_mapW(dir)                    \
    (*PL_Dir->pMapPathW)(PL_Dir, (dir))
#endif

[download]

but search high'n'low, I cannot find out where these vtable entries are filled in?

It appears to be related to PL_curinterp and embedvar.h, but I tracked it back through about 6 levels of indirection before getting completely lost. It will take someone much cleverer than me to resolve this further.

Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
"Memory, processor, disk in that order on the hardware side. Algorithm, algoritm, algorithm on the code side." - tachyon

In reply to Re^3: -e " " returns true by BrowserUk
in thread -e " " returns true by PerlingTheUK

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.