Hi,
there is a potential bug in the constant folding optimiser that causes
the following boolean expression:
true /\ false,
which would obviously be false, to be transformed into true. The reason
is that the binary Bool$Machine operations use only first argument for
both operands. I fixed this, but I was wondering why it never manifested
itself. Apparently, "true /\ false" is actually a SInt expression, not a
Bool one. Why is this? From axllib, it looks like Boolean's
representation is actually a Bool. Maybe this is the result of another
optimiser? Maybe retyping? Can anyone explain?
--
Pippijn van Steenhoven
_______________________________________________
Aldor-l mailing list
Aldor-l@...
http://aldor.org/mailman/listinfo/aldor-l_aldor.org