Bug 25018 - parseCompilationUnit(..) does not report a compile error
Summary: parseCompilationUnit(..) does not report a compile error
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.1 M3   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-10-17 15:09 EDT by Rory Lucyshyn-Wright CLA
Modified: 2002-11-13 09:14 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rory Lucyshyn-Wright CLA 2002-10-17 15:09:04 EDT
It appears that when the following code is parsed using parseCompilationUnit
(..), with bindings, the CompilationUnit node return does not have any messages 
or problems attached to it.  No messages or problems are returned by 
getMessages or getProblems when these methods are invoked on the node.
In the editor, no error is detected by the on-the-fly error detection when I 
type the following code into the editor and don't save.
It is invalid code and results in a reported compile error when it saved and 
built.

package p;

public class A {
	void foob() {
		int b= b;
	}
}
Comment 1 Olivier Thomann CLA 2002-10-17 16:15:03 EDT
This is a consequence of bug 24773. The error you mention is reported later in
the compilation process. Fixing bug 24773 will fix this one as well.
I have a fix ready, but I am waiting M2 to be out to release it in 2.1 stream.
Comment 2 Olivier Thomann CLA 2002-10-17 16:45:56 EDT
Fixed and released in 2.1 stream.
Regression tests added.
Comment 3 David Audel CLA 2002-11-13 09:14:39 EST
Verified.