Sorry that wasn't clear. I understand the desired feature. My point
was that a completion algorithm that needs to validate a dynamically
constructed fully qualified type can use reflection. For example,
class.forName(packageName + "." + simpleClassName) where packageName
runs over all packages in the current import declarations of the
compilation unit. This only handles completions that can be resolved by
considering the current imports, but that's a pretty common case.
Allan
----- Original Message -----
From: Paul Kinnucan <[EMAIL PROTECTED]>
To: Allan Stanley <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, May 06, 1999 12:05 PM
Subject: Re: Feature thought [WAS: RE: smart completion]
> At 11:31 AM 5/6/99 -0400, Allan Stanley wrote:
> >What about reflection: Class.forName("java.io.File")
> >
> >This is supported by all JDK versions, but I don't know about the
bean
> >shell (tricky!). If reflection could be used we wouldn't have to
mess
> >with classpaths, etc.
> >
>
> The idea is to avoid having to enter the fully qualified class name.
>
> The jde-import-class command (C-c C-v C-z) already generates an import
> statement if you specify a qualified class name. The only value-added
I can
> see in what you're suggesting is that the JDE would actually verify
that
> the class exists.
>
> - Paul
>
