Confused by behavior of LispWorks for code snippet
- From: Damien Kick <dkixk@xxxxxxxxxxxxx>
- Date: Sat, 29 Sep 2007 23:10:17 -0500
With LispWorks Personal Edition 5.0.1 (PowerPC), I see the following behavior:
<code>
CL-USER 1 > (defparameter *x* #'(lambda () 13))
*X*
CL-USER 2 > *x*
#<anonymous interpreted function 200EB012>
CL-USER 3 > (setf (symbol-function 'f) *x*)
#<anonymous interpreted function 200EB012>
CL-USER 4 > (setf (symbol-function 'g) *x*)
#<anonymous interpreted function 200EB012>
CL-USER 5 > (eq #'f #'g)
NIL
CL-USER 6 > (eql #'f #'g)
NIL
CL-USER 7 > (eql #'f *x*)
NIL
CL-USER 8 > (eq *x* *x*)
T
</code>
I would've expected (EQ #'F #'G) => T. I am getting that result, i.e. (EQ #'F #'G) => T, with both Allegro CL 8.0 and Clisp. Is LispWorks mistaken or is that an allowable result?
.
- Follow-Ups:
- Re: Confused by behavior of LispWorks for code snippet
- From: Barry Margolin
- Re: Confused by behavior of LispWorks for code snippet
- From: Kent M Pitman
- Re: Confused by behavior of LispWorks for code snippet
- From: Carl Taylor
- Re: Confused by behavior of LispWorks for code snippet
- From: Tobias C. Rittweiler
- Re: Confused by behavior of LispWorks for code snippet
- From: Klaus Harbo
- Re: Confused by behavior of LispWorks for code snippet
- From: Rob Warnock
- Re: Confused by behavior of LispWorks for code snippet
- Prev by Date: ACL:AllegroCache philosophical question
- Next by Date: Re: ACL:AllegroCache philosophical question
- Previous by thread: ACL:AllegroCache philosophical question
- Next by thread: Re: Confused by behavior of LispWorks for code snippet
- Index(es):