[Openmcl-devel] Question about 'process-interrupt run on exhausted process'
gb at clozure.com
Sat Feb 10 23:58:02 EST 2007
On Sat, 10 Feb 2007, Denis Bueno wrote:
> On 2/10/07, Gary Byers <gb at clozure.com> wrote:
> [snip detailed and useful explanation]
>> This all had something of a familiar ring to it; according to a terse
>> comment in the bleeding-edge CVS logs, I did make that change shortly
>> after 1.0 was released, but never backported it to 1.0.
>> For 1.0, I -think- that it'd be safe to simply remove the check
>> in PROCESS-INTERRUPT (in ccl/level-1/l1-processes.lisp); in this context,
>> the check leads to an error that amounts to "I can't kill this dead
> Does this mean that one can expect the next release (FSVO "next") to
> have this problem fixed?
Yes, it's been fixed in the 1.1-prereleases since October of 2005.
> This issue pretty much means if I release I would have to compile my
> own OpenMCL and bundle it with whatever I release, should I choose to
> use OpenMCL, right?
You can basically bundle a patch as part of what you distribute; something
(let* ((ccl:*warn-if-redefine-kernel* nil)) ; quietly redefine built-in
(defun ccl:process-interrupt (....)
> Thanks for the explanation.
More information about the Openmcl-devel