[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [platform-core-dev] Latest on path character issues
|
This looks better. Notes:
1. You have isValidSegment() and isValidPath() deprecated
in one section (Other migration issues) and not deprecated in an earlier section
(API Details). I think you are intending for nothing to be deprecated in this
latest version.
2. It's not clear what change, if any, is proposed for the
two-argument Path() contstructor. On Windows if the device is null does it look
for device in the second argument? How about on Unix? If device is not null does
it still look for and strip off (but otherwise ignore) a device in the second
argument on Windows? Unix?
3. It's still not clear how the output of toString(),
toOSString(), and toPortableString() will vary for various paths on various
hosts.
Based on feedback from the previous
proposal, and from the experience of implementing and testing various solutions,
I have made some changes to the proposal to allow colon and backslash characters
in paths. ...
