Comment #11 on issue 1463 by Toon.Verstraelen: Initial codegen implementation http://code.google.com/p/sympy/issues/detail?id=1463
I think the symbols in the tests are global variables. Will add the comment in ccode. I have considered the idea to extend the printing routines for sympy functions in such a ways that it prints complete compilable code, but there are a few unsurmountable issues: - For C, one needs both a code and a header file, while the printing routines generate just one string. I'm also interesting in generating .pyf files for f2py. - Sympy functions are not concerned with programming-technical issues, such as input, output and input-output arguments. Other examples are contiguous or non-contiguous arrays, including headers of other libraries such as gsl or others. - It is highly interesting to evaluate several sympy functions in one C routine, eventually sharing common intermediate results with the help of the cse routine. This is more than just printing. - From the programming perspective, expressions with constants should be evaluated in the code generator as much as possible. This is different for printing. I'm not yet very familiar with all the sympy features, so if any of the reasons above is not valid, please let me know. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sympy-issues" group. To post to this group, send email to sympy-issues@googlegroups.com To unsubscribe from this group, send email to sympy-issues+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sympy-issues?hl=en -~----------~----~----~----~------~----~------~--~---
