Guay jean-Sébastien wrote: > > > I agree with your basic solution, but since he will > > be doing his development in Windows, shouldn't that > > be 'file system neutral'? hence not using the unix > > separator "/" between the directory component and the filename > > component? > > In a move to simplify porting of scripts (and save the sanity of Windows > Perl coders), ActiveState made it so that the "/" path separator works on > Windows too, and is converted internally. We don't have to think about it. > And it's easier than trying to remember to escape backslashes, too. :-) > > So the solution proposed will work fine on Unix, Windows, MacOSX, etc. > > Just FYI.
It has nothing to do with what ActiveState did or didn't do. The DOS/Windows command interpreter (command.com/cmd.exe) uses '\' as the path separator however the operating system itself is able to use '/' as the path separator. John -- use Perl; program fulfillment -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
