Trac #9200 [1] adds new keywords from_left and from_right to the top
level limit() function. We already have above, below, minus, plus as
keywords. I wonder if a new one is necessary, and if it should be
"from_left/from_right".
[1] http://trac.sagemath.org/sage_trac/ticket/9200
For reference, Maple only support 4 keywords [2], left, right, real,
complex.
[2] http://www.maplesoft.com/support/help/Maple/view.aspx?path=limit
IMHO, we should also try to keep the interface simple, and not clutter
things up by supporting many different ways of doing the same thing.
Any comments?
Cheers,
Burcin
On Sat, 24 Jul 2010 22:00:12 -0700 (PDT)
Rob Beezer <goo...@beezer.cotse.net> wrote:
> Hi Burcin,
>
> As Dana Ernst has now mentioned on the ticket, this an outgrowth of
> the professional development workshop that Jason Grout, Karl-Dieter
> Crisman and myself have been running this summer on Sage through the
> Mathematical Association of America. Dana is one of our top
> students. ;-) But seriously, he is interested in contributing to
> Sage and I've been helping him along with the process.
His patch was perfect. I'd be really happy to see other people
contribute to symbolics. There are lot's of relatively simple issues
new developers could address. We should be more careful about keeping a
clean user interface however.
> Another one of the "students" (faculty at mostly undergraduate
> colleges) wondered about why these keywords were not present (I think
> they may be in some other of the M's, but obviously not Maple, and I
> can't recall exactly). So we all suggested they could be added, and
> Dana took the bait.
Here is the help page for the MMA command Limit:
http://reference.wolfram.com/mathematica/ref/Limit.html
They seem to only allow -1 and 1 for the Direction argument.
I suggest we add "left" and "right" (instead of "from_left" and
"from_right"). In addition, deprecate "above" and "below".
Comments?
Burcin
On Tue, 27 Jul 2010 12:23:28 -0700 (PDT)
"D.C. Ernst" <ernst...@gmail.com> wrote:
> > > I suggest we add "left" and "right" (instead of "from_left" and
> > > "from_right"). In addition, deprecate "above" and "below".
> >
> > +1 from me. I think that would be a big improvement.
>
> I'm assuming that you want to replace "from_left" (respectively,
> "from_right") with "left" (respectively, "right"). There are two
> reasons why I elected to go with "from_*":
>
> 1. This is more akin to the language that students use when learning
> one-sided limits.
> 2. I wanted to avoid confusion about whether "left" meant "moving
> leftward" as opposed to "from the left."
There is no tab completion for these arguments, I don't think they'll
be used if we leave them as "from_*"
> I'm not particularly in love with "from_*" and I am certainly
> agreeable to changing it (as suggested earlier or otherwise). Can we
> use the symbols "+" and "-"? This most closed mimics the standard
> notation and is concise. Thoughts?
I like these better than "left" and "right", especially since we
already support "plus" and "minus."
Thank you.
Burcin
I am a native English speaker, and have never heard left or right
meaning anything other than the limit *from* the left (negative) or
right (positive) sides. Personally, I'd rather save the keystrokes and
not have to type "from_" every time.
- Robert
> I'm not particularly in love with "from_*" and I am certainly
> agreeable to changing it (as suggested earlier or otherwise). Can we
> use the symbols "+" and "-"? This most closed mimics the standard
> notation and is concise. Thoughts?
>
+1 on the '+' and '-'. If we had that syntax, that's what I'd teach my
students to use since they'd already be using it in the classroom.
Thanks,
Jason
'+'1, we're getting closer... :)
- Robert
> +1 on the '+' and '-'. If we had that syntax, that's what I'd teach my
> students to use since they'd already be using it in the classroom.
My votes are the same as Rob's.
Thanks,
Jason
>Also my votes are the same as Rob's :)
> > [X] minus/plus
>
> > [X] '-'/'+'
>
> > [ ] below/above
>
> > [X] left/right
>
> > [ ] from_left/from_right
>
> My votes are the same as Rob's.
> Thanks for all the discussion! (I never thought such a small thing
> would generate so much discussion.)
Typically, the discussion is inversely proportional to the scope of the
change and the knowledge required to understand the change. See
or
http://en.wikipedia.org/wiki/Parkinson%27s_Law_of_Triviality
Thanks,
Jason