Bugzilla – Full Text Bug Listing
| Summary: | New compiler warning: uncommented (catch) block | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Gary Gregory <ggregory> |
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | 3.0 | ||
| Target Milestone: | 3.0 M3 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
Lucky you, I just released support for this one for today's integration build ! It also finds empty methods, empty types and all empty blocks, which are not documented as you were suggesting. *** This bug has been marked as a duplicate of 32285 *** Whoa, you must have ESP... ;-) |
IMHO opinion, this not commenting empty catch block is very bad practice. I am not sure if this falls under the E compiler warning phylosophy but... the following could be flaged as a warning: ... catch (FooException foo) { } while the following would not: catch (FooException foo) { // any kind of comment }