Enforcing Component Constraints

[Cantor, Scott]

On 1/27/17, 2:47 PM, "dev on behalf of Brent Putman" <dev-bounces at shibboleth.net on behalf of putmanb at georgetown.edu> wrote:

>... in the meantime, if there is a bug in a caller, then your production code blows up, maybe even doing Something Bad(tm).

It's going to blow up either way unless we stop using unchecked exceptions, and in my mind one's the same as another.

Obviously if a null implies a nuclear weapon gets launched, no, but hey, Java's not allowed for that, says so right in the license.

In a world of unchecked errors, most of the time you either fall into a specifically defined error path or the process ends, I think that's normally an outcome that doesn't do anything but log the result and move on. Which stack frame you were in when it happened doesn't seem to matter that much.

-- Scott