AFAICS bug #157 really is about confusing printouts. Namely, both with
Axiom from December 2004 and current build-improvements I get:
)lisp (setq *miss* t)
x
<snip>
getdatabase call: Variable CONSTRUCTORMODEMAP
getdatabase miss: CONSTRUCTORMODEMAP Variable
This output is "as expected": reporting of database calls prints
constructor first and attribute second, printing of database misses uses
the opposite order. To avoid confusion we probably should use the same
order in both printouts (if you think that we should correct the printout
I will prepare a patch).
--
Waldek Hebisch
[EMAIL PROTECTED]
_______________________________________________
Axiom-developer mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/axiom-developer
