Open p5pRT opened 11 years ago
As reported in \<http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=257568> the behaviour of Cwd::abs_path has changed over time to working with non-existent to paths\, to not.
Quoting Roger in that report (on Sun\, 11 Jul 2010):
"To justify why I think this is a serious misfeature\, let's look at what we want to do. abs_path is doing two things: 1) if the path is relative to the CWD\, we make it absolute 2) if the path contains any symbolic links\, we remove them
Now\, if the path doesn't yet exist\, by definition it doesn't contain any links\, so part 2 can be skipped. But making it absolute is still useful. The path may also partially exist. If I'm in /tmp/foo and call abs_path('bar') then it could return /tmp/foo/bar if /tmp/foo contains no links. If foo was a symlink to /srv/baz then it should return /srv/baz/bar.
To summarise: abs_path can still work sanely in the existence of a nonexistent (or partially existent) path. It can walk up the tree so far as it can (while it exists) both making it absolute and removing links as necessary and then it can return the nonexistent part verbatim after that. For users who want to get a canonicalised path\, returning undef when there's a perfectly reasonable answer to give them is not good\, and it would be great to get this long-standing regression fixed. "
On Sun Mar 31 15:05:56 2013\, dom wrote:
This is a bug report for perl from dom@earth.li\, generated with the help of perlbug 1.39 running under perl 5.17.10.
----------------------------------------------------------------- [Please describe your issue here]
As reported in \<http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=257568> the behaviour of Cwd::abs_path has changed over time to working with non-existent to paths\, to not.
Quoting Roger in that report (on Sun\, 11 Jul 2010):
"To justify why I think this is a serious misfeature\, let's look at what we want to do. abs_path is doing two things: 1) if the path is relative to the CWD\, we make it absolute 2) if the path contains any symbolic links\, we remove them
Now\, if the path doesn't yet exist\, by definition it doesn't contain any links\, so part 2 can be skipped. But making it absolute is still useful. The path may also partially exist. If I'm in /tmp/foo and call abs_path('bar') then it could return /tmp/foo/bar if /tmp/foo contains no links. If foo was a symlink to /srv/baz then it should return /srv/baz/bar.
To summarise: abs_path can still work sanely in the existence of a nonexistent (or partially existent) path. It can walk up the tree so far as it can (while it exists) both making it absolute and removing links as necessary and then it can return the nonexistent part verbatim after that. For users who want to get a canonicalised path\, returning undef when there's a perfectly reasonable answer to give them is not good\, and it would be great to get this long-standing regression fixed. "
I observe the following on Darwin (where /tmp is a symlink to /private/tmp):
##### $ cd /tmp $ perl -E 'use Cwd; say "\<"\, Cwd::abs_path(q{foo})\, ">"' \</private/tmp/foo> #####
##### $ perl -E 'use Cwd; say "\<"\, Cwd::abs_path(q{foo/bar})\, ">"' \<> #####
... where neither 'foo' nor 'foo/bar' exists. It seems it is the addition of another level in the filesystem that causes 'abs_path' to return what I think is more likely an empty string rather than an undefined value.
Comments?
Thank you very much. Jim Keenan
The RT System itself - Status changed from 'new' to 'open'
This may be related to RT #116332: "abs_path dies on Windows when called with non-existent path".
This may be related to RT #116332: "abs_path dies on Windows when called with non-existent path".
Migrated from rt.perl.org#117423 (status was 'open')
Searchable as RT117423$