<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br style="font-size: 17px; "><div style="font-size: 17px; "><div>On Dec 1, 2009, at 7:55 AM, Brain, Jim wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>If you have a listener concept in v4 and will pass the errors to the listener, it seems to me that someone who needs Exceptions can just throw the exception in the listener.</div></blockquote><div style="font-size: 17px; "><br></div>That's true. they can decide what's fatal. i'll have to pass more info to the listener this way though and can't manage a bitset of what to pay attention to.</div><div style="font-size: 17px; "><br><blockquote type="cite"><div>Is it common in systems to have a "conditional Exception system" like this, where the same conditions may or may not throw Exceptions depending on some configuration setting? If so, I'm unfamiliar with it. From a language perspective, I much prefer Exceptions either be "always" or "never", not "optional"<br></div></blockquote></div><br style="font-size: 17px; "><div><font class="Apple-style-span" size="5"><span class="Apple-style-span" style="font-size: 17px;">Well, in many ways it's a way to specify language semantics depending on your situation. Some rely on <a.b> being valid when b doesn't exist. Some people consider it a programming error. Both use cases are valid. </span></font></div><div><font class="Apple-style-span" size="5"><span class="Apple-style-span" style="font-size: 17px;"><br></span></font></div><div><font class="Apple-style-span" size="5"><span class="Apple-style-span" style="font-size: 17px;">As u say, maybe pass everything to listener and it can decide...</span></font></div><div><font class="Apple-style-span" size="5"><span class="Apple-style-span" style="font-size: 17px;"><br></span></font></div><div><font class="Apple-style-span" size="5"><span class="Apple-style-span" style="font-size: 17px;">Ter</span></font></div></body></html>