On 9 November 2017 at 22:12, Norbert Hartl <norb...@hartl.name> wrote: > is there a good explanation why > > ‚foo‘ asFileReference parent basename > > gives ‚/‘ ?
I'd like to think about this a bit more, but at first glance the problem seems to be that Path>>basename was written only taking Absolute paths in to consideration. So RelativePath>>basename needs to be added: basename "Returns the base of the basename, i.e. foo/gloops.taz basename is 'gloops.taz' . basename is '.'" self size == 0 "the current directory" ifTrue: [ ^ '.']. ^ self at: self size Cheers, Alistair