<div dir="ltr">Juan,<div><br></div><div>Thanks, that will keep me going for now.</div><div><br></div><div>Phil</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Oct 19, 2019 at 4:00 PM Juan Vuletich <<a href="mailto:juan@jvuletich.org">juan@jvuletich.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u>

  
    
  
  <div bgcolor="#ffffff">
    On 10/17/2019 5:35 PM, Phil B wrote:
    <blockquote type="cite">
      <div dir="ltr">
        <div dir="ltr">Juan,</div>
        <br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">On Thu, Oct 17, 2019 at 1:08
            PM Juan Vuletich <<a href="mailto:juan@jvuletich.org" target="_blank">juan@jvuletich.org</a>>
            wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div bgcolor="#ffffff"> Hi Phil,<br>
              <br>
              On 10/17/2019 2:31 AM, Phil B wrote:<br>
              <blockquote type="cite">
                <div dir="ltr">
                  <div>
                    <div class="gmail_quote">
                      <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
                        <div bgcolor="#ffffff"> My changes do two
                          things. One is to avoid non local returns in
                          handler blocks. The other one is about a few
                          places where you did [ :exception | exception
                          signal ] as the signal handler. Exceptions can
                          only be signaled once! I changed them to do [
                          :exception | exception pass ]. This was
                          breaking the exception system if the recent
                          changes were loaded.<br>
                        </div>
                      </blockquote>
                      <div><br>
                      </div>
                      <div>1) Would you be opposed to a #nonLocalReturn:
                        method on Exception?  That seems to me a cleaner
                        and clearer way of doing this.  It's also more
                        consistent with how Exception deals with the
                        other scenarios.</div>
                    </div>
                  </div>
                </div>
              </blockquote>
              <br>
              I think #nonLocalReturn: would be ok. Maybe a better name
              could be #methodReturn:<br>
              <br>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>Attached (along with exception recycling).  This was too
            easy... what did I miss?</div>
          <div><br>
          </div>
          <div>Thanks,</div>
          <div>Phil</div>
        </div>
      </div>
    </blockquote>
    <br>
    Hi Phil,<br>
    <br>
    I just pushed a change that allows for exception recycling without
    an explicit call. The signaling context is reset after handling.<br>
    <br>
    The change set also adds a couple of preferences to control allowing
    of non-local returns in handlers, and the warning shown in the
    Transcript.<br>
    <br>
    Thanks,<br>
    <pre cols="72">-- 
Juan Vuletich
<a href="http://www.cuis-smalltalk.org" target="_blank">www.cuis-smalltalk.org</a>
<a href="https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev" target="_blank">https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev</a>
<a href="https://github.com/jvuletich" target="_blank">https://github.com/jvuletich</a>
<a href="https://www.linkedin.com/in/juan-vuletich-75611b3" target="_blank">https://www.linkedin.com/in/juan-vuletich-75611b3</a>
@JuanVuletich</pre>
  </div>

</blockquote></div>