Changes in getCanonical Path behaviour

Thread view:

Roedy Green - 11 Feb 2006 03:58 GMT

In the olden days, on Windows, File.getCanonicalPath would look the
file up in the directory and find out its precise case and return that
to you. Now it returns the same thing as getAbsolutePath, echoing the
case of the filename as you gave it.

Signature

Canadian Mind Products, Roedy Green.
http://mindprod.com Java custom programming, consulting and coaching.

Reply to this Message

Chris Smith - 11 Feb 2006 04:07 GMT

> In the olden days, on Windows, File.getCanonicalPath would look the
> file up in the directory and find out its precise case and return that
> to you. Now it returns the same thing as getAbsolutePath, echoing the
> case of the filename as you gave it.

"Now"? I don't see that behavior with Java 1.5.0-b64. On what version
do you see this behavior?

Signature

www.designacourse.com
The Easiest Way To Train Anyone... Anywhere.

Chris Smith - Lead Software Developer/Technical Trainer
MindIQ Corporation

Reply to this Message

Roedy Green - 11 Feb 2006 04:51 GMT

On Sat, 11 Feb 2006 03:58:04 GMT, Roedy Green
<my_email_is_posted_on_my_website@munged.invalid> wrote, quoted or
indirectly quoted someone who said :

>In the olden days, on Windows, File.getCanonicalPath would look the
>file up in the directory and find out its precise case and return that
>to you. Now it returns the same thing as getAbsolutePath, echoing the
>case of the filename as you gave it.

oops. My mistake. I did not set up the test files correctly. I was
getting results for a non-existent file, which of course has no define
canonical case.

Signature

Canadian Mind Products, Roedy Green.
http://mindprod.com Java custom programming, consulting and coaching.

Reply to this Message

Changes in getCanonical Path behaviour

Free Magazines