[phobos] next release (meaning of path)

[Jesse Phillips]

I do not know of a good reason for having a Path type. However I do
believe much can be added to help with manipulated paths. Here are
some issues I've had.

* Converting to the proper sep
* getBaseName(getName(file)) will give just the filename and no path
when there is no extension, switching the calls gives you nothing.
* A quoted path is sometimes valid, and some times not. Namely making
system calls needs the quotes or escaped spaces, while std.file
expects none of that.
* It should be easy to convert one OS path style to another. (Ignoring
drive letter)

On Sun, Jan 2, 2011 at 4:01 PM, Andrei Alexandrescu <andrei at erdani.com> wrote:
> Let's have a brief vote. Do you think we should have a string-like structure
> Path in std.path? What primitives should it have?
>
> I'm fine using strings, but I could be convinced to use a Path type if it
> had some compelling advantages.
>
>
> Andrei