Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 84585

Summary:	[dom] dual mode ASTParser for binding resolution
Product:	[Eclipse Project] JDT	Reporter:	Olivier Thomann <Olivier_Thomann>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	deepakazad, dirk_baeumer, markus.kell.r, martinae
Version:	3.1
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:
Bug Depends on:
Bug Blocks:	81101, 81544

Description Olivier Thomann

2005-02-07 11:37:43 EST

Right now, if some bindings are problem binding on the compiler side, we do
return them as normal binding on the dom/ast side.
I think we need two modes:
- strict mode: problem binding => return null on the dom/ast
- fuzzy mode: problem binding => return a binding not null on dom/ast if the
error can be handled (visibility problem for example).
See bug 81544 comment 11.

Comment 1 Olivier Thomann

2005-02-07 11:38:28 EST

Jim,

Do you think this could be explained in the specs?

Comment 2 Olivier Thomann

2005-02-08 10:02:13 EST

This can slow down the conversion.
The compiler doesn't always create problem bindings. So I would not push to get
a dual mode.

Comment 3 Markus Keller

2005-06-07 14:36:04 EDT

Copying bug 81544 comment 25 and adding CCs.

The current solution (returning a generic type binding for half-way resolved
bindings) conflicts with bug 80472. When I get a generic binding, I
don't know whether it's generic because of bug 80472 or because type arguments
could not be resolved. I think we can ship 3.1 with the current solution, but
this should definitely be discussed again for 3.2.

Comment 4 Markus Keller

2005-06-30 11:55:06 EDT

See also bug 101955.

Comment 5 Philipe Mulet

2006-04-04 08:59:02 EDT

defer post 3.2

Comment 6 Denis Roy

2009-08-30 02:12:25 EDT

As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.