Bugzilla – Full Text Bug Listing
| Summary: | [polish][compiler] Inconsistent error message for non-visible field | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Philipe Mulet <philippe_mulet> |
| Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 3.1 | ||
| Target Milestone: | 3.1 RC2 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
Changed problem reporter, and adapted various compiler tests which were exposing offending error message (e.g. NegativeTest#test221). Verified for 3.1 RC2 using build N20050607-0010 + JDT/Core HEAD However, note that text range for the compiler error is still inconsistent: - first is "val" - second is "x.someX.val" Perhaps should it be "someX.val" for both? Open bug 98689 for field source range inconsistencies. Verified with I20050610-0010 |
Build 3.1rc1 On following testcase, the various occurrences of visibility errors are not flagged with a consistent error message: public class X { X someX; private int val = 0; } class Other { { int i = new X().someX.val; // The field val is not visible X x = new X(); int j = x.someX.val; // The field x.someX.val is not visible } } Both should include the field declaring class, and read: The field X.val is not visible