Randy Kobes wrote:

>On Thu, 20 May 2004, Geoffrey Young wrote:
>
>  
>
>>I find it strange, though, that File::Spec doesn't take
>>care of this.  after all, isn't File::Spec supposed to be
>>used for exactly this reason?  if I need to use
>>Apache::TestUtil::t_catfile for tests in cross-platform
>>CPAN modules then what's the point of File::Spec::catfile?
>>
>>not to increase your workload, but maybe File::Spec should
>>be patched to account for the win32 differences for the
>>greater good, rather than working around what appears to
>>me to be a bug.
>>    
>>
>
>I asked Ken Williams about this, and he replied:
>
>[...]
>File::Spec is supposed to only deal with file
>specifications.  In general it shouldn't ever touch the
>filesystem itself.  So canonpath()  shouldn't ask the OS to
>translate a path to long form - that's the job of something
>else, essentially a layer on top of File::Spec or something.
>
>A similar issue has been well hashed-out on Unix: should
>canonpath()  turn "foo/../bar" into just "bar".  It's been
>ruled that it should *not*, because if 'foo' is a symbolic
>link then "foo/../bar" may refer to a different place than
>"bar" does.
>
Cwd::realpath() does that sort of thing, so perhaps it is that which 
needs patching to sort out Win32 short/long names then?

- Steve



------------------------------------------------
Radan Computational Ltd.

The information contained in this message and any files transmitted with it are 
confidential and intended for the addressee(s) only.  If you have received this 
message in error or there are any problems, please notify the sender immediately.  The 
unauthorized use, disclosure, copying or alteration of this message is strictly 
forbidden.  Note that any views or opinions presented in this email are solely those 
of the author and do not necessarily represent those of Radan Computational Ltd.  The 
recipient(s) of this message should check it and any attached files for viruses: Radan 
Computational will accept no liability for any damage caused by any virus transmitted 
by this email.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to