Which Lisp for Windows if not GCL? WAS: foreign language patch for build-index+cl-ppcre branch
Subject: Which Lisp for Windows if not GCL? WAS: foreign language patch for build-index+cl-ppcre branch
From: Richard Fateman
Date: Sat, 26 Feb 2011 15:22:29 -0800
I suppose it may be better behaved, but not really satisfactory..
consider this:
In GCL,
(handler-case (f 100000)(error (x)(format t "~% handler-case caught
error ~s" x) 'boohoo))
results in this:
handler-case caught error #<CONDITIONS::INTERNAL-SIMPLE-STREAM-ERROR.0>
BOOHOO
In Allegro CL, it
results in this:
handler-case caught error #<synchronous-operating-system-signal @
#x221524ca>
boohoo
but in CCL we get this...
(handler-case (f 100000)(error (x)(format t "~% handler-case caught
error ~s" x) 'boohoo))
> Error: Stack overflow on value stack.
> While executing: F, in process listener(1).
> Type :POP to abort, :R for a list of available restarts.
> Type :? for other options
So CCL does not have error handling for this kind of error.
I don't know how this would affect the top-level listener loop, but I
think it would be bad.
There are many lisps that may not be quite ready for prime time...
RJF