On Dec 14, 11:43 am, Carlos Córdoba <ccordob...@gmail.com> wrote: > I have to agree with Marshall, because it could be confusing for new sage > users that come from python to see such a different syntax meaning. > > But what about the Mathematica syntax? Could it be adopted by sage? > > The problem is that most CAS are functional in nature and the first thing > one tries to do in Sage is to translate one's old Mathematica, Maple, etc, > programs to python. For example, I was accustomed to write one-liners that > did a lot of stuff with maps over lists. But the lambda keyword is somewhat > discouraging because it makes your code look overwhelmed and ugly. I have > seen that people use it in python to write very simple functions. Now most > people use list comprehensions, which are nice but not so much if you want > to compose to or three functions at a time.
Rather than adopt the Mathematica (or Maple) syntax, how feasible would it be to have translation functions, so you could plug in your old Maple (or Mathematica) code and it would attempt to produce valid Sage code? This might be a good project for a team of undergraduates. John -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
