Fw: [platform-core-dev] Latest on path character issues

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

[forwarding to list]

I have added those examples to the doc.

toString does indeed produce the same
output as toOSString on Linux. This has actually always been true; the
only difference between the two is that toString always uses '/' as the
segments separator, and toOSString always uses the local file system's
segment separator (java.io.File.separatorChar). It's also worth noting
that under this new proposal, the implementations of toString and toOSString
are completely untouched.

Thanks again for the comments.

"Ed Burnette" <Ed.Burnette@xxxxxxx>

10/19/2004 11:02 AM

To	John Arthorne/Ottawa/IBM@IBMCA
cc
Subject	RE: [platform-core-dev] Latest on path character issues

Looks good. On #3 simply including
those two examples in your doc, plus matching examples for the reverse
operation (i.e., given the strings "c:\foo", "c:/foo",
and "c::/foo", calling these contructors/factories results in
this device/segment on Windows/Linux), would address it.
 
It looks like toString() is returning
on all systems what toOSString() returns under Linux, is that right? Should
the doc say that or is that an accident?