> > I doubt there's much that can be done while strictly preserving the > semantics of the language (addition and multiplication of floats aren't > associative). OTOH, if we assume that the programmer wanted to use > infinite-precision real numbers, we can probably do some useful > transformations, but that might fail badly if the programmer actually > dealt with floating-point pitfalls. >
Agreed. I think that the majority of scientific programmers (or programmers in general) aren't very aware of numerical precision issues. Those that are would probably know better than to trust us :) > I think we need a real-world use-case to clarify the goals. > Yes, this would be good. Andy, does anything come to mind? > > I'd guess that most useful optimisations would require moving stuff in > and out of for loops. > This would be good, yes, it might also be beyond our ability. We should make sure that we're not duplicating functionality already found in standard compilers. > There are already lots of parsing libraries. I don't think it's a good > idea to reinvent the wheel. > Is there an easy way to hook such a library into SymPy? > > Later today I'll put code parsing on the ideas page (if someone > > doesn't beat me to it). > Done. -- You received this message because you are subscribed to the Google Groups "sympy" 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/sympy?hl=en.
