Comment #6 on issue 1463 by Toon.Verstraelen: Initial codegen implementation http://code.google.com/p/sympy/issues/detail?id=1463
Thanks for the suggestions, I'll make a new set of patches. Maybe it is even better to let codegen return the contents of the files as strings by default. With an extra argument to_files=True, the contents can be written to files. I'm not sure about the build_system option. In most cases the generated files will be included as part of an existing project that already has a build system of its own. Generating the files for a build system only makes sense if the generated code represents a completely autonomous package (a shared library or an executable). A shared library is maybe possible, but an entire program is something completely different. Even in the case of a shared library, I would prefer to add an API on top of the raw generated functions that is more developer friendly. That said, I'm looking at the entire concept from my own perspective, and others might have different ways of using the codegen feature. -- 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 -~----------~----~----~----~------~----~------~--~---
