Bugzilla – Full Text Bug Listing
| Summary: | [compiler] wrong error message for specific synthetic accessor warning | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Maxime Daniel <maxime_daniel> |
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | minor | ||
| Priority: | P3 | CC: | Olivier_Thomann |
| Version: | 3.4 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | stalebug | ||
Kent, please see if we can rephrase this warning. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |
3.4 M7 Consider the following source: public class X { void foo() { new XX(); // warning here } private class XX { private XX() { } } } It raises a warning which reads: Access to enclosing constructor X.XX() is emulated by a synthetic accessor method. Increasing its visibility will improve your performance The 'enclosing' word is misleading in this case, given the effective types enclosing configuration. This might also happen with other members than constructors.