Greetings! Seems fine in my tests, but I'm still unsure whether it is not better to throw an error and point out the faulty pathname concatenation. Seems like we are just covering up bad code out of convenience.
Take care, Raymond Toy <[email protected]> writes: > On 2/19/26 9:19 AM, Camm Maguire wrote: > > Greetings, and thanks for the note! > > Actually, I thought this was more of a feature rather than a bug. > Pathname namestrings of the form "...//..." are inherently ambiguous > (e.g. ...//.. means ..././... in Linux et.al., but means / in emacs) and > are almost always the result of a lazy concatenation of paths, typically > avoiding merge-pathnames which should always give the right answer: > > (merge-pathnames "../bar/baz" "etc/foo/") > > #P"etc/foo/../bar/baz" > > That said I have a patch now testing which collapses // to /. > > Thanks! I think it makes gcl more consistent with what other lisps do with > paths like this. > > ​ > -- Camm Maguire [email protected] ========================================================================== "The earth is but one country, and mankind its citizens." -- Baha'u'llah
