Thanks for the good suggestions. The challenge is trying to recognize
the variables in derived expressions. I'm sure I can combine your
ideas to produce something suitable.
Thanks!
- Ryan
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, se
On Apr 26, 9:48 am, Ryan Hinton wrote:
> sage: nn = var('n(0.1)(3.)')
>
> Creating expressions using ``nn`` seems to work fine -- as long as
> everything stays in Sage. But when I try to do some non-trivial
> equality comparisons, Sage punts the decision to Maxima, which chokes
> on the variable
Could not you use another way to use these subscripts. The following
may be ugly, but works
sage: n=var('n__0_3__0_1')
sage: maxima(n+1)
n__0_3__0_1+1
On 26 abr, 17:48, Ryan Hinton wrote:
> I'm using variable names with non-alphanumeric characters for
> convenience. (Longer story: I have varia
I think that this is a problem inherent to the way that sage
communicates to maxima. And would be difficult to correct unless every
symbolic variable/function has a different maxima, pari etc. name that
does not cause this problem.
For example I would not like the following to be supported
sage:
