FullForm looks like a bit of a headache to me - in part one of the examples given, InputForm gives Sqrt[5], whereas FullForm gives Power[5,Rational[-1,2]]. The former is closer to sage's syntax and should be easier to parse (and a basic parser for InputForm already exists, in _sage_repr().) So I'm not yet convinced that FullForm is the way to go.
But I've just noticed that mathematica doesn't seem to be responsible for the weird orderings here after all - it seems to be sage itself. For example: sage: 4+I I + 4 As Nick wrote some time ago, >In this example, isn't the sage() function supposed to convert this to >a sage data type, which has fixed order printing on all architectures? It seems that sage's order printing might be at fault in the math_bessel_K example. Could anyone who knows about sage's order printing comment on this? In any case, the biggest problem here is that a patch for #3587 got through that broke functionality, and that no developers noticed until now because no-one ran sage -t -optional. I think we need to write somewhere in big letters that sage -t -optional must be run for any tickets affecting optional packages. It's a bit silly to change the mathematica interface then not run any doctests involving mathematica! Cheers, Felix -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
