Well, as you said before, current behavior -- excessive generation of new kernels, is also a problem. Although it can be mitigated by recycle kernel cache. As you said, correct behavior should be to avoid generation of unnecessary kernels.
After run "make all" in src/input, I find one reason on the new dummy variable substitution: in src/input/heat.input, there's a "rule" patter matching, it will mess up the %diff kernel to %diff(f(z*sqrt(t)),z*sqrt(t), z) So variable substitution is needed sometimes, and I still believe that using new dummy every time is not necessary, dummy variables can be reused. - Qian On 5/22/26 10:40 PM, Waldek Hebisch wrote: > > The trouble is that such change affects all expression code. Bugs > that I mentioned looked like obviously correct code when viewed in > isolation and were triggered by interaction with other code. > > For old bugs we have tests, so hopefully anybody trying to > reintroduce old bug will be warned by failing test. But here > we are likely to see problem only some time after making change. > -- You received this message because you are subscribed to the Google Groups "FriCAS - computer algebra system" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/fricas-devel/047f0e6d-19f9-4bd2-84e3-093c3a7c1d0b%40gmail.com.
