<div class="gmail_quote">On 2 February 2012 11:18, Ethan Furman <span dir="ltr"><<a href="mailto:ethan@stoneleaf.us">ethan@stoneleaf.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">Implementation questions for the __NoException__ route:</div>
<br>
1) Do we want double underscores, or just a single one?<br>
<br>
I'm thinking double to mark it as special as opposed<br>
to private.<br></blockquote><div><br></div><div>Double and exposed allows someone to explicitly the __cause__ to __NoException__ on an existing exception. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2) This is a new exception class -- do we want to store the<br>
class itself in __context__, or it's instance? If its<br>
class, should we somehow disallow instantiation of it?<br>
<br>
3) Should it be an exception, or just inherit from object?<br>
Is it worth worrying about somebody trying to raise it, or<br>
raise from it?<br></blockquote><div><br></div><div>If it's not actually an exception, we get prevention of instantiation for free. My feeling is just make it a singleton object.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
4) Is the name '__NoException__' confusing?</blockquote><div><br></div><div>Seems perfectly expressive to me so long as it can't itself be raised.</div><div><br></div><div>Tim Delaney</div></div>