Hi, That is interesting .. and to me it makes the most sense to put path and file translation functionality in the File::Spec namespace ... because it keeps platform path/file related functionality under one "roof," which makes writing cross-platform scripts easier, and also because File::Spec is a standard part of the perl distribution.
Max On Wed, 13 Nov 2002 09:57:59 EST, David Boyce wrote: > Interesting. I didn't know that and it's an unfortunate design. However, > guess what? Here's the same hash from the version bundled with 5.8.0: > > my %module = (MacOS => 'Mac', > MSWin32 => 'Win32', > os2 => 'OS2', > VMS => 'VMS', > epoc => 'Epoc', > NetWare => 'Win32', # Yes, File::Spec::Win32 works on NetWare. > dos => 'OS2', # Yes, File::Spec::OS2 works on DJGPP. > cygwin => 'Cygwin'); > > And indeed there's now a File::Spec::Cygwin. All it does as of 5.8.0 is > override the 'canonpath' and 'file_name_is_absolute' methods. I can't > remember what problem the OP was trying to solve but I suspect if what's > there now doesn't satisfy him he can add the desired functionality without > much trouble. > > -dsb
