in reply to Re: "But I'm never going to..."
in thread "But I'm never going to..."

ActiveState perl already understands that slashes and backslashes are equivalent for most modules. This is not to say everything in CPAN will be friendly, but in all of my Windows scripts I just use "/" like normal -- and I haven't had any problems unless I am sending something to the shell.

In the rare cases where I had to do this, a simple fix_path function is usually sufficient to insert (which turns slashes into backslashes). I *do* need to look at File::Spec and others in these cases, but in general, conciseness is important to me when it can be done without causing problems. And when only dealing with Windows, Linux, and basic Unix systems, this is good enough for me. I'll capitulate when I have to port to something more obscure, I'm sure.

Replies are listed 'Best First'.
Re: Re: Re: "But I'm never going to..."
by Steve_p (Priest) on Apr 11, 2004 at 02:01 UTC

    I've never had a problem with ActiveState not translating between "/" and "\" in a path. The main problem I've had is with the tests, where a path in a string is "t/foo/bar" and Windows returns "t\foo\bar". This is enough to cause a test and CPAN install to fail.