On Wed, Jan 27, 2021 at 04:09:04PM -0800, Ralf Hemmecke wrote:
> Waldek,
> your commit
>
> commit 240e2641928fab6f3bd2d638c5d5c437a8f68d7a
> Author: Waldek Hebisch <[email protected]>
> Date: Thu Jan 21 21:09:35 2021 +0100
>
> Better handle '%iint'
>
> cures the initial issue, but does it also prevent %iint from ever appearing
> in user output?
Well, I fixed one bug. It is unrealistic to expect that single
fix will fix all possible bugs involving %iint. As I wrote,
when there is a bug we want to see it (to be able to fix it).
To say this differently: when you have data structure like
a stack than pushes and pops should be balanced. Fixing
one issue with lack of balance does not mean the problem
will not appear in different place. Better code structure
(possible after rewrite) can signifcantly reduce risk,
but ATM eliminating all bugs is unrealistic.
--
Waldek Hebisch
--
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 on the web visit
https://groups.google.com/d/msgid/fricas-devel/20210128003516.GC39685%40math.uni.wroc.pl.
