#8734: make sage variables unique in maxima
-------------------------------------+-------------------------------------
Reporter: jason | Owner: jason
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.3
Component: interfaces | Resolution:
Keywords: | Merged in:
Authors: Jason Grout, Ralf | Reviewers: Volker Braun, Paul
Stephan | Zimmerman, Karl-Dieter Crisman
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/rws/ticket/8734-1 | a195985c0617bf14a5d644f5c065bea896340ce4
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by rws):
After studying this in detail, the reason why the last change makes no
difference is the following: in `desolve` and `desolve_laplace` the
translation to Maxima is applied several times using `maxima()?` and `P()`
(which is the parent of the first translation result, i.e. of a Maxima
expression). `P()` is also applied to `dvar.operator()` resulting in
`dvar_str` which already has `_SAGE_VAR_` and is template for
sanitization. Appending `_SAGE_VAR_` to `dvar_str` and replacing it thus
was useless.
In `desolve_rk4` the `cmd` is constructed from two parts: the `de0` that
gets translated via `._maxima()_` and the construction via string
concatenation. So, there is no difference between `desolve` and
`desolve_rk4` because `desolve` gets `_SAGE_VAR_` everywhere and
`desolve_rk4` too.
--
Ticket URL: <http://trac.sagemath.org/ticket/8734#comment:61>
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.
