On Sat, Mar 23, 2013 at 4:42 PM, Yakov Galka
On Sat, Mar 23, 2013 at 9:55 PM, Joseph Van Riper < fleeb.fantastique@gmail.com> wrote:
On Sat, Mar 23, 2013 at 12:36 PM, Yakov Galka
wrote:
[...]
What are the separator characters in c:\x.txt, c:x.txt, or SYS$SYSDEVICE:[USER.DOCS]PHOTO.JPG:8?
* C:\x.txt: : for root, \ for branches (and branches between leaves). * C:x.txt: : for root, leading right into a leaf that would be wherever your sense of 'current directory' should be.
Whatever definition you give here, it won't let you parse the path with a simple split() or concatenate it with a simple join(). Therefore all such definition would be useless, and thus I see no point in talking about "separators" in a portable path library.
To be honest, I think we're actually thinking the same thing here, in general. I was describing what it would take to create a string out of the underlying objects, but you're describing the effort it takes to convert a string into the underlying objects, which I hadn't covered in my e-mail. It is an important problem, though. I should examine your link... it sound intriguing. - Trey