Bugzilla – Full Text Bug Listing
| Summary: | [compiler] Qualified parameterized allocation expressions rejected incorrectly. | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Srikanth Sankaran <srikanth_sankaran> |
| Component: | Core | Assignee: | Srikanth Sankaran <srikanth_sankaran> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | maxime_daniel, Olivier_Thomann |
| Version: | 3.7 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | stalebug | ||
*** Bug 236243 has been marked as a duplicate of this bug. *** (In reply to comment #0) > The following program elicits just one error from > javac7 (b137) while it elicits two errors from > JDK5,6 and from eclipse. This difference needs to > be investigated. > > > public class X<T> { > class Y<K> { > } > X<String>.Y<Integer> xy = new X<String>.Y<Integer>(); // <<<--- HERE That doesn't sound right, how can a compiler guarantee that the enclosing instance is of suitable type here ? See also https://bugs.eclipse.org/bugs/show_bug.cgi?id=321185 Needs further study, Moving it out of M5 plan. 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. If you have further information on the current state of the bug, please add it. 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. 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. If you have further information on the current state of the bug, please add it. 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. |
The following program elicits just one error from javac7 (b137) while it elicits two errors from JDK5,6 and from eclipse. This difference needs to be investigated. public class X<T> { class Y<K> { } X<String>.Y<Integer> xy = new X<String>.Y<Integer>(); // <<<--- HERE } class Z { X<String>.Y<Integer> xy = new X<String>.Y<Integer>(); }