On Monday, 1 September 2014 22:37:31 UTC+2, James Crist wrote: > > /.../ Handling compiler options should definitely be added to the > codewrappers though, but should be a separate issue. >
Yes, I even went so far to write my own package to handle compilaton (github.com/bjodah/pycompilation). Looking back maybe I should have turned to WAF or something similar instead of reinventing the wheel (an inferior wheel maybe even). When (if) we tackle this, it would be great if we allow sympy to cache e.g. object files from compiled cython wrapper code - at least for me cythonizing/compiling the cython generated C file has been a bottle neck more than once. On Wednesday, 3 September 2014 21:21:06 UTC+2, James Crist wrote: > > Adding to the already created header sounds fine, although it may be > unexpected. Right now I'm kind of leaning to the creation and inclusion of > a separate header-only library that includes SymPy's specially defined > functions. > header only library sounds fine to me, though if there is only one single function "sympy_power_double_int" or whatever it will be named it may be overkill. -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/4b58aa29-72c9-49ab-9fe4-dc2248fd328c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
