Re: import statements generated by dava make ambiguity of class ref.

[Ondrej Lhotak <olhotak@sable.mcgill.ca>]

I was under the impression that Dava used to do this at one point, but
that Jerome fixed it to put in the import statements instead, because it
makes the code much more human-readable than having every class fully
qualified. So perhaps we just need a way to turn this feature off. Or,
perhaps we need a way to have it automatically turn off when there is a
conflict (although, as you point out, this may be difficult to detect).

Jerome, can you comment on this?

Ondrej

On Fri, Sep 19, 2003 at 09:20:50AM +0900, Haruyuki Kawabe wrote:
> 
> Laurie Hendren wrote:
> 
> >Yes, I believe that is a weakness in the decompiler.  Would you like
> >to submit a patch so that it can do something more accurate.
> >  
> >
> It seems to me that it is difficult to generate import statements with 
> wild card from
> a class file scine all classes are refered by fully qualified name (i.e. 
> with packages )
> in it. Otherwise we have to inspect  whole tree of packages that would 
> be imported.
> 
> So the easiest solution for this problem would be refering all classes 
> by its fully qualified
> name and avoiding use of import statements in the generated java codes, 
> right ?
> 
> If you agree with me on this solution, I'll try to make a patch for it.
> 
> Haruyuki Kawabe
>