Windows paths in glob

OK, so there's a well-known difficulty with handling Windows-style paths in glob: it doesn't
like backslashes, nor does it like spaces. One solution to that is to use Unix-style paths:

glob('C:\Documents and Settings\*'); # Doesn't work
glob('C:/Documents\ and\ Settings/*'); # Works

Problem is, the rest of Perl's built-in file-handling functionality behaves the other way around.
For instance, with -d:

-d 'C:\Documents and Settings'; # Works
-d 'C:/Documents\ and\ Settings'; # Doesn't work

Question: is there any way to use the same path string with glob and with the rest of Perl,
without having to convert them back and forth?

.

Relevant Pages

  • Re: Windows paths in glob
    ... in glob: it doesn't like backslashes, ... solution to that is to use Unix-style paths: ... In the examples you gave, the versions with backslashes cannot work, the ... unless they escape something other than a backslash. ...
    (comp.lang.perl.misc)
  • Re: Windows paths in glob
    ... in glob: it doesn't like backslashes, ... solution to that is to use Unix-style paths: ... I don't have Windows to test here, but I recall that using either a ... In the examples you gave, the versions with backslashes cannot work, the ...
    (comp.lang.perl.misc)
  • Re: Windows paths in glob
    ... paths in glob: it doesn't like backslashes, ... One solution to that is to use Unix-style paths: ... perldoc File::DosGlob ...
    (comp.lang.perl.misc)
  • Re: Windows paths in glob
    ... paths in glob: it doesn't like backslashes, ... One solution to that is to use Unix-style paths: ...
    (comp.lang.perl.misc)
  • Re: Typeglobs, Anonymous Filehandles
    ... BC> isn't this regarded as a symbolic reference, but Perl under strict ... BC> 'refs' doesn't complain? ... Then where does the GLOB come from? ... access a perl i/o handle except through a glob. ...
    (comp.lang.perl.misc)