| Re: [jdt-core-dev] Definition of potential match? |
A potential match means that the search engine could not resolve everything
it needed. This can happen if the build path was not correctly set by the
user (for example some required projects are missing from the build path),
or if the user code would not compile (for example a class doesn't
implement all the methods of an interface).
The main benefit of showing a potential match is that the user can still
see references and declarations even if his/her code is not ready to be
compiled.
"Daniel
Megert/ZRH/OTI" To: jdt-core-dev@xxxxxxxxxxx
<Daniel_Megert@oti.c cc:
om> Subject: [jdt-core-dev] Definition of potential match?
Sent by:
jdt-core-dev-admin@e
clipse.org
12/04/2001 03:59 PM
Please respond to
jdt-core-dev
Can you give an exact definition of a possible match i.e. if I see a
possible match in the Search view what conditions are valid and what is the
benefit of showing it as potential match instead of ignoring it?