<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    Hi Phil, Folks,<br>
    <br>
    On 10/13/2019 9:25 PM, Phil B wrote:
    <blockquote
cite="mid:CAMJMOehPrJ_OvxwEtr59uoBSqfoDrh+xRDDXEuHwhnAe9VWgLQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">Just did a quick look at senders of #on:do: and
        found these:
        <div><br>
          <div>AndreasSystemProfiler>canWork</div>
          <div>Browser>contents:notifying:</div>
          <div>FeatureRequirement>require</div>
          <div>FeatureRequirement>satisfyRequirementsAndInstall</div>
          <div>MethodNode>generatePreSpur:using:</div>
          <div>MethodNode>generateSpur:using:</div>
          <div>RefactoringApplier>createAndValueHandlingExceptions:</div>
          <div>SmalltalkEditor>renameTemporary:</div>
          <div>SmalltalkEditor>withClassDefinitionNodeAndClassDo:ifErrorsParsing:</div>
          <div>SmalltalkEditor>withMethodNodeAndClassDo:ifErrorsParsing:</div>
          <div>SystemDictionary>okayToSave</div>
          <div><br>
          </div>
          <div>That's ~15% of #on:do: senders in the base image
            *directly* returning within the block.  (i.e. I didn't check
            any of the blocks passed as parameters which might also do
            so or any of the other ways this might occur)  I don't think
            this change is fully baked...</div>
          <div><br>
          </div>
        </div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Sun, Oct 13, 2019 at 8:00
          PM Phil B <<a moz-do-not-send="true"
            href="mailto:pbpublist@gmail.com">pbpublist@gmail.com</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 dir="ltr">It looks like we have at least some changes in
            the core image to resolve.  World menu->Save as... now
            fails.  Has a scan of the image been done to identify where
            these cases might be buried?</div>
          <br>
        </blockquote>
      </div>
    </blockquote>
    <br>
    I pushed these changes without fully analyzing their consequences,
    and without appropriate discussion. I should have discussed this
    with fellow co-maintainer Hernán and Andrés who saw the issue and
    suggested the solution some months ago. This most likely annoyed you
    all. <br>
    <br>
    I take responsibility for this error, and apologize for this.<br>
    <br>
    More comments in other responses to this thread.<br>
    <br>
    Thanks for your patience.<br>
    <pre class="moz-signature" cols="72">-- 
Juan Vuletich
<a class="moz-txt-link-abbreviated" href="http://www.cuis-smalltalk.org">www.cuis-smalltalk.org</a>
<a class="moz-txt-link-freetext" href="https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev">https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev</a>
<a class="moz-txt-link-freetext" href="https://github.com/jvuletich">https://github.com/jvuletich</a>
<a class="moz-txt-link-freetext" href="https://www.linkedin.com/in/juan-vuletich-75611b3">https://www.linkedin.com/in/juan-vuletich-75611b3</a>
@JuanVuletich</pre>
  </body>
</html>