There are a lot of things that are wrong with the code. I tried pretty hard to think of a good usage for why you’d use this instead of wrapping in a try/catch and the only thing I could really think of was if you have multiple entry points in your code but you want uncaught exceptions to be handled the same way through all of them. This is slightly more elegant, in this scenario, then making an class that you pass exception information to, and catching Throwable in all of your entry points, then passing it to that class.

But yes, it does break the principle of encapsulation to a great extent (which is what the globals issue is about). I definitely wouldn’t recommend this in place of more traditional solutions except for a few very specific issues.

I’m not making the post like a “hey, look at this cool feature” but a “hey, look at this feature that nobody seems to be talking about.” I certainly have no intention of using it.

Also, it occurs to me anyone who’s not already wrapping the body of their main() or run() inside a try/catch is the sort of lazy pig who wouldn’t piss on their own leg if it were on fire, and so I’m not sure how giving them a different method to ignore really heals the World’s Pain.