#13655: anonymous symbols lose their identity when passed through maxima
-----------------------------+----------------------------------------------
Reporter: tkluck | Owner: burcin
Type: defect | Status: new
Priority: major | Milestone: sage-5.5
Component: symbolics | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
-----------------------------+----------------------------------------------
Comment (by burcin):
Replying to [comment:3 nbruin]:
> Some systems have both interned and uninterned strings/symbols. Using
the latter in a context where the former is expected results exactly in
the behaviour you observed. That's why I mentioned it, but a pynac expert
(which I'm not) can probably quickly tell if this is the problem here.
`SR.symbol()` is intended to return uninterned symbols when called without
an argument. In the source, you will see that there is a branch `if name
is None:` where `pynac_symbol_registry[name] = e` is not called. My
intention was to let the user create symbolic variables without the risk
of picking the name of a variable used in the input.
The conversion back from Maxima always creates an interned symbol if it
cannot find one already existing in the registry. I admit that this use
case never occured to me before. So we have a bug.
I don't want to lose the current `SR.symbol()` behavior (uninterned
symbols). One possible solution here is to keep two symbol registries.
Keeping the current one and introducing a new one which contains all
symbols including the "uninterned" ones, to be used for Maxima
conversions.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13655#comment:4>
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.