[news.eclipse.tools] Re: Auto Completion for new Methods

["Bob Foster" <bob@xxxxxxxxxx>]

Already have something along these lines. If you call a method that doesn't
exist editor will offer to generate it for you; if you do, thereafter,
method is available to code assist.

The unresolved problem seems to me to be that, if you are writing top down
the signature of unwritten methods often changes as you write. Currently,
editor will offer to generate a new method, but not to modify signature of
an existing method, which would be more appropriate in this context.

Just a thought.

Bob

"Robert Klemme" <bob.news@xxxxxxx> wrote in message
news:b6bmg4$3uc$1@xxxxxxxxxxxxxxxx
>
> Hi all,
>
> I was just thinking of an interesting feature.  Assume you are Java coding
> top down, i.e. you first write a method that invokes other methods etc.
> If you strictly adhere top down you end up always referencing methods that
> are not there.  When writing a new method auto completion could suggest
> those methods names that were detected to be in error because they are not
> present in the class or because the signature does not match.
>
> What do others think?
>
>     robert
>