Wrong File(parent, child) behaviour on Windows when child starts with one s

Question

I've sent following problem report:
A DESCRIPTION OF THE PROBLEM :
On Windows when relative path starts from one slash it should be resolved from current disk (not current directory). This behaviour should be preserved for Files constructed with constructor File(parent, child). So results of run "System.out.println(new File(dir, relPath).getAbsolutePath())" and "System.out.println(new File(relPath).getAbsolutePath())" should be identical when running program from directory "dir".
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Compile and run from directory C:\temp\relpath following code:
import java.io.*;
public class Main {
     public static void main(String[] args) throws Exception {
          System.out.println(new File("C:\\temp\\relpath", "\\temp\\relpath\\Main.java").getAbsolutePath());
          System.out.println(new File("\\temp\\relpath\\Main.java").getAbsolutePath());
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
C:\temp\relpath>java Main
C:\temp\relpath\\Main.java
C:\temp\relpath\Main.java
ACTUAL -
C:\temp\relpath>java Main
C:\temp\relpath\temp\relpath\Main.java
C:\temp\relpath\Main.java
The answer was:
I have been analyzing your problem and it is not a bug but the intended behavior of the API.
The File(File,String) constructor includes this in the specification:
"If the |child| pathname string is absolute then it is converted into a relative pathname in a system-dependent way."
In the example provided here, the child path is absolute so it is converted into a relative path. This is the intended behavior.
My comments:
First, child pathname is not absolute. Even so, I don't understand why this guy contend that this behavior is correct.
Please comment this!

Answer 1

Please comment this!
I've sent following problem report:
A DESCRIPTION OF THE PROBLEM :
On Windows when relative path starts from one slash
it should be resolved from current disk (not current
directory). This behaviour should be preserved for
Files constructed with constructor File(parent,
child). So results of run "System.out.println(new
File(dir, relPath).getAbsolutePath())" and
"System.out.println(new
File(relPath).getAbsolutePath())" should be identical
when running program from directory "dir".
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Compile and run from directory C:\temp\relpath
following code:
import java.io.*;
public class Main {
public static void main(String[] args) throws
s Exception {
System.out.println(new File("C:\\temp\\relpath",
", "\\temp\\relpath\\Main.java").getAbsolutePath());
System.out.println(new
ew
File("\\temp\\relpath\\Main.java").getAbsolutePath());
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
C:\temp\relpath>java Main
C:\temp\relpath\\Main.java
C:\temp\relpath\Main.java
ACTUAL -
C:\temp\relpath>java Main
C:\temp\relpath\temp\relpath\Main.java
C:\temp\relpath\Main.java
The answer was:
I have been analyzing your problem and it is not a
bug but the intended behavior of the API.
The File(File,String) constructor includes this in
the specification:
"If the |child| pathname string is absolute then it
is converted into a relative pathname in a
system-dependent way."
In the example provided here, the child path is
absolute so it is converted into a relative path.
This is the intended behavior.
My comments:
First, child pathname is not absolute. Even so, I
don't understand why this guy contend that this
behavior is correct.
*/