New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File::Spec::Unix->catfile("./a") ne File::Spec::Unix->catfile(".", "a") #12232
Comments
From perl@profvince.comCreated by perl@profvince.com $ perl -MFile::Spec::Unix -le 'print File::Spec::Unix->catfile("./a")' I don't think those two should be different, but they are. Which form and I suspect that changing this to './a' could cause a lot of breakage. Perl Info
|
From @jkeenanOn Fri Jun 29 06:02:21 2012, perl@profvince.com wrote:
I don't think this is a bug. I think your second instance is a correct "File::Spec::Unix::catfile: Concatenate one or more directory names and a filename to form a The documentation -- and this is true of File::Spec itself, as well -- Your first instance provides a relative path to a filename in the first If others differ, then we should discuss. But I don't think this is a Thank you very much. |
The RT System itself - Status changed from 'new' to 'open' |
From @ikegamiOn Sat, Jun 30, 2012 at 2:32 PM, James E Keenan via RT <
I disagree about the lack of bug, even though the behaviour is technically catfile, as standard for File::Spec, normally returns a canonized path.
|
From perl@profvince.com
I hadn't even realized that the documentation required at least one I can see several solutions : - 1°) catfile() should always return canonical paths stripped from their - 2°) catfile() should always return canonical paths starting with ./ - 3°) catfile() should just concatenate its arguments, without To summarize, here's what catfile() returns for each of these strategies +-----+-----+-----+-----+ I have implemented solution 3°) in the topic branch Vincent |
From @rjbs* Vincent Pit <perl@profvince.com> [2012-07-01T09:38:19]
I agree with your preference. -- |
From @jkeenanOn Sun Jul 01 06:38:57 2012, perl@profvince.com wrote:
Vincent, Did you get smoke results? Should we continue to explore this solution? Thank you very much. |
From perl@profvince.com
I must confess that it has been a long time since I've looked into this.
Probably, yes. The issue is still there.
|
From zefram@fysh.orgAll uses of catfile that conform to the API produce consistent results. -zefram |
@iabyn - Status changed from 'open' to 'rejected' |
Migrated from rt.perl.org#113898 (status was 'rejected')
Searchable as RT113898$
The text was updated successfully, but these errors were encountered: