"Andrew M. Langmead" wrote: > That isn't part of Activestate Perl, but rather part of Microsoft's > file system API itself. It has always (as far back as MS-DOS 2.0) > allowed either forward or backslashes as path separators. It is only > tools that use those OS calls (like COMMAND.COM) that gets confused.)
And the dialog boxes > Most versions of perl just pass things directly to fopen() unchanged. And likewise, all the modern tools accept them fine. The only problem is if you have to reference something on a different drive -- P:/whereever/whatever/foo.bar works, but the Perl may choke if it's not expecting it. Luckily, URLishness means foo://etc/foo.bar is now more expected, so getting less annoying. bill _______________________________________________ Boston-pm mailing list [EMAIL PROTECTED] http://mail.pm.org/mailman/listinfo/boston-pm
