> Paul Kinnucan wrote:
> > b. If any of the entries has the same root name as the target
class, go
> > to next step.
>
> Wouldn't it be better to make this collect a list of _all_ matching
entries,
> sort of like jikes does when it finds an ambiguous class when
compiling (which
> you guys that don't use * in imports probably never see :-))? If
there's only
> one entry, no problem. If there are more, let the user select the
correct one
> (I guess this would probably be best handled at the elisp level, by
checking the
> number of lines in the string returned).
When I import a class from a package I often import *other* classes from
that package. It would be convenient if this could be taken into
account when presenting the completion list - give priority to
completions involving packages that already appear in the current import
declarations.
Hmmm... considering packages that appear in current imports might give
rise to another completion strategy...
> Cheers,
> Len.
> ---
> Len Trigg =========== http://www.cs.waikato.ac.nz/~trigg/
> Computer Science Dept, University of Waikato, New Zealand
> PGP Public key http://www.cs.waikato.ac.nz/~trigg/key.asc
Allan
