BTW, my Directory::Scratch module is meant to solve this problem. At
the top of your program you:
use Directory::Scratch "YourOS"
and all path names passed to the module are interpreted as though
they're from YourOS, even when running on some other OS. This means
that you can use UNIX path names in your tests, and they'll work
everywhere Path::Class does. (Of course, you can use Win32/VMS/MacOS
paths, also; but UNIX is the default.)
The version of D::S on CPAN right now is kind of embarrassing (got a few
patches and applied them even though I felt uneasy about them), but I'll
have a fixed version up tonight.
So don't try the module yet -- I'll send another note to the list when
I'm happy with it :)
Regards,
Jonathan Rockway
(Disclaimer: nothing is broken in the current version, but it does
assume that you're using your native OS's paths. So if you don't care
about cross-platform usability, go ahead and use it now. In addition,
the tests are kind of "icky", as are some of the features. YMMV. :)
A. Pagaltzis wrote:
> * David Golden <[EMAIL PROTECTED]> [2006-09-18 12:30]:
>> Many of the test failures can be attributed to:
>>
>> * non-portable path expectations
>
> Btw, is there a chance of Path::Class becoming core?
>
> It is *so* *much* better than File::Find, File::Basename,
> File::Spec and the rest of the entourage it’s not even funny. And
> it’s also sane, as opposed to IO::All.
>
> Regards,
