> > the second time solver is invoked, it is silently assumed
> > that l is an integer.
> This has to do with solve setting the integer property of L,
> when it asked. It is the way maxima works. You can remove
> this property with remove.
I consider this to be a bug, even if it's the way Maxima has worked for
30 years. The scope of assumptions based on interactive queries by
Asksign ("Is ... positive, negative, or zero?") is the current
interaction; the same should be true of property assumptions ("Is ... an
integer/even number/...?"). I realize that internally they are
completely distinct databases, but that shouldn't be the user's concern.
That said, Maxima could certainly be more sophisticated about all this,
e.g. carrying assumptions along with the resulting expressions, but
that's another story. For now, it would be nice if it would just be
consistent.
-s