2017-08-17 20:43 GMT+02:00 Eliot Miranda <[email protected]>: > Hi Stef, > > On Thu, Aug 17, 2017 at 8:08 AM, Stephane Ducasse <[email protected] > > wrote: > >> I do not know but I imagine that I added basenameWithoutExtension because >> I found the name much much clearer. I would have never guessed that >> base is the basename without the extension. >> > > While basenameWithoutExtension is an intension revealing selector it is > soon loooonnnnngggg :-) For file manipulation code that's a problem. I > wonder if something like bodyName is better because it's shorter. > > 25 years ago I had `aFilename basename withoutExtension` in my vw app... I don't think that such decomposition is a big efficiency problem for scripting.
Nicolas >> Stef >> >> On Wed, Aug 16, 2017 at 9:46 PM, Alistair Grant <[email protected]> >> wrote: >> > Hi All, >> > >> > I've just taken a look at issue 19609 FileReference>>base should be >> > before last separator and wonder whether it is a correct interpretation >> > of the original intentions. >> > >> > The original author of the issue, Michael, seems to feel that >> > FileReferene>>base and FileReference>>basenameWithoutExtension are the >> > same. >> > >> > My reading of the comments is that they perform a different function, >> > i.e.: >> > >> > >> > '/a/b/c.d.e' asFileReference base. "c" >> > '/a/b/c.d.e' asFileReference basenameWithoutExtension. "c.d" >> > >> > >> > are both the expected values, i.e.: >> > >> > - #base answers the name up to the first extensionDelimiter. >> > - #basenameWithoutExtension answers the name without what is typically >> > considered the file extension (the bit after the last >> > extensionDelimiter). >> > >> > Not shown above, but: >> > >> > - #basename answers the entire filename, i.e. "c.d.e". >> > >> > >> > Does anyone know the history of these methods? >> > >> > >> > Cheers, >> > Alistair >> > >> >> > > > -- > _,,,^..^,,,_ > best, Eliot >
