15 Jul
2008
15 Jul
'08
10:51 a.m.
Dear Alexei, Alexei Sheplyakov schrieb:
1. One can compare expressions in a natural way (with operator==, operator==, etc) instead of GiNaC-specific is_equal(). 2. (a consequence of 1) No bugs like this: 3. (a consequence of 1) STL containers and algorithms "just work" with GiNaC classes.
okay, so far the advantages. I like them. But then, how would one write the equalities to be given to solve(), series(), subs(), ...? I can only imagine giving two arguments to each function instead of one, but how does it work with lists? Double nested lists? Also, the answers returned by GiNaC like x==0 need to be given differently.
The changes to achive this are not really big.
Mmmh, probably not. Regards, Jens