[Openmcl-devel] with-autorelease-pool question

[Phil]

Then the problem may be related my access method (i.e. SLIME) as I  
had hundreds (thousands?) of 'just leaking' messages and it took a  
reboot to clean up the swap files.  Any pointers on what SLIME would  
need to do to avoid this issue?  I was under the impression that  
SLIME was just a wrapper around the initial REPL but it sounds like  
there may be more going on than that.

On Aug 22, 2006, at 12:54 AM, Gary Byers wrote:

> Both the initial listener thread (e.g., the one created when the lisp
> was started from the command-line/emacs/etc.) and any Cocoa listeners
> that're created should have their own autorelease pools.  Temporary
> (autoreleased) objects just collect in those pools, but there are
> colon-commands that're supposed to allow you to manually clean things
> up every now and then.  (I don't remember exactly what the commands
> are, but doing :? from a REPL in the Cocoa environment should show
> you.)
>
>
>
> On Tue, 22 Aug 2006, Phil wrote:
>
>> Can a top-level with-autorelease-pool be implemented in OpenMCL for
>> interactive development?  A call around the top-level application
>> code does the trick once all the code is done but I'm wondering more
>> about doing this for REPL work where I am calling into any number of
>> entry points and don't want to wrap every function/method 'just in
>> case.'  (just rebooted as I forgot to do this for some code over the
>> last few days... ;-)
>> _______________________________________________
>> Openmcl-devel mailing list
>> Openmcl-devel at clozure.com
>> http://clozure.com/mailman/listinfo/openmcl-devel
>>
>>