On Tue, Apr 01, 2003 at 09:18:51AM -0800, Ranga Nathan wrote: > Greg: > I use both ActiveState Perl and on Linux. If you stick to the forward > slash (/), there is no problem. From my memory, I never needed to code > MicroSlash!
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.) Most versions of perl just pass things directly to fopen() unchanged. There are other operating systems with file path semantics much different than MS-DOS or Unix (the mac comes to mind.) that can't easily an unambiguously be converted into somethig that fits the Unix model. (In the MacOS, you can name a file "2003/04/01", and it will refer to a file in the current working directory.) I think that VMS Perl uses some DWIMishness to decide whether you mean Unix or VMS style paths, but I think the DWIMery is built into the C RTL. I have no idea of what some of the more obscure ports (IBM MVS) do. As someone else said, File::Spec can sweep it all under the carpet for you. -- If you want to be an astronaut, you need to know all the planets, because you wouldn't want to be surprised. -- Samantha Langmead, age 5 1/2 _______________________________________________ Boston-pm mailing list [EMAIL PROTECTED] http://mail.pm.org/mailman/listinfo/boston-pm
