File: boolean-const.m

package info (click to toggle)
rumur 2025.08.31-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 3,644 kB
  • sloc: cpp: 18,711; ansic: 3,825; python: 1,578; objc: 1,542; yacc: 568; sh: 331; lex: 241; lisp: 15; makefile: 5
file content (32 lines) | stat: -rw-r--r-- 877 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
/* This model is intended to provoke a bug that was observed on commit
 * 7eafb5295a1f2f094579ef259b537bd3e4996158. Constants would always be
 * constructed with no type (i.e. implicitly an unrestricted range). This is
 * fine for anything except a boolean (non-range) constant. A boolean constant
 * that is constructed with no type can never be used in a boolean expression
 * because Rumur thinks it is a numeric value and rejects it.
 *
 * If this bug is present, the model will fail code generation with a message
 * like "condition of if clause is not a boolean expression". If everything is
 * OK, code generation should complete successfully and the generated verifier
 * should not find any errors.
 */

const
  NOT_TRUE: false;

var
  x: boolean;

startstate begin
  x := true;
end;

rule begin
  if NOT_TRUE then
    x := !x;
  end;
end;

rule begin
  x := !x;
end;