Summary: | [1.5][compiler] Overloading with autoboxing handled differently from javac | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | dave irving <dave.irving.personal> |
Component: | Core | Assignee: | Kent Johnson <kent_johnson> |
Status: | VERIFIED NOT_ECLIPSE | QA Contact: | |
Severity: | minor | ||
Priority: | P3 | CC: | Olivier_Thomann |
Version: | 3.4 | ||
Target Milestone: | 3.5 M6 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
dave irving
2009-03-06 08:16:04 EST
Hmmm. Looking closer at 15.12.2 of the JLS - the first step involves finding _all_ potentially applicable methods. The subsequent steps appear to attempt to find one or more applicable methods from the initial set of potentially applicable methods. Given that, surely doSomethingWith(int) cant be a potentially applicable method - and thus I'd expect an applicable method to be found in phase 2 (15.12.2.3) - applying boxing to select doSomethingWith(Object) as the applicable method. So I'm beginning to think that perhaps its actually Eclipse which is doing the right thing here..... All I can confirm, of course, is that Eclipse and javac are not agreeing :) The example compiles successfully with javac 7 Whatever issue javac had, has been fixed. Verified for 3.5M6 |