Summary: | No error message from inner type instantiation in static context | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Jared Burns <jared_burns> |
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 2.0 | ||
Target Milestone: | 2.0 M6 | ||
Hardware: | Other | ||
OS: | other | ||
Whiteboard: |
Description
Jared Burns
2002-04-30 11:18:41 EDT
This error is reported by the compiler during the code generation. The AST conversion doesn't do a code generation. I think we have a misunderstanding on what is done during the conversion. There is no flow analysis, neither a code generation during the AST conversion. So all errors which are detected later in the compilation process (after the type checking) cannot be reported through the compilation unit getMessages() collection. I will discuss with Jim to find out if we are suppose to do so. getMessages() states that it returns the list of messages reported by the compiler during the parsing or name resolution of this compilation unit. I will change it to specify more clearly that this list might be a subset of the problems returned by the compiler when the corresponding source is compiled. In summary, reporting this kind of error is outside the scope of the DOM/AST. This is the kind of error that only a full Java compiler is ever going to give you. If you need to detect this kind of error, your only serious option is to invoke the Java compiler. This bug report should be rejected. |