--- Raymond Toy <raymond.toy@ericsson.com> wrote:
> To be honest, I use CMUCL's DESCRIBE function a lot to figure out
> where, say diff is defined. Then I also use (lisp) trace a lot to
> watch what's happening. And lots of debugging print statements
> everywhere. :-(
>
> Ray
Ah, the lisp trace. I've been meaning to go back and find the examples
of complete traces people have done in Maxima (and I think one or two
in Macsyma from Dr. Fatemen) and write up how that is done for the
debugging section of the Maxima book. And then figure out if SLIME
would be of any help (I think the weirdness of things like defmfun
limits SLIME's abilities somewhat - at least the one time I tried
SLIME+Maxima I couldn't get its xref abilities to do much that was
interesting - but darn it it seems like getting it to work would be a
Good Thing.) The current debugging section has nothing, and it is a
section that would probably be a profitable one to create :-). Is
there any "Maxima debugging howto" or some such I could start with?
Also useful would be an example of a tricky problem that has been
debugged as a sort of "test problem" for SLIME - i.e. the bug could be
reintroduced and then hunted.
CY
__________________________________
Do you Yahoo!?
The all-new My Yahoo! - Get yours free!
http://my.yahoo.com