Re: [Jython-dev] Class.forName bug The return.

[<bc...@wo...>]

[Samuele ]

>A simple note:
>
>also AdapterMaker should not use Class.forName.

I'll fix this.

>A question:
>
>After these fixings is the name taking constructor for ProxyMaker still 
>necessary?

The ctor still takes a name string, but now the name only specify the
name of the class we are building.

>and it's Class.forName based build method?

I think this removes the last of the bad forName's.

I have not fixed the Tools/mkjava.py or Tools/Freezer.py. Neither of
these scripts have been working for a long time due to other changes in
the constructor of JavaMaker.

regards,
finn