Summary: | Missing code implementation in the compiler | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Thomas Pedersen <tho_ped> | ||||||
Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> | ||||||
Status: | RESOLVED WORKSFORME | QA Contact: | |||||||
Severity: | normal | ||||||||
Priority: | P3 | CC: | hood | ||||||
Version: | 2.0.2 | ||||||||
Target Milestone: | 2.1 M5 | ||||||||
Hardware: | PC | ||||||||
OS: | Windows NT | ||||||||
Whiteboard: | |||||||||
Attachments: |
|
Description
Thomas Pedersen
2003-01-08 09:36:13 EST
Could you please provide steps to reproduce? At least a source code that failed would help us to track it down. Do you have the same issue using 2.1 builds? This error indicates that an internal error occurred inside the compiler, typically an unhandled innerclass scenario (bug). We need a testcase reproducing the problem in order to issue a fix. Thomas - any update on this front ? Lowering severity until steps to reproduce are provided. We are also performing some rework on this front, which may improve this behavior in M5. If no steps are provided, will have to close this defect, hoping that ongoing changes will also cover this scenario. Closing. Please reopen if you can reproduce it in latest HEAD content (will be released into integration build 20030121). Created attachment 23724 [details]
Eclipse project file to reproduce bug
I was able to reproduce the bug:
"Missing code implementation in the compiler"
in Build I20050617-1618
Created attachment 23725 [details]
This is a project level workaround
The workaround just strips the inner class/interface definitions. The previous
code was production code that had compiled without problems in build
I20050401-1645.
Ben - At a 2 years distance, it is likely not the same defect, though same symptoms. Especially considering your testcase has some 1.5 code in there. Could you please enter a separate bug instead ? Entered bug 101283 with reduced testcase |