Am Montag, den 08.12.2008, 17:24 -0600 schrieb Barton Willis:
> Things like this happen when the code tries to save time with things
> like (cons '(mtimes simp) l). Saving time this way isn't worth it--for
> one, it causes trouble with tellsimp & friends. It's best to keep
> expressions simplified at all times---you never know where an
> expression will be sent.
>
> Barton
> (who likely marked rtest 5 #48 as a bug :)
Ok, I see it.
I often have problems to formulate the correct results for the
testsuite. I will look more carefully at the results.
In a lot of places in the code I do not see what would be the right
simplification, we have mul, mul*, simplify, simplifya with the flag T
or NIL. Expressions with a simp-flag in it and more variations.
Furthermore we have a lot of macros or functions (perhaps hundreds) like
m+, gm, mlog, bess, sin%, ... which are only shortcuts, but do all
different simplifications too.
Perhaps a first step to get correct simplifications would be to have a
more simple style to program the simplification. Maybe one rule could be
that the simplification has to be done by the simplifier and not by hand
within the code.
Dieter Kaiser