[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [platform-core-dev] Valid characters in Eclipse paths
|
I don't understand what you mean. I'm saying that if you
use "new Path (null, pathName)" then any colons in pathName would NOT be treated
as device separators. Isn't that the same as what you're
saying?
Ed, From the standpoint of how the CVS plugin uses the Path
constructor, what you propose in point 2 would not work. Even if a relative path
contains a colon, it must not be treated as a device separator. The only way I
can see to solve it is for the Path API to provide an alternate constructor that
is speced to not treat the colon as a device separator. Michael platform-core-dev-admin@xxxxxxxxxxx wrote on 05/10/2004 11:41:04
AM:
> 2. Colons are easy too. In
Path(fullPath), make everything before
> the first colon the device and
leave any other colons untouched. In
> Path(device,path), do not scan
path for colons at all. Note that's
> not an API break, just an
implementation detail. Currently these two
> constructors go to the same
initialize() function but there's no
> reason it has to be that
way.
