problem with 'is zero or nonzero'



On 2013-10-23, Przemek Klosowski <przemek.klosowski at nist.gov> wrote:

> (Maxima 5.30.0 using Lisp SBCL 1.1.8-2 on Fedora 19)
>
> I guess it is a Maxima-wide problem with resolving constant conditions, 
> that I ran into back in July for integrate()
> and now with desolve().  Whenever Maxima asks 'Is ... zero or nonzero?' 
> both  'nonzero' and 'zero' are interpreted as 'zero'.
> I suspect the only way to specify non-zero is to say 'n':

I believe this bug has been fixed since 5.30. Can you please try it
again with the current version (5.31).

best

Robert Dodier