News for hackers. Stuff that matters.

A comment on Java’s Checked Exceptions Are Evil? (2015). Parent comment

Re:Java’s Checked Exceptions Are Evil? (2015) by kjeetgill on Sunday September 23, 2018 @02:59PM (#18052549)
It just depends I suppose? Sometimes you rewrap to get an unchecked runtime exception out of it. Sometimes there's context worth adding: new IndexLoadException(ioException, "Is Hadoop down?").

Either way I think the one thing I hate hate hate is, losing stacktraces! Don't throw a new exception without wrapping the old one. I need that info!

[ Parent | on HN ]
Re:Java’s Checked Exceptions Are Evil? (2015) by EdwardDiego on Sunday September 23, 2018 @08:55PM (#18054280)
> Either way I think the one thing I hate hate hate is, losing stacktraces! Don't throw a new exception without wrapping the old one. I need that info!

This! Throw as many RuntimeExceptions as you like, so long as you include the originating exception.

[ Parent | on HN ]
Re:Java’s Checked Exceptions Are Evil? (2015) by bluejekyll on Monday September 24, 2018 @09:53AM (#18057658)
Again I go back to InterruptedException, this advice is very wrong in that context, and similarly others.

People often make the very big mistake of generically catching Throwable and then rewrapping that, which would include all Error types. Those should must be rethrown without wrapping. I don’t think you meant to imply that, but it’s easy to overapply advice like this.

[ Parent | on HN ]