Bug 46166 - Compiler Error: "y can not be resolved" in comment(?)
Summary: Compiler Error: "y can not be resolved" in comment(?)
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 3.0 M5   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-05 22:47 EST by markusle CLA
Modified: 2003-11-07 05:01 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description markusle CLA 2003-11-05 22:47:01 EST 
/* The next peace of code produces Compiler Error messages:
 *  1. Invalid Unicode
 *  2. nvalidUnicode cannot become resolvewd (or ....) 
 *  3. y can not be resolved
 * I think only the first error should become reported, because all others
 * (possible very much) confuses me (and perhaps other persons)
 * Bug Seven?
 *
 * Kinds regards
 * mle
 */
/**
 * .\uInvalidUnicode converts comment to none-comment 
 * int x=y;
 */
Comment 1 Philipe Mulet CLA 2003-11-06 05:06:07 EST 
I can only reproduce the invalid unicode in comment which is legite.
Comment 2 markusle CLA 2003-11-06 05:21:40 EST 
Sorry I forget to note the version I use:
  linux_i386.eclipse_gtk_2003_10_10 integration build.

Yesterday I tried the newest intergration build and there
are some (at least one) bugs fixed in the compiler;
but the new version debugpane is too buggy for me, 
so I stopped using it. Perhaps this bug is fixed also in 
the newest release.

Sorry for my bug report on old version.

PS: I read a little bit in the sources of
  
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-core-home/r3.0/main.html#updates

and it seams it exists a good peace of Java 1.5 language features
in the compiler.
When are they useable? I tried to compile a template, but it doesn't work.
Comment 3 Philipe Mulet CLA 2003-11-06 05:52:17 EST 
1.5 support is in progress, we will broadcast once we reach some decent state. 
This isn't achieved yet. We have a grammar and some of the nodes created, but 
not supported yet.

The unicode issue is a JLS requirement (JLS 3.2) or see bug 6677.
Does the invalid reference occur if you remove the invalid unicode ?
Comment 4 markusle CLA 2003-11-06 06:05:28 EST 
>The unicode issue is a JLS requirement (JLS 3.2) or see bug 6677.
I know: first lex, then parse the JavaCode or something like that .. .
> Does the invalid reference occur if you remove the invalid unicode ?
No: If I remove the invalid unicode, or insert an valid one everything 
is ok.
Btw: I discovered this (fixed) bug as I inserted ca. 100 lines of a 
Windows batch file in a comment: I got dozend of compilaton errors beyond
an invalid unicode.
Comment 5 Philipe Mulet CLA 2003-11-06 18:00:52 EST 
Is it ok to close now ?
Comment 6 markusle CLA 2003-11-06 23:16:28 EST 
Yes, please close it. (Btw: (--bugcount) == 6 ;-)
Comment 7 Philipe Mulet CLA 2003-11-07 05:01:16 EST 
Closing, as reporter cannot reproduce either on latest.