Dear Robert,
Thank you very much for the quick fixes.
It works now. I've tested the similar changes to ctensor in my cvs tree, and
it's ok as well (I've replaced all inputs in sum codes from i to i%).
Valery
On Thursday 25 May 2006 14:52 about Re: [Maxima] itensor is broken, partly
Robert Dodier wrote:
> Valery, you wrote:
> > Are there any changes from 5.9.2 to cvs in "apply" code?
>
> The rules code was recently (post 5.9.3) modified so that
> there is a separate indication of rule match success apart
> from the match result. Otherwise it is impossible for false
> to be a match result.
>
> I've patched itensor.lisp so that the hard-coded rules $lc_u
> and $lc_l have the appropriate (return (values <foo> t)).
>
> I suppose we might consider reverting the rules to Maxima
> code, since Maxima rule declarations (defrule, etc) just
> construct Lisp functions pretty similar to $lc_u and $lc_l.
> It's not a big deal either way.
>
> Robert