I'm sorry, but if expand is broken, then expand and all of the code
relying on it should be updated.
I'm not going to fix expand (I don't know lisp). If someone does fix it,
fine. If nobody is up for the task, then I'd like for someone to comment
it out.
That's elementary engineering... don't build on broken components... ;-)
IMHO, the same thing apply to ev, if indeed it is broken.
The easiest way to improve Maxima, at this point, seems to be to remove
broken components. I appreciate Richard's comments "rule 1. don't
use...", but I think it is a mistake to setup such rules. You are much
better off disabling it in the software. Period.
If there is a workaround, then let's apply the workaround and be done
with these problems.
These bugs have major impacts on the usability of Maxima. This cost is
much higher than the one time cost of doing a search and replace in some
old code (expand-> rat).
Let's cut the fat out!!!
Tuukka Toivonen wrote:
>On Mon, 4 Feb 2002, Daniel Lemire wrote:
>
>>I propose that expand be removed, or fixed. I suspect that if nobobody
>>wants to fix it, the easier path would be to remove it (which I suspect
>>
>
>If it'd be removed, old code relying on it would break.
>I don't recommend.
>
>Has the expand worked before? I assume so, so what has caused it
>to break? (This isn't an user error, or is it? I didn't follow
>the thread closely).
>
>