Camm Maguire wrote:
2) Paul, if *compile-verbose* defaults to t, must the output of compile-file
have
semi-colons?
From COMPILE-FILE:
If verbose is true, compile-file prints a message in the form of a comment
(i.e., with a leading semicolon) to standard output indicating what
Thank you, and my apologies for the question. I'm trying to hurry
this summer, and am using your wonderful tet suite largely as a
replacement for me having to read and parse the spec in detail
myself. I should have known that you'd get it right, but I just had
the nagging question that this
Greetings!
Page, Bill [EMAIL PROTECTED] writes:
Bob,
On Monday, June 27, 2005 7:45 AM you wrote:
I have gotten a preliminary *local* web-browser interface for
Axiom working. It uses pipes for communication. Get it here:
http://bob.mcelrath.org/moz-axiom.tar.gz
Un tar it,
Hello,
I am using GCL 2.6.6 on linux. I find that GCL
apparently can compute IEEE 754 special values,
but then it complains when the number is to be printed
on the console.
E.g. (* 1e300 1e300) succeeds, so far as I can tell,
and yields IEEE 754 infinity. However, then there is
an error
Greetings, and thanks! Fixed in CVS head, not yet tagging t3 until
other changes get in later. But at this burning moment, CVS head
works.
Take care,
Robert Boyer [EMAIL PROTECTED] writes:
The file md5.lisp is simply http://www.pmsf.de/pub/download/MD5/md5.lisp.
This bug does not arise in
Greetings! I could probably implement 'Inf' an 'NaN' as the print
forms of these float pretty trivially -- the question is whether the
reader must be modified to read them in, and what are the compliance
issues if any.
Take care,
Robert Dodier [EMAIL PROTECTED] writes:
Hello,
I am using
Greetings,, and thanks for your report!
Here is the patch you need:
Index: o/num_arith.c
===
RCS file: /cvsroot/gcl/gcl/o/num_arith.c,v
retrieving revision 1.18
diff -u -r1.18 num_arith.c
--- o/num_arith.c 14 Jun 2005 14:35:54
Camm Maguire wrote:
Thank you, and my apologies for the question. I'm trying to hurry
this summer, and am using your wonderful tet suite largely as a
replacement for me having to read and parse the spec in detail
myself. I should have known that you'd get it right, but I just had
the nagging
Hello Camm,
Greetings! I could probably implement 'Inf' an 'NaN' as the print
forms of these float pretty trivially -- the question is whether the
reader must be modified to read them in, and what are the compliance
issues if any.
Well, maybe some special symbols can be defined so
that
