> I do not think so. I installed this patch and the command
> sage: maxima("x#0").sage()
> gives still error: TypeError: unable to make sense of Maxima
> expression 'x#0' in Sage
>
> Anyway, I uploaded new patch and hope that problem related to parsing
> # will be solved in another patch.
>
Ah, thanks for observing this - #1163 currently makes it so
sage: maxima((x != 1))
x#1
but didn't parse the other way around, didn't occur to me that this
was not already implemented. I will try to update that one.
In the long run, all these Maxima parsing functions should be
refactored to make them easier to find, but that probably won't happen
for a while - also see #7377, which has a much more ambitious agenda.
Incidentally, if you were able to produce the current patch at #7325,
I am sure you are more than competent to review #1163 :-)
- kcrisman
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
