[Openmcl-devel] Listener spawning (tiny problem)
plkrueger at comcast.net
Tue Sep 7 06:03:17 PDT 2010
FWIW, I haven't upgraded in a while and can't seem to duplicate this in 1.6-dev-r13776M-trunk (DarwinX8664).
On Sep 7, 2010, at 6:39 AM, Arthur Cater wrote:
> Data point: My trunk is 1.6-dev-r14216M-trunk and it happens there already.
> IMHO Inspect is irrelevant.
> On Sep 6, 2010, at 9:17 PM, Alexander Repenning wrote:
>> confirmed. It's pretty annoying.
>> On Sep 6, 2010, at 1:56 PM, Tim Bradshaw wrote:
>>> Under circumstances I don't understand but which may have to do with using the inspector, Hemlock seems to decide that it needs a new listener window when you compile a new definition. It will then use this window for a while until something causes it to decide it needs another one. I tend to start killing them off when it gets to three or four, in case they reach some kind of criticality.
>>> I think the way to replicate this is:
>>> - write a definition in Hemlock
>>> - Compile it with C-XC-C
>>> - (inspect *) in the listener
>>> - write and compile another definition, which will spawn a listener.
>>> I'm on the trunk and I've just updated to 14232, which is current. On Snow Leopard.
>>> Openmcl-devel mailing list
>>> Openmcl-devel at clozure.com
>> Prof. Alexander Repenning
>> University of Colorado
>> Computer Science Department
>> Boulder, CO 80309-430
>> vCard: http://www.cs.colorado.edu/~ralex/AlexanderRepenning.vcf
>> Openmcl-devel mailing list
>> Openmcl-devel at clozure.com
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openmcl-devel