With the symbolics rewrite moving quickly, I'd like to request that if
possible people try to avoid adding more "Maxima-isms" to
sage.calculus.  Specifically, if functionality is being added, please
try to keep it "general" in that the design of the functionality is
not dictated by what Maxima does.  Functions that pass arguments
directly to Maxima are especially bad, as I either have to break API
compatibility or write complicated, expensive (to write and to
execute) parsers to allow backwards compatibility, and I'm not a very
big fan of having to remove interfaces that were added less then a
month before.  This applies primarily to things like assume(x,
"analytic") or otherwise where we are just passing a symbolic
expression directly to Maxima without any real internal logic (which
is also bad because it means the code isn't really doing any error
checking either).
Thanks,
Gary
--~--~---------~--~----~------------~-------~--~----~
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-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to