Re: wrong File::SEPARATOR ?
> You have a point, as I just can't imagine that the file=20
> separator used=20
> by Ruby internally will change any time soon (but who=20
> knows?).=20
I think this can be ruled out, because there probably won't be
too many apps around which just *know* that Ruby accepts /, and
have slashes hardcoded everywhere. I too have never thought about
the existence of File::SEPARATOR as a constant, and came accross
it only when I wanted to construct file names for external applications,
which should be OS independent.
Ronald
|