[Gcl-devel] Version_2_7_0t3

2005-07-08 Thread Camm Maguire
Production version: 2.6.6 (CVS tag Version_2_6_6) Testing version: (CVS tag Version_2_7_0t3) This is just a bundle of accumulated bug fixes -- no new compiler features, which I hope to be committing to CVS head in the next few days. Am checking the acl2 build now -- tagging anyway as it looks

[Gcl-devel] Re: (+ 2 . 3) = ?

2005-07-08 Thread Camm Maguire
Greetings, and thanks! Believe is fixed in just created tag t3. Take care, Robert Boyer [EMAIL PROTECTED] writes: Probably, just for compatibility with what the compiler does and with other implementations of Common Lisp, the interpreter's evaluation of (+ 2 . 3) should cause an error rather

[Gcl-devel] Re: bug in read?

2005-07-08 Thread Camm Maguire
Greetings, and thanks! Believe is fixed in just created tag t3. Take care, Robert Boyer [EMAIL PROTECTED] writes: Isn't it a bug in GCL's READ that #c(#c(1 2) 3) does not cause an error? I didn't see anything about this in ansi-tests, but I probably don't know how to search it very well.

[Gcl-devel] Re: Four ansi compliance bugs in GCL

2005-07-08 Thread Camm Maguire
Greetings, and thanks! Believe is fixed in just created tag t3. Take care, Robert Boyer [EMAIL PROTECTED] writes: Here are four bugs in GCL ANSI compliance, in the newest 2.7.0 ANSI. GCL causes an error on: (get-macro-character #\a nil) GCL causes an error on: (set-macro-character #\{

[Gcl-devel] Re: :print-object ansi compliance bug

2005-07-08 Thread Camm Maguire
Greetings, and thanks! Believe is fixed in just created t3. will test more tomorrow. Take care, Robert Boyer [EMAIL PROTECTED] writes: Though GCL 2.7.0 handles ok: (defstruct (bug (:print-function (lambda (rest x) (print foo t) it causes an error on (defstruct (bug

[Gcl-devel] Re: GCL File o/hasd.d

2005-07-08 Thread Camm Maguire
Greetings! Just checked into t3 -- only a few aethetic mods -- please feel free to provide feedback if I've messed something up. Take care, Warren A. Hunt Jr. [EMAIL PROTECTED] writes: Hi Camm, Do you feel comfortable enough with Boyer's and my update of GCL file o/hash.d to include it in

[Gcl-devel] Re: compiler no longer recognizes LIST type

2005-07-08 Thread Camm Maguire
Greetings! Before, the compiler saw it as T -- now we're passing and proagating much more type information. nested cons, list and symbol types are going into t4 with the sequence function acceleration stuff. Take care, Robert Boyer [EMAIL PROTECTED] writes: Somewhere after 2.6.6, the

[Gcl-devel] Re: :print-object ansi compliance bug

2005-07-08 Thread Camm Maguire
Greetings! I take it then this is is working for you -- great! There is an issue, at least for me, compiling acl2 with the profiling image -- the function name gets corrupted in TMP1.h -- havent' traced this yet. Am having troubles with :enable-eval T not allowing top level evals in breaks.

[Gcl-devel] Re: on incf

2005-07-08 Thread Paul F. Dietz
Camm Maguire wrote: Greetings! Paul, are there any overlapping types in Common Lisp neither of which is a subtype of the other? FIXNUM and UNSIGNED-BYTE (I assume you mean builtin types with type specifiers that are symbols.) Paul ___

[Gcl-devel] Re: printing IEEE 754 special values (inf, nan)

2005-07-08 Thread Robert Dodier
Hi Paul, thanks for your interest in this topic. You wrote: One property that is important: if *PRINT-READABLY* is true, then either NaN should print in a readable form (that is, in a form that, when read back in with the other reader/printer variables bound to the same values, produces a