Hi,
there are apparently 3 bugs in db.lisp, that generate a compiler
warning in CMUCL and SBCL. Here is what I see in my compile log:
File: /home/are/maxima/src/db.lisp
; In: DEFUN QUEUE+P
; (LOGIOR +LAB-HIGH-BIT+ (UNLAB LAB))
; ==>
; (LOGIOR C::Y -536870912)
; Warning: Result is a (INTEGER -536870912
; -1), not a (VALUES &OPTIONAL LIST &REST T).
;
; In: DEFUN QUEUE-P
; (LOGIOR +LAB-HIGH-BIT+ (UNLAB LAB))
; ==>
; (LOGIOR C::Y -536870912)
; Warning: Result is a (INTEGER -536870912
; -1), not a (VALUES &OPTIONAL LIST &REST T).
;
; In: DEFUN MARK+3
; (DBV (+LABZ #) (-LABZ #))
; Warning: Result is a INTEGER, not a (VALUES &OPTIONAL LIST &REST T).
In the first 2 cases the warning could be eliminated by wrapping
the logior in a copyn call, like a few lines up.
And in the 3rd case, maybe the unlab around the dbv call is wrong.
But I am not really sure, if this is right, because the code is
very hard to understand :-(
Does anyone on the list know more about these issues?
Thanks,
'Andreas
--
ceterum censeo redmondinem esse delendam.