<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I agree that we shouldn't be using Error for everyday occurrences such as syntax errors in MDX. Errors are for unrecoverable system issues such as OutOfMemory.<div><br></div><div>The TokenMgrError class is generated by JavaCC. We didn't have a choice. But I believe that it is handled each time it is thrown.<div><br></div><div>Julian</div><div><br><div><div>On Mar 29, 2012, at 4:32 AM, Paul Stoellberger wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I just encountered a parser Exception that would throw a TokenMgrError, and I was wondering why you would use Error instead of Exception?<div>It kinda messes up my exception handling a bit (which I can adapt, but just wondered why you chose Error over Exception)</div><div><br></div><div>And is there any other point where you chose Error over Exception that I need to be aware of?</div><div><br></div><div>-Paul</div><div><span class="Apple-style-span" style="font-size: 11px; font-family: Monaco; "><br></span></div></div>_______________________________________________<br>Mondrian mailing list<br><a href="mailto:Mondrian@pentaho.org">Mondrian@pentaho.org</a><br>http://lists.pentaho.org/mailman/listinfo/mondrian<br></blockquote></div><br></div></div></body></html>