Yigal Weinstein wrote:
> Alright as an end user I find it frustrating/traumatic that such errors
> are to be expected. I have recompiled the latest Maxima with GCL and
> removed the Maxima I compiled with CLISP. My question is, was there any
> way of expecting this error in CLISP or is it a complete fluke?
>
I think you'd have to ask the Clisp guys, but I would think it is a fluke.
> It seems so haphazard simplifying a simple trig. function and upon
> converting it to a float an error is produced, not just any error but an
> egregious one - this is somewhat traumatic as how can expect to use
> Maxima for any major programming let alone as a calculator?
>
As one who has had his fair share of stupid and not so stupid bugs, all
I can say is, "Bugs happen". No one does it on purpose, but they happen.
If this bug prevents you from using maxima, I suspect you will not be
satisfied with any program because they all have bugs. Perhaps you
won't find them, but what if you do?
Ray