Proposal for std.path replacement

[spir]

On 03/05/2011 05:32 PM, Lars T. Kyllingstad wrote:
> On Fri, 04 Mar 2011 08:14:44 -0500, Nick Sabalausky wrote:
>
>> "Lars T. Kyllingstad"<public at kyllingen.NOSPAMnet>  wrote in message
>> news:ikofkc$322$1 at digitalmars.com...
>>> As mentioned in the "std.path.getName(): Screwy by design?" thread, I
>>> started working on a rewrite of std.path a long time ago, but I got
>>> sidetracked by other things.  The recent discussion got me working on
>>> it again, and it turned out there wasn't that much left to be done.
>>>
>>> So here it is, please comment:
>>>
>>>     http://kyllingen.net/code/ltk/doc/path.html
>>>     https://github.com/kyllingstad/ltk/blob/master/ltk/path.d
>>>
>>>
>> I don't want to jinx it, but there seems to be a lot of agreement in
>> this thread. Seriously, how often does that happen around here? :)
>
> Not too often, so I take it as a good sign that I'm onto something. ;)
>
> The only disagreement seems to be about the naming, so let's have a round
> of voting.  Here are a few alternatives for each function.  Please say
> which ones you prefer.
>
>   * dirSeparator, dirSep, sep
dirSep
>   * currentDirSymbol, currentDirSym, curDirSymbol
currentDirSymbol
>   * basename, baseName, filename, fileName
baseName, fileName
>   * dirname, dirName, directory, getDir, getDirName
dirName, getDirName
>   * drivename, driveName, drive, getDrive, getDriveName
driveName, getDriveName
>   * extension, ext, getExt, getExtension
>   * stripExtension, stripExt
> (The same convention will be used for stripExtension, replaceExtension
> and defaultExtension.)
don't mind

About "xyz" vs "xyzName": the point is what is denoted /is/ a name. It's not a 
programming object modelling a directory or a drive.

> -Lars

Denis
-- 
_________________
vita es estrany
spir.wikidot.com