Ok the idea of type migration kicks ass, and is certainly on the wow
factor. I am just going through an exercise of moving all Vectors to
List (with ArrayList instead of Vector) and tried to use Type Migration.
It throws a lot of exceptions during the process, and then to top it all
off, it really screws up the code!
if you had something like foo.removeElementAt(i) I get
(foo.removeElementAt)get(i)... what the heck is that? :)
Anyway, the idea is real cool, but man it needs some serious testing,
and I can't give it serious testing until the exceptions stop being
thrown. This is in the 3326 or what ever number eap we're at now.
I filed the exceptions. Did not file the messed up syntax replacement.
Too bad, I REALLY could have used this today.