Frank-Michael Moser wrote:
This would be nice, I will test it...
OK, I've committed it now.
No, I think that would involve the halting problem :-). My fix is most likely compiler-specific and depends on how the compiler names the implicit Class instances. Maybe not that desirable.
What do you have in mind for patching this case - testing whether a string given to Class.forName(...) forms a valid class-name or something similar?
Let me know what you think.
Conor
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
