Summary: | [1.5][compiler] public method with varags and protected single-argument method behave differently from javac | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Joachim Sauer <mail> |
Component: | Core | Assignee: | Kent Johnson <kent_johnson> |
Status: | VERIFIED NOT_ECLIPSE | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | jerome_lanneluc, Olivier_Thomann |
Version: | 3.4 | ||
Target Milestone: | 3.5 M2 | ||
Hardware: | PC | ||
OS: | Linux | ||
Whiteboard: |
Description
Joachim Sauer
2008-08-21 07:59:30 EDT
http://java.sun.com/docs/books/jls/third_edition/html/expressions.html#316811 seems to suggest that the behavior of Eclipse is correct here, as the protected method should not be considered at all, since it's not even "potentially applicable", since it's not accessible. I've filed a bug in the Sun bug parade as well and will update this bug, as soon as I hear back from Sun. Side note: Java 5 produces exactly the same problem when compiling the example. I've got a reply from Sun saying that the behaviour is indeed a bug (or at least was accepted into their bug tracking system as a bug). The bug _will be_ visible at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6746184 (according to the mail it can take 1 or 2 days until it is visible). This seems to indicate that the behaviour of ejc is in fact correct and this bug entry is invalid. Thank you. Closing as NOT_ECLIPSE Verified for 3.5M2 |