On Monday 05 April 2004 21:45, David Hovemeyer wrote:
> The downside, of course, is breaking backward compatibility. But,
> the original APIs were flawed, and the new behavior is (IMO) better.
Ok, thanks for the background.
In principal, I can do
try
{
return currentClass.getSuperClass();
} catch( Exception e )
{
return null;
}
in our code. I can't catch ClassCastException, since that is not compatible
with the 5.5 release that we officially depend on.
But it works with reasonable amount of comments - - for us.
Is this a change that are in many other method signatures as well, or just a
few?
If only a few, I would recommend the compatible approach of introducing a
seperate method where the exceptions are thrown, to keep the compatibility.
Well, once the BCEL community can decide and hopefully release, please (if you
remember) CC [EMAIL PROTECTED], so we can update the hack.
Cheers
Niclas
--
+---------//-------------------+
| http://www.bali.ac |
| http://niclas.hedhman.org |
+------//----------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
