> It's not a debugging issue. If you have a function that applies the tan -> > sin/cos rule, it's literally impossible to pull the identity tan(x) = > sin(x)/cos(x) out of it. So if you want to do something nontrivial with > that equation (e.g., solve it for another term, or combine it with a second > rule) you won't be able to. The combination part is definitely an > efficiency question, but it also presents a lack of power of the system > with regards to solving. > > This is a contrast to languages like lisp, where you can always inspect a > function closure. >
I have conceded this point a couple times already. I think that this relates to the following "We may very well want a more structured way to define a rule than a python function" -- 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.
