Bug 10753

Summary: Compiler barfs on c:\ubizen with invalid unicode
Product: [Eclipse Project] JDT Reporter: Jos Dehaes <jos.dehaes>
Component: CoreAssignee: Philipe Mulet <philippe_mulet>
Status: RESOLVED WONTFIX QA Contact:
Severity: blocker    
Priority: P3    
Version: 2.0   
Target Milestone: 2.0 M4   
Hardware: PC   
OS: Linux-Motif   
Whiteboard:

Description Jos Dehaes CLA 2002-03-05 08:06:40 EST 
Files that are checked in in our source control system (starteam) have a header
with the local filename in the filecomment. Since the starteam client only runs
on windows, the path will contain backslashes. If one of these backslashes is
followed by a letter 'u', it will be considered as a unicode escape sequence.
This blocks me from compiling classes that contains paths like that (which means
all my files in that project, since the package structure is "com.ubizen.sdp"). 

Eclipse worked fine for me until I checked in my sources, now they contain the
full pathname in the filecomment, and the compiler won't compile them, so I
consider this to be a blocker.
Comment 1 Philipe Mulet CLA 2002-03-05 10:09:27 EST 
JLS 3.2 explains that unicode translation occurs prior to tokenization. 
Therefore invalid unicode sequences are reported inside comments.
Javac produces the same error.

/**
 * \u\X.java is invalid
 * \\u\X.java is fine
 */
public class X {
}

This is a bug of the source control system you're using, which ends up 
producing illegal Java source files according to the specs.
Comment 2 Ralf Hauser CLA 2004-08-29 02:03:10 EDT 
see also: Bug 6677