Boolean literals not correctly expanded for message types

[senier]

package Test is
   type M1
      is message
         X : Boolean
            then null
               if X = True;
      end message;

   type M2
      is message
         Y : M1;
      end message;
end Test;

$ rflx check test.rflx 
Parsing test.rflx
Processing Test
model: error: undefined variable "Test.True" referenced

[treiher]

Interpreting True and False as real boolean literals in the model leads to problems during code generation, as the expressions are not type-checked (#87). A workaround would be to interpret them as numbers 1 and 0.

[senier]

Then we should do that (and mark it as workaround0 until we have type checking.

[treiher]

The issue is much simpler than I thought on Friday. No workaround is needed.