<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">
Hi Christoph --<div><br></div><div>> [...] <span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">with this preference enabled [...]</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px"><br></span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">You mean "disabled", I suppose. I fixed that code loading via MethodAddition in Monticellop-mt.765.</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px"><br></span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Best,</span></div><div><span style="font-family: Arial, Helvetica, sans-serif;font-size: 13px">Marcel</span></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 10.01.2022 17:58:10 schrieb christoph.thiede@student.hpi.uni-potsdam.de <christoph.thiede@student.hpi.uni-potsdam.de>:</p><div style='font-family:Arial,Helvetica,sans-serif'>
Hi Marcel, Tim, all,<br>
<br>
with this preference enabled, I would have expected that I would be able to perform all common code management operations in an image that has no access to the changes file. However, here are some things that still fail under this circumstance:<br>
<br>
* load/merge a Monticello version - MethodAddition>>#createCompiledMethod does not honor AcceptsLoggingOfCompilation, and neither does MCMethodDefinition>>#asMethodAddition.<br>
* re-classifying methods in a browser (or renaming a category)<br>
<br>
See also all senders to #logMethodSource:forMethodWithNode:inCategory:withStamp:notifying:. I wonder whether this method should check AcceptsLoggingOfCompilation itself, or whether we need to make all senders aware of that preference. It would be really great to be able to open multiple instances of an image in parallel for throwaway experiments. :-)<br>
<br>
Best,<br>
Christoph<br>
<br>
<span style="color: #808080">---<br>
</span><span style="color: #808080"><i>Sent from </i></span><span style="color: #808080"><i><a href="https://github.com/hpi-swa-lab/squeak-inbox-talk"><u><font color="#808080">Squeak Inbox Talk</font></u></a></i></span><br>
<br>
On 2022-01-03T18:44:06+01:00, christoph.thiede@student.hpi.uni-potsdam.de wrote:<br>
<br>
> Fantastic! I'm already looking forward to make use of this in my TelegramSmalltalkBot! :-)<br>
> <br>
> Until then, I wonder whether we should write method changes to the #source attribute of the compiled method in question so that you do not loose your temp names after accepting when the change file is unavailable. See CompiledMethod >> #getSourceFor:in:. What do you think? :-)<br>
> <br>
> Best,<br>
> Christoph<br>
> <br>
> ---<br>
> Sent from Squeak Inbox Talk<br>
> <br>
> On 2021-12-26T07:21:46+00:00, commits at source.squeak.org wrote:<br>
> <br>
> > Marcel Taeumel uploaded a new version of Kernel to project The Trunk:<br>
> > http://source.squeak.org/trunk/Kernel-mt.1437.mcz<br>
> > <br>
> > ==================== Summary ====================<br>
> > <br>
> > Name: Kernel-mt.1437<br>
> > Author: mt<br>
> > Time: 26 December 2021, 8:21:42.050619 am<br>
> > UUID: 28086a0b-8543-4f44-9c9f-7e63d3028f7f<br>
> > Ancestors: Kernel-ct.1436<br>
> > <br>
> > Makes #acceptsLoggingOfCompilation a preference that can be disabled. See commentary #logCompiledSources. Classes can still override this preference but should follow a "super acceptsLoggingOfCompilation and: [...]" pattern.<br>
> > <br>
> > Thanks to Tim (tpr) for figuring out the mechanics and testing it throughout the year!<br>
> > <br>
> > =============== Diff against Kernel-ct.1436 ===============<br>
> > <br>
> > Item was changed:<br>
> > Behavior subclass: #ClassDescription<br>
> > ????instanceVariableNames: 'instanceVariables organization'<br>
> > + ????classVariableNames: 'AcceptsLoggingOfCompilation TraitImpl'<br>
> > - ????classVariableNames: 'TraitImpl'<br>
> > ????poolDictionaries: ''<br>
> > ????category: 'Kernel-Classes'!<br>
> > <br>
> > !ClassDescription commentStamp: '<historical>' prior: 0!<br>
> > I add a number of facilities to basic Behaviors:<br>
> > ????Named instance variables<br>
> > ????Category organization for methods<br>
> > ????The notion of a name of this class (implemented as subclass responsibility)<br>
> > ????The maintenance of a ChangeSet, and logging changes on a file<br>
> > ????Most of the mechanism for fileOut.<br>
> > ????<br>
> > I am an abstract class, in particular, my facilities are intended for inheritance by two subclasses, Class and Metaclass.<br>
> > <br>
> > The slots 'organization' and 'methodDict' should ONLY be accessed by message in order for things to work during ImageSegment>>discoverActiveClasses (q.v.).!<br>
> > <br>
> > Item was added:<br>
> > + ----- Method: ClassDescription class>>logCompiledSources (in category 'compiling') -----<br>
> > + logCompiledSources<br>
> > + ????<preference: 'Log compilations to changes file'<br>
> > + ????????category: 'general'<br>
> > + ????????description: 'If enabled, the code being compiled will get logged to the changes file. Disabling allows loading code with no changes file in use. See also #warnIfNoChangesFile and #warnIfNoSourcesFile and #readDocumentAtStartup. You can configure a silent image/DoItFirst for, e.g., server environments.'<br>
> > + ????????type: #Boolean><br>
> > + <br>
> > + ????^ AcceptsLoggingOfCompilation ifNil: [true]!<br>
> > <br>
> > Item was added:<br>
> > + ----- Method: ClassDescription class>>logCompiledSources: (in category 'compiling') -----<br>
> > + logCompiledSources: aBoolean<br>
> > + ????^ AcceptsLoggingOfCompilation := aBoolean!<br>
> > <br>
> > Item was changed:<br>
> > ----- Method: ClassDescription>>acceptsLoggingOfCompilation (in category 'compiling') -----<br>
> > acceptsLoggingOfCompilation<br>
> > ????"weird name is so that it will come lexically before #compile, so that a clean build can make it through. 7/7/96 sw"<br>
> > <br>
> > + ????^AcceptsLoggingOfCompilation ifNil: [true]!<br>
> > - ????^ true!<br>
> > <br>
> > <br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20220103/35319af7/attachment.html><br>
> <br>
>
</div></blockquote>
</div></body>