On Friday, April 25, 2014 5:02:19 PM UTC+2, Matthew wrote: > > > I used the strategies module to pull out the tree search stuff. See > either sympy.strategies or github.com/logpy/strategies/ > It is used in fu simp here > > > https://github.com/sympy/sympy/blob/821fc389bcb7285555f6ec46c32afa38faceeab1/sympy/simplify/fu.py#L1597 > > I was thinking of a possible scenario to continue the development of CSymPy. Suppose that a mathematical algorithm is implemented by a rule file, which either defines rules for LogPy or Strategies. SymPy could be added parsing capabilities to that "rule" file, i.e. SymPy works together with LogPy and/or Strategies to perform the defined algorithm. On the meantime, there could be an implementation of LogPy and/or Strategies through C++ template metaprogramming, which implies that the rule file is parsed at compile time, and efficient code is generated still at compile time in the CSymPy object files/binary. Template metaprogramming is Turing complete, so it should be possible to implement LogPy and/or Strategies through it.
There could be a slow and unoptimized version through SymPy + LogPy/Strategies for the development, and then the fast version of the algorithm when CSymPy is compiled. Do you think that this one is a plausible way? -- 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/7c0d7970-eb9c-432d-b303-3956debaac14%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
