Bug 159448 - [1.5][compiler] Compiler could be better resilient to ill-formed method signature
Summary: [1.5][compiler] Compiler could be better resilient to ill-formed method signa...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-02 09:18 EDT by Philipe Mulet CLA
Modified: 2016-01-14 12:59 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Philipe Mulet CLA 2006-10-02 09:18:37 EDT 
Build 3.3M2

On following code, the method binding could still be created, to avoid secondary problem (undefined method).

public class X {
	
	void foo(X<String> x) {}
	
	{ 
		this.foo(null); // secondary error
	}
}
Comment 1 Philipe Mulet CLA 2008-01-23 05:29:15 EST 
Related to bug 196200
Comment 2 Philipe Mulet CLA 2008-02-29 05:13:21 EST 
This is slightly different from bug 196200. Here X is resolved to a non-generic type. There is no doubt the code is ill-formed. 
If X wasn't resolved, then there is no evidence it is not generic, hence recovery can help a bit more (in doubt, assume it is right).