#7661: maxima interface gives precedence to function dictionary instead of local
variables
--------------------------+-------------------------------------------------
Reporter: burcin | Owner: was
Type: defect | Status: new
Priority: major | Milestone: sage-4.3.2
Component: interfaces | Keywords: maxima
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
--------------------------+-------------------------------------------------
Comment(by eigenlambda):
sage: d = var('delta')
sage: e = d._maxima_()
sage: sage.calculus.calculus.symbolic_expression_from_maxima_element(e)
dirac_delta
somewhere in symbolic_expression_from_maxima_element(), the string from
maxima is looked up in sage.calculus.calculus._syms, which by default has
'delta': dirac_delta . So this is what's happening, next, SR() barfs on
trying to turn dirac_delta into a symbolic expression, at which point
people who just wanted their variable 'delta' back get confused and
frustrated.
sage: del sage.calculus.calculus._syms['delta']
sage: sage.calculus.calculus.symbolic_expression_from_maxima_element(e)
delta
That may not be such a good idea, however, since what sage calls
dirac_delta, maxima refers to as delta. Nevertheless, since
reset('delta') appears to remove delta from that dictionary, perhaps
var('delta') should also do so?
Of course, what happens when someone does a Laplace transform with delta
as a sage variable will then come out confusing and wrong. At least the
current behavior is merely broken.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7661#comment:2>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
