> I'm not sure what would be a reasonable way to handle an out of bounds > exceptions or an overflow even if it were catchable. It's not like a file not > found where we can expect user interaction behind.
For an HTTP server, output an error 500 and go on processing other requests (the point of Araq still stands). For anything with user interaction: would you prefer a calculator to display "number too large" or rather crash when you enter "2^2^500"? I really don't see why crashing can be an acceptable way to deal with errors
