<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">
Ah, nevermind. You wanted to remove all those "Smalltalk classNamed:" references from SystemOrganizer. :-)<div><br></div><div>Best,</div><div>Marcel</div><div class="mb_sig"></div><blockquote class='history_container' type='cite' style='border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;'>
<p style='color: #AAAAAA; margin-top: 10px;'>Am 29.03.2021 10:43:07 schrieb Tony Garnock-Jones <tonyg@leastfixedpoint.com>:</p><div style='font-family:Arial,Helvetica,sans-serif'>I noticed this, btw, removing a system category from a non-default
<br>environment, only to find the classes in Smalltalk were removed :-)
<br>
<br>
<br>
<br>On 3/29/21 10:42 AM, Tony Garnock-Jones wrote:
<br>> On 3/29/21 10:36 AM, Marcel Taeumel wrote:
<br>>> I suppose that the idea was that every environment has its own system
<br>>> organization.
<br>>
<br>> Exactly. They already do: but the problem is that doing anything with
<br>> the resulting SystemOrganizer resulted in changes to *Smalltalk
<br>> globals*! So this allows the per-Environment organizers to scope their
<br>> effects correctly.
<br>>
<br>>> By adding a back reference from organization to environment, there is
<br>>> still no support of "multiple" environments. Do you plan to change
<br>>> this dynamically? If so, why? :-) Would you sketch an example?
<br>>
<br>> It wouldn't change dynamically: instead, it is set at construction time.
<br>> See related change Environments-tonyg.80.
<br>>
<br>> Regards,
<br>> Tony
<br>>
<br></div></blockquote>
</div></body>