The doubling of identity should have been corrected yesterday with [r13378]().
[r13378]: http://trac.common-lisp.net/armedbear/changeset/13378
Sent from my iPad
On Jul 7, 2011, at 1:37 PM, Alessio Stalla alessiostalla@gmail.com wrote:
On Thu, Jul 7, 2011 at 12:32 PM, Mark Evenson evenson@panix.com wrote:
On 7/7/11 11:07 AM, Chun Tian (binghe) wrote:
(defconstant a #.(make-array '(8 256) :element-type '(unsigned-byte 32) :initial-element 0))
Reproduced and filed [as ticket #156][1]
I don't know if it's related, but I noticed that the printing of some objects (at least CLOS objects and conditions) has been broken for some time. For example:
CL-USER(8): (car 12) #<THREAD "interpreter" {1A0283E}>: Debugger invoked on condition of type TYPE-ERROR The value 12 is not of type LIST. Restarts: 0: TOP-LEVEL Return to top level. [1] CL-USER(9): :bt
0: (SYSTEM:BACKTRACE) 1: (INVOKE-DEBUGGER #<TYPE-ERROR #<TYPE-ERROR {3B3219ED}> {3B3219ED}>) 2: org.armedbear.lisp.Lisp.error(Lisp.java:373) 3: org.armedbear.lisp.Lisp.type_error(Lisp.java:414) 4: org.armedbear.lisp.LispObject.car(LispObject.java:156) 5: org.armedbear.lisp.cxr$pf_car.execute(cxr.java:80) 6: org.armedbear.lisp.LispThread.execute(LispThread.java:636) 7: org.armedbear.lisp.Lisp.evalCall(Lisp.java:540) [1] CL-USER(10):
Note the #<TYPE-ERROR #<TYPE-ERROR {3B3219ED}> {3B3219ED}>
Alessio