This feature encourages a good development practice: compile early and keep
it compilable. :-)
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]
> On Behalf
> Of Paul Kinnucan
> Sent: Wednesday, January 17, 2001 11:46 AM
> To: Sherley BROTHIER
> Cc: [EMAIL PROTECTED]
> Subject: Re: JDE/Completion: import statement completion
>
>
> At 08:12 PM 1/17/01 +0100, Sherley BROTHIER wrote:
> >Thanks Paul for your answer.
> >I think it's shame that it doesn't work.
> >Is there any plan for such an extension ?
> >I think it could be very usefull to have completion even on
> non compiled
> >classes.
>
> Why? Any "intellisense" capability requires creation of a completion
> database "compiled" from the source code. Every time you
> create or modify a
> source file, the database has to be updated to permit
> completion. The JDE
> uses the current classpath as the completion database.
> Compiling a source
> file updates the completion database. I don't see the benefits of a
> specialized completion database justifying the huge amount of
> development
> work required to design and implement it.
>
> - Paul
>
