Stephen, > We had a big discussion on this a little while ago. Having it through > TorqueException then prevents users from implementing an interface that > has save throws ThisOtherException. Case in point, Fulcrum, which is one > of Torque's "official" users if there is such a thing.
> The basic conclusion was to switch everything over to > TorqueRuntimeException, as it would have the same effect as > TorqueException but the freeness of Exception. Kewl. This would be good for webapps. For Swing clients it might be an issue (throwing Runtime to the AWT thread makes for messy System.out). Maybe there is a case for determining at generation time whether you want TorqueRuntimeException or TorqueException on method signatures. That would be very cool. > We just haven't gotten to implementing it yet. - Paul __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
