J
J Krugman
Is something like
require '/path/to/some/Module.pm';
portable?
I could have sworn that there was a perlvar that contained the OS's
directory separator, but I can't find it, so either my memory is
playing me a trick, or this variable was eliminated at some point.
File::Spec is the generally accepted way to construct filenames
portably. But I have read in a couple of places that it is OK to
give Perl paths with the Unix directory separator like the one
above even in systems that don't use this separator. If this is
the case, then Perl must be doing the translation internally, which
would greatly diminish the utility of File::Spec, and make the
various OS-specific File::Spec::* modules all but useless.
What gives?
TIA!
jill
require '/path/to/some/Module.pm';
portable?
I could have sworn that there was a perlvar that contained the OS's
directory separator, but I can't find it, so either my memory is
playing me a trick, or this variable was eliminated at some point.
File::Spec is the generally accepted way to construct filenames
portably. But I have read in a couple of places that it is OK to
give Perl paths with the Unix directory separator like the one
above even in systems that don't use this separator. If this is
the case, then Perl must be doing the translation internally, which
would greatly diminish the utility of File::Spec, and make the
various OS-specific File::Spec::* modules all but useless.
What gives?
TIA!
jill