Fixed problem with handleing oldsytle function declarations.

[splint.git] / test / preds.expect

diff --git a/test/preds.expect b/test/preds.expect
index c5549a8d6acd3b4631fa4dcdd70f7cee95767294..68a31a2bbd0a9d6a63cf24c4de10cfe15c0ae1b3 100644 (file)
--- a/test/preds.expect
+++ b/test/preds.expect
@@ -1,25 +1,25 @@
 
 preds.c: (in function f)
 preds.c:10:7: Test expression for if not bool, type int: *p
-  Test expression type is not boolean or int. (-predboolint will suppress
-  message)
+  Test expression type is not boolean or int. (Use -predboolint to inhibit
+  warning)
 preds.c:15:8: Operand of ! is non-boolean (int): !(*p)
   The operand of a boolean operator is not a boolean. Use +ptrnegate to allow !
-  to be used on pointers. (-boolops will suppress message)
+  to be used on pointers. (Use -boolops to inhibit warning)
 preds.c:20:7: Test expression for if is assignment expression: b1 = b2
   The condition test is an assignment expression. Probably, you mean to use ==
   instead of =. If an assignment is intended, add an extra parentheses nesting
-  (e.g., if ((a = b)) ...) to suppress this message. (-predassign will suppress
-  message)
+  (e.g., if ((a = b)) ...) to suppress this message. (Use -predassign to
+  inhibit warning)
 preds.c:25:7: Test expression for if not bool, type char: (c = 'a')
-  Test expression type is not boolean. (-predboolothers will suppress message)
+  Test expression type is not boolean. (Use -predboolothers to inhibit warning)
 preds.c:30:7: Use of == with bool variables (risks inconsistency because of
                  multiple true values): b1 == b2
   Two bool values are compared directly using a C primitive. This may produce
   unexpected results since all non-zero values are considered TRUE, so
   different TRUE values may not be equal. The file bool.h (included in
-  lclint/lib) provides bool_equal for safe bool comparisons. (-boolcompare will
-  suppress message)
+  splint/lib) provides bool_equal for safe bool comparisons. (Use -boolcompare
+  to inhibit warning)
 preds.c:35:7: Test expression for if not bool, type char: c
 
 Finished checking --- 6 code warnings, as expected
@@ -28,38 +28,38 @@ preds.c: (in function f)
 preds.c:20:7: Test expression for if is assignment expression: b1 = b2
   The condition test is an assignment expression. Probably, you mean to use ==
   instead of =. If an assignment is intended, add an extra parentheses nesting
-  (e.g., if ((a = b)) ...) to suppress this message. (-predassign will suppress
-  message)
+  (e.g., if ((a = b)) ...) to suppress this message. (Use -predassign to
+  inhibit warning)
 
 Finished checking --- 1 code warning, as expected
 
 preds.c: (in function f)
 preds.c:5:8: Operand of ! is non-boolean (int *): !p
-  The operand of ! operator is a pointer. (+ptrnegate will suppress message)
+  The operand of ! operator is a pointer. (Use +ptrnegate to inhibit warning)
 preds.c:10:7: Test expression for if not bool, type int: *p
-  Test expression type is not boolean or int. (-predboolint will suppress
-  message)
+  Test expression type is not boolean or int. (Use -predboolint to inhibit
+  warning)
 preds.c:15:8: Operand of ! is non-boolean (int): !(*p)
   The operand of a boolean operator is not a boolean. Use +ptrnegate to allow !
-  to be used on pointers. (-boolops will suppress message)
+  to be used on pointers. (Use -boolops to inhibit warning)
 preds.c:20:7: Test expression for if is assignment expression: b1 = b2
   The condition test is an assignment expression. Probably, you mean to use ==
   instead of =. If an assignment is intended, add an extra parentheses nesting
-  (e.g., if ((a = b)) ...) to suppress this message. (-predassign will suppress
-  message)
+  (e.g., if ((a = b)) ...) to suppress this message. (Use -predassign to
+  inhibit warning)
 preds.c:25:7: Test expression for if not bool, type char: (c = 'a')
-  Test expression type is not boolean. (-predboolothers will suppress message)
+  Test expression type is not boolean. (Use -predboolothers to inhibit warning)
 preds.c:30:7: Use of == with bool variables (risks inconsistency because of
                  multiple true values): b1 == b2
   Two bool values are compared directly using a C primitive. This may produce
   unexpected results since all non-zero values are considered TRUE, so
   different TRUE values may not be equal. The file bool.h (included in
-  lclint/lib) provides bool_equal for safe bool comparisons. (-boolcompare will
-  suppress message)
+  splint/lib) provides bool_equal for safe bool comparisons. (Use -boolcompare
+  to inhibit warning)
 preds.c:35:7: Test expression for if not bool, type char: c
 bool.h:21:13: Function bool_initMod declared but not used
   A function is declared but not used. Use /*@unused@*/ in front of function
-  header to suppress message. (-fcnuse will suppress message)
+  header to suppress message. (Use -fcnuse to inhibit warning)
 bool.h:24:29: Function bool_unparse declared but not used
 bool.h:27:13: Function bool_not declared but not used
 bool.h:30:13: Function bool_equal declared but not used