#11576: make it possible to generate sequences of variables easily
-------------------------------+--------------------------------------------
Reporter: kcrisman | Owner: burcin
Type: enhancement | Status: new
Priority: major | Milestone: sage-5.6
Component: symbolics | Resolution:
Keywords: Cernay2012 | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
-------------------------------+--------------------------------------------
Comment (by mjo):
Replying to [comment:15 kcrisman]:
> Is it `a_1_{2_3}` or `a_{123}`? I guess I was thinking of subscripts
of subscripts. Maybe that's not at issue here; I can't quite reconstruct
my thinking then either. Wasn't there some nesting somewhere in your
patch?
It's `a_{1)_{2}_{3}`. To create `a_{123}`, you'd call `a[123]`. There is
nesting going on, but each "level" should be separated by an underscore
now. In fact now that we're only accepting the square brackets, I think
commas should map directly to underscores. For example,
{{{
sage: xs[3, 8:10, 2:4]
[xs_3_8_2, xs_3_8_3, xs_3_9_2, xs_3_9_3]
}}}
You're allowed to think of `a[2,3]` as `a_{2_3}`, but I don't think
there's any way to create it distinct from `a_{2}_{3}`. The implementation
creates an `a_{2}` first, and then subscripts that with 3.
I still think the underscores are a little ugly, but I've gotten used to
them and it's preferable to having `a[1,1] - a[11] == 0`.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11576#comment:16>
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.
