At 12:31 PM 5/6/99 -0400, Allan Stanley wrote:
>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.
>
Oops, Allan, I'm sorry. I read your message out of context. Yes, letting
the Java reflection API do the walking, as you an Philip suggest, is
definitely worth exploring.
- Paul
