The Daily WTF

One of the most powerful features of using exceptions for error handling is that they let you create your own exceptions, and thus accurately describe the family of exceptional situations your code could generate. On the flip side, some developers over-specialize, creating custom exceptions for every different place an out-of-range error could happen, for example.

Then there’s the code Nasch was debugging recently. The previous developer found a different way to create unique exceptions for every place an error might occur.

if (SwiftContextFactory.getInstance().generateWireCanonicalSendException) { 6/0 // Do some other things } catch (Throwable t) { log.error(“Couldn’t send wire message to SWIFT”, t) // Other error condition things }

The code in question here is Groovy, but it could be nearly any other OO language.

This block here is representative of a pattern that appears all over the codebase. When an exceptional situation occurs, divide by zero, then log the

To read the full article click on the 'post' link at the top.