#17502: fix interface to maxima.product
------------------------------+------------------------
Reporter: rws | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-6.5
Component: interfaces | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
------------------------------+------------------------
Comment (by nbruin):
Note that the same thing happens with
{{{
sage: maxima.sum(k,k,1,n).sage()
k*n
}}}
The problem is probably that these maxima routines aren't specially
wrapped, so sage probably generates the following maxima session
(roughly):
{{{
(%i1) sage0: k;
(%o1) k
(%i2) sage1: k;
(%o2) k
(%i3) sage2: 1;
(%o3) 1
(%i4) sage3: n;
(%o4) n
(%i5) product(sage0,sage1,sage2,sage3);
n
(%o5) k
}}}
Sage doesn't know that the parameter in the second slot is "special": it
needs to be a name, and maxima treats it as just a name. If we wrap
"product" as we do with "sum" the problem will go away. Plus, in the
process you'll see sums don't get evaluated via the string interface at
all.
--
Ticket URL: <http://trac.sagemath.org/ticket/17502#comment:1>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
