Re: understanding GC
Julian Bradfield <jcb+xeb(a)jcbradfield.org> writes:
>Julian Bradfield <jcb+xeb(a)jcbradfield.org> writes:
>>>It allocates. If there's not enough free space in the heap to satisfy
>>>an allocation, a GC is triggered.
>> The manual clearly says "this is _not_ the case".
>What is not the case?
That allocation can trigger a GC - in the sense of running a GC
immediately.
Allocation as such does not cause a GC within the code of concat(),
though it may cause the reserve to drop such that GC happens next time
GC is possible.
Sorry, I was very unclear in my choice of words:
The allocation may eventually lead to a GC happening. A superficial
look over concat indeed revealed no possibilities for QUIT or explicit
GC, but I'm assuming the author was trying to be safe rather than sorry.
GCPROs are much easier to add while writing the code, as opposed to
putting them in afterwards, so I'd say the choice was prudent.
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta