string comparisons, was: Maxima 5.21.1 release



On Mon, Apr 26, 2010 at 9:37 AM, Stavros Macrakis <macrakis at alum.mit.edu> wrote:

> You are saying that is(%i>0)=>false is not a bug?

Is it really a problem if a > b and b > a are both false?
(It seems likely that Maxima assumes one is true if the other
is false, but it doesn't have to be that way, does it?)

Be that as it may, I would be willing to accept the same behavior
for is(%i > 0) and is("x" > 0) which is now displayed by
is(a > 0) where a is a list, matrix, or set, namely, it returns
unknown when prederror = false and triggers and error when
prederror = true.

> A related bug is is(%i+1>%i) => true

Yeah, that looks like a bug to me.

Robert Dodier