Berin Loritsch wrote:
Is there any compelling reason to have both a declared exception and a runtime
exception for the meta-model? It seems to me a mixing of methodologies, so
I would like to standardize on one way of doing things.
The runtime exceptions are used in the meta builders.
There are some method implementations that will not throw an exception from a logical point of - ie - the sort of thing that you typically comment and say "this will never happen". Rather than swallow these exception cases I prefer to throw a runtime exception. Basically the usage of runtime exceptions indicates errors outside of the anticipated scope.
Considering its use is limited to only a couple locations--namely the builders/readers would it make better sense to have a ModelBuilderRuntimeException or something like that? Maybe I am just being too sensitive about that, but having one ModelException gives the impression that it will always be declared--and having a more specific runtime exception closer to the builders gives a more realistic expectation of what is currently happening.
It's just a thought, and as I delve a little deeper in it, I will have a more detailed proposal/patch.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
