[squeak-dev] Clearing the changes file
tapplek at gmail.com
Mon Aug 18 15:49:24 UTC 2008
On Mon, Aug 18, 2008 at 05:21:58PM +0200, Thomas Kowark wrote:
> Hi all,
> I am currently developing an application that continuously creates and deletes methods on its own. This, however, leads to the changes file exceeding the limits of what Squeak can handle. The error message tells me to take "some actions", but unfortunately I'm not quite sure, what to do now. I have renamed the changes file as a first fix, but this leads to errors upon startup. So does anybody know what might be the best solution here?
> Secondly, I wanted to ask if it is possible to prevent changes of methods that match certain naming patterns from being written to the changes file?
--------- The best way: -----------------
I assume you are using something like this?
aClass compile: 'aMethod ^ aValue' classified: #autogen
use the longer version:
aClass compile: 'aMethod ^ aValue' classified: #autogen withStamp: 'autogen' notifying: nil logSource: false
The important bit is logSource: false. It is true by default. If
you do this, your methods will have no source code, and will
have to be decompiled. Check the implementation of
compile:classified: to see how it fills in the other parameters.
----------- the next best way: -----------
You can disable the preference general >
warnIfNoChangesFile, then delete the .changes file.
This will mean that many methods in your system will not have
source code, only those methods unchanged since the creation of
the .sources file. This most definitely means methods you
created will have no source code.
> kind regards,
> Thomas Kowark
> GMX Kostenlose Spiele: Einfach online spielen und Spaß haben mit Pastry Passion!
Matthew Fulmer -- http://mtfulmer.wordpress.com/
More information about the Squeak-dev