On Sat, Jul 09, 2005 at 08:14:47AM +0200, demerphq wrote:
The current working directory is not considered in canonpath(), period.
canonpath(../../foo) is ../../foo.
As I said before, the docs DONT specify what canonpath() is for very
well. All of this stuff is inferred or implied.
On Jul 8, 2005, at 4:07 PM, demerphq wrote:
Im not entirely sure what scenario I
should be testing here, but i beleive the problem you are thinking of
is due to symlinks to a directory? If so then the win32 equivelent
would be a junction I think and in that case yes, foo\..\bar == bar.
Could
On 7/9/05, Ken Williams [EMAIL PROTECTED] wrote:
On Jul 8, 2005, at 4:50 PM, yves orton via RT wrote:
Sorry, i guess I didnt express myself properly. You cant clean up a
relative path properly without knowing where it is relative to.
Consider the following path:
..\..\foo
If
On 7/9/05, Glenn Linderman [EMAIL PROTECTED] wrote:
On approximately 7/8/2005 2:07 PM, came the following characters from
the keyboard of demerphq:
On 7/8/05, Michael G Schwern [EMAIL PROTECTED] wrote:
On Fri, Jul 08, 2005 at 03:50:49PM +0200, demerphq wrote:
Im not sure if this is
On 7/6/05, Ken Williams [EMAIL PROTECTED] wrote:
On Jul 6, 2005, at 4:00 PM, Dinger, Tom wrote:
To be perfectly honest, I don't care which way it is fixed, as long
as the
result still points to the right file.
Of course. That's what I'm asking: is bar guaranteed on Windows to
be
On Jul 8, 2005, at 8:51 AM, yves orton via RT wrote:
Im not sure if this is useful, but many of the things that File::Spec
tries to do on win32 are actually supported directly by the Win32 API.
IMO at least some of File::Spec's behaviour could take advantage of
this API.
Yeah, very true.
On Fri, Jul 08, 2005 at 03:50:49PM +0200, demerphq wrote:
Im not sure if this is useful, but many of the things that File::Spec
tries to do on win32 are actually supported directly by the Win32 API.
IMO at least some of File::Spec's behaviour could take advantage of
this API.
On 7/8/05, Michael G Schwern [EMAIL PROTECTED] wrote:
On Fri, Jul 08, 2005 at 03:50:49PM +0200, demerphq wrote:
Im not sure if this is useful, but many of the things that File::Spec
tries to do on win32 are actually supported directly by the Win32 API.
IMO at least some of File::Spec's
On Fri, Jul 08, 2005 at 11:07:22PM +0200, demerphq wrote:
should be testing here, but i beleive the problem you are thinking of
is due to symlinks to a directory? If so then the win32 equivelent
would be a junction I think and in that case yes, foo\..\bar == bar.
I have the creeping feeling
On 7/8/05, Michael G Schwern [EMAIL PROTECTED] wrote:
On Fri, Jul 08, 2005 at 11:07:22PM +0200, demerphq wrote:
should be testing here, but i beleive the problem you are thinking of
is due to symlinks to a directory? If so then the win32 equivelent
would be a junction I think and in that
On 7/8/05, Glenn Linderman [EMAIL PROTECTED] wrote:
On approximately 7/8/2005 1:53 PM, came the following characters from
the keyboard of Michael G Schwern:
On Fri, Jul 08, 2005 at 03:50:49PM +0200, demerphq wrote:
Im not sure if this is useful, but many of the things that File::Spec
On Jul 8, 2005, at 4:26 PM, Michael G Schwern wrote:
On Fri, Jul 08, 2005 at 11:07:22PM +0200, demerphq wrote:
should be testing here, but i beleive the problem you are thinking of
is due to symlinks to a directory? If so then the win32 equivelent
would be a junction I think and in that case
On Fri, Jul 08, 2005 at 11:49:59PM +0200, demerphq wrote:
canonpath() should never be inserting the CWD when cleaning up. ./bar is
the same as bar but $CWD/bar is not! Its important that cannonical
relative paths remain relative.
Sorry, i guess I didnt express myself properly. You cant
On Jul 8, 2005, at 4:50 PM, yves orton via RT wrote:
Sorry, i guess I didnt express myself properly. You cant clean up a
relative path properly without knowing where it is relative to.
Consider the following path:
..\..\foo
If we are in \bar then ..\..\foo is the same as ..\foo and \foo
On Jul 6, 2005, at 4:00 PM, Dinger, Tom wrote:
To be perfectly honest, I don't care which way it is fixed, as long
as the
result still points to the right file.
Of course. That's what I'm asking: is bar guaranteed on Windows to
be the right file when the input is foo\\..\\bar? On Unix,
To be perfectly honest, I don't care which way it is fixed, as long as the
result still points to the right file.
And now some history: the version of File::Spec::Win32 in Perl 5.8.0 did no
.. processing in canonpath(), and that was fine. As of Perl 5.8.1, the
canonpath() started doing the broken
16 matches
Mail list logo
