Bugzilla – Full Text Bug Listing
| Summary: | [1.5][dom] Foreach statement shows extraneous semi column into debug variables view | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Maxime Daniel <maxime_daniel> |
| Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | minor | ||
| Priority: | P3 | ||
| Version: | 3.2 | ||
| Target Milestone: | 3.2 M3 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
yes, this is related to the fact that Object o is considered as a local declaration and therefore it is printed as a statement. We would need to change the printStatement(...) implementation of the ForeachStatement not to use the print method for the local declaration. But this is for debugging purpose anyway, so is it really worth it? I'll fix it. We simply cannot use the print method for the local variable declaration in the foreach. Fixed and released in HEAD. Regression test added in org.eclipse.jdt.core.tests.compiler.parser.DietRecoveryTest.test113. Verified for 3.2 M3 using build I20051031-0010 |
Build id: I20050923-1000 When debugging into code that parses Java source into a model, the following statement: for (Object o : i) { o.toString(); } appears as follows when selecting the matching ForeachStatement instance into the variables view of the debugger: for (Object o; : i) { o.toString(); } (note the extraneous ; after o). This must be related to printStatement, which calls Statement.print, hence gets the terminator whereas it should not.