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

["Robert Klemme" <bob.news@xxxxxxx>]

"Bob Foster" <bob@xxxxxxxxxx> schrieb im Newsbeitrag
news:b6brk0$mvb$1@xxxxxxxxxxxxxxxx
> 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.

That's great!  Hopefully my download of 2.1 finishes this week, then I'll
have a look. :-)

> 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.

Well, you can always refactor the signature.

    robert

>
> 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
> >
>
>