[clisp bug] assoc code fails *only* when compiled...

[D. G. <de...@gl...>]

[please excuse the format of the msg... i first attempted bugtrack,
then direct email.. then i learnt about that list, while the msg
bounced... so am fwding the msg here]
====================================================

Greetings

i was submitting a long report via sourceforge bugtracker, but
unfortunately, it lost all my huge write up, so am now rewriting it on
email.  Sorry for the inconvenience that i am not using the
bugtracker.


[1] Here's a small piece of code, which works great in lisp, compiles
fine, with no warnings or errors, but gives bizarre untraceable errors
when running the compiled code.  IMHO, either it should run fine when
compiled, or else---> it should break when uncompiled as well, and
should give warnings or errors when being compiled.  FWIW, franz's CL
runs this code just when even when compiled.  The code is:

(assoc (list 1 2) (list (list 1 2) 3) :test #'equal :test #'equal)


BTW, the error message was really even more bizarre for the way i had
actually implemeted the code ---- i had defined an assoc-equal --whcih
was like assoc, except that the default was equal.  Then, i had called
this assoc-equal with arguments :test #equal. 


[2] Also, i call clisp with -M 200M and -M 800M, but that seems to
have no effect on the stack size.. and i consistenly get a program
stack overflow --- i know it is not an infiniteloop---it is the '10th'
deepening of a fractal---and again, the code worked for me in Allegro's CL.



[3] By the way, thanks a lot for CLISP, clisp and the awesome
keybindings were love at first sight for me.  (even though i usually
run it from emacs)


[4] Are there any plans or thoughts on merging clisp and gcl?


Thanks,
DG				   
--