On Thu, Jan 13, 2000 at 02:37:13PM -0500, Mike Linksvayer wrote:
Argh, please unfix. I'm an idiot ... the behavior of getAbsolutePath()
is correct, only getCanonicalPath() is incorrect. I'll post a real
fix tonight, after I've tested more thoroughly.
It happens that getCanonicalPath
File.getAbsolutePath() was not stripping out extra "." path
components, which is contrary to the behavior of the JDK, and
breaks user code that relies on the JDK behavior. getCanonicalPath()
was also broken was a result.
The following code produces a simple case:
Thanks, fixed!
Argh, please unfix. I'm an idiot ... the behavior of getAbsolutePath()
is correct, only getCanonicalPath() is incorrect. I'll post a real
fix tonight, after I've tested more thoroughly.
I must learn not to:
* think code is finished before writing unit tests
* think code is
