15 Jul
2008
15 Jul
'08
10:31 a.m.
Dear Jens, On Tue, Jul 15, 2008 at 09:01:01AM +0200, Jens Vollinga wrote:
It sounds like a big API change with no apparent benefits for me.
The benefits are 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: ex e1, e2; // do some calculation if (e1 == e2) { // gotcha: this is always true. // do something } 3. (a consequence of 1) STL containers and algorithms "just work" with GiNaC classes. The changes to achive this are not really big. Best regards, Alexei -- All science is either physics or stamp collecting.