<div dir="ltr"><div class="gmail_default" style="font-size:small">Hi All,</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">  I've just run into what I think is a bad mistake.  My understanding of Symbol class>>findInterned: is that it answers a Symbol if its (string) argument already exists as a Symbol, and answers nil otherwise.  Indeed looking at Collections-mt.935, 13 April 2021, this is the case:</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Symbol class>><b>findInterned:</b>aString<br><br>    self hasInterned:aString ifTrue:[:symbol| ^symbol].<br>    ^nil.<br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">In Collections-nice.936,13 April 2021 it was deprecated, but the new method in 60Deprecated-nice.95, 13 April 2021 reads:</div><br>Symbol class>><b>findInterned:</b>aString<br> <span class="gmail_default" style="font-size:small">    </span>self flag: #deprecated. "use lookup: instead, they are synonym"<br>    <span class="gmail_default" style="font-size:small">    </span>^self lookup: aString<div><br></div><div><div class="gmail_default" style="font-size:small">But lookup: *always* interns:</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Symbol intern: 'union {<br>                                                           sqIntptr_t valword;<br>                                                           struct { int low, high; } valleint64;<br>                                                         struct { int high, low; } valbeint64;<br>                                                         double valflt64;<br>                                                              struct { void *addr; sqIntptr_t size; } valstruct;<br>                                                    }' #'union {<br>                                                          sqIntptr_t valword;<br>                                                           struct { int low, high; } valleint64;<br>                                                         struct { int high, low; } valbeint64;<br>                                                         double valflt64;<br>                                                              struct { void *addr; sqIntptr_t size; } valstruct;<br>                                                    }' <br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">So I think it is *urgent* that we undeprecate findInterne3d: and restore its old meaning.  I apologixze for not finding this earlier.  i just ran VMMaker today after an update and that triggered the bug for the first time.  I'm guessing the update flushed symbols.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">I'm going to make this change now.</div><br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><span style="font-size:small;border-collapse:separate"><div>_,,,^..^,,,_<br></div><div>best, Eliot</div></span></div></div></div></div></div>