adlint 1.18.6 → 2.0.0

data/features/{message_detection → code_check}/W0689.feature

@@ -3,41 +3,41 @@ Feature: W0689
   W0689 detects that the syntax of #line directive is illformed.
 
   Scenario: line number as an arithmetic-expression and no file name
-    Given a target source named "W0689.c" with:
+    Given a target source named "fixture.c" with:
       """
       #line 35 * 100 /* W0689 */
       """
-    When I successfully run `adlint W0689.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0689 | 1    | 10     |
 
   Scenario: line number as an arithmetic-expression and valid file name
-    Given a target source named "W0689.c" with:
+    Given a target source named "fixture.c" with:
       """
       #line 35 * 100 "test.c" /* W0689 */
       """
-    When I successfully run `adlint W0689.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0689 | 1    | 10     |
 
   Scenario: valid line number and invalid file name
-    Given a target source named "W0689.c" with:
+    Given a target source named "fixture.c" with:
       """
       #line 35 L"******.c" /* W0689 */
       """
-    When I successfully run `adlint W0689.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0689 | 1    | 10     |
 
   Scenario: inverted arguments
-    Given a target source named "W0689.c" with:
+    Given a target source named "fixture.c" with:
       """
       #line __FILE__ 35 /* W0689 */
       """
-    When I successfully run `adlint W0689.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0689 | 1    | 16     |

data/features/{message_detection → code_check}/W0690.feature

@@ -3,32 +3,32 @@ Feature: W0690
   W0690 detects that no line number is in the #line directive.
 
   Scenario: an identifier as arguments
-    Given a target source named "W0690.c" with:
+    Given a target source named "fixture.c" with:
       """
       #line LINE1000 /* W0690 */
       """
-    When I successfully run `adlint W0690.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0690 | 1    | 7      |
 
   Scenario: inverted arguments
-    Given a target source named "W0690.c" with:
+    Given a target source named "fixture.c" with:
       """
       #line __FILE__ 35 /* W0690 */
       """
-    When I successfully run `adlint W0690.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0689 | 1    | 16     |
       | W0690 | 1    | 7      |
 
   Scenario: line number and macro replaceable filename
-    Given a target source named "W0690.c" with:
+    Given a target source named "fixture.c" with:
       """
       #line 35 __FILE__ 35 /* OK */
       """
-    When I successfully run `adlint W0690.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
 

data/features/{message_detection → code_check}/W0691.feature

@@ -3,65 +3,65 @@ Feature: W0691
   W0691 detects that `##' operator makes invalid preprocessing token.
 
   Scenario: resulting a decimal-constant `123456'
-    Given a target source named "W0691.c" with:
+    Given a target source named "fixture.c" with:
       """
       #define MACRO(a, b) a ## b
 
       double d = (double) MACRO(123, 456); /* OK */
       """
-    When I successfully run `adlint W0691.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0442 | 1    | 1      |
       | W0117 | 3    | 8      |
 
   Scenario: resulting a floating-constant `.123'
-    Given a target source named "W0691.c" with:
+    Given a target source named "fixture.c" with:
       """
       #define MACRO(a, b) a ## b
 
       double d = (double) MACRO(., 123); /* OK */
       """
-    When I successfully run `adlint W0691.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0442 | 1    | 1      |
       | W0117 | 3    | 8      |
 
   Scenario: resulting a floating-constant `3.1415'.
-    Given a target source named "W0691.c" with:
+    Given a target source named "fixture.c" with:
       """
       #define MACRO(a, b) a ## b
 
       double d = (double) MACRO(3., 1415); /* OK */
       """
-    When I successfully run `adlint W0691.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0442 | 1    | 1      |
       | W0117 | 3    | 8      |
 
   Scenario: resulting a floating-constant `1.23e3'
-    Given a target source named "W0691.c" with:
+    Given a target source named "fixture.c" with:
       """
       #define MACRO(a, b) a ## b
 
       double d = (double) MACRO(1.23, e3); /* OK */
       """
-    When I successfully run `adlint W0691.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0442 | 1    | 1      |
       | W0117 | 3    | 8      |
 
   Scenario: resulting an expression `-123'
-    Given a target source named "W0691.c" with:
+    Given a target source named "fixture.c" with:
       """
       #define MACRO(a, b) a ## b
 
       double d = (double) MACRO(-, 123); /* W0691 */
       """
-    When I successfully run `adlint W0691.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0442 | 1    | 1      |
@@ -69,13 +69,13 @@ Feature: W0691
       | W0117 | 3    | 8      |
 
   Scenario: resulting an expression `1 / 23'
-    Given a target source named "W0691.c" with:
+    Given a target source named "fixture.c" with:
       """
       #define MACRO(a, b) a ## b
 
       double d = (double) MACRO(1/, 23); /* W0691 */
       """
-    When I successfully run `adlint W0691.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0442 | 1    | 1      |
@@ -84,13 +84,13 @@ Feature: W0691
       | W0117 | 3    | 8      |
 
   Scenario: resulting an expression `1.2 * 3.4'
-    Given a target source named "W0691.c" with:
+    Given a target source named "fixture.c" with:
       """
       #define MACRO(a, b) a ## b
 
       double d = (double) MACRO(1.2*, 3.4); /* W0691 */
       """
-    When I successfully run `adlint W0691.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0442 | 1    | 1      |

data/features/{message_detection → code_check}/W0692.feature

@@ -3,13 +3,13 @@ Feature: W0692
   W0692 detects that no argument is given to a function-like macro.
 
   Scenario: no argument to a function-like macro
-    Given a target source named "W0692.c" with:
+    Given a target source named "fixture.c" with:
       """
       #define MACRO(a) #a
 
       const char *s = (char *) MACRO(); /* W0692 */
       """
-    When I successfully run `adlint W0692.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0442 | 1    | 1      |
@@ -17,13 +17,13 @@ Feature: W0692
       | W0117 | 3    | 13     |
 
   Scenario: enough arguments to a function-like macro
-    Given a target source named "W0692.c" with:
+    Given a target source named "fixture.c" with:
       """
       #define MACRO(a) #a
 
       const char *s = (char *) MACRO(str); /* OK */
       """
-    When I successfully run `adlint W0692.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0442 | 1    | 1      |

data/features/{message_detection → code_check}/W0694.feature

@@ -4,7 +4,7 @@ Feature: W0694
   `assert' macro is undefined.
 
   Scenario: undefining `assert' macro and then declaring `assert' function
-    Given a target source named "W0694.c" with:
+    Given a target source named "fixture.c" with:
       """
       #undef assert
       extern void assert(int);
@@ -14,7 +14,7 @@ Feature: W0694
           assert("should not be reached" == ""); /* W0694 */
       }
       """
-    When I successfully run `adlint W0694.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0695 | 1    | 8      |
@@ -28,7 +28,7 @@ Feature: W0694
       | W0628 | 4    | 6      |
 
   Scenario: declaring `assert' function and then undefining `assert' macro
-    Given a target source named "W0694.c" with:
+    Given a target source named "fixture.c" with:
       """
       extern void assert(int);
       #undef assert
@@ -38,7 +38,7 @@ Feature: W0694
           assert("should not be reached" == ""); /* W0694 */
       }
       """
-    When I successfully run `adlint W0694.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0695 | 2    | 8      |
@@ -53,7 +53,7 @@ Feature: W0694
 
   Scenario: undefining `assert' macro in function and then declaring `assert'
             function
-    Given a target source named "W0694.c" with:
+    Given a target source named "fixture.c" with:
       """
       void foo(void)
       {
@@ -62,7 +62,7 @@ Feature: W0694
           assert("should not be reached" == ""); /* W0694 */
       }
       """
-    When I successfully run `adlint W0694.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0695 | 3    | 8      |
@@ -79,7 +79,7 @@ Feature: W0694
 
   Scenario: declaring `assert' function and then undefining `assert' macro in
             function
-    Given a target source named "W0694.c" with:
+    Given a target source named "fixture.c" with:
       """
       extern void assert(int);
 
@@ -89,7 +89,7 @@ Feature: W0694
           assert("should not be reached" == ""); /* W0694 */
       }
       """
-    When I successfully run `adlint W0694.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0695 | 5    | 8      |
@@ -104,7 +104,7 @@ Feature: W0694
       | W0628 | 3    | 6      |
 
   Scenario: `assert' function declared but calling `assert' macro
-    Given a target source named "W0694.c" with:
+    Given a target source named "fixture.c" with:
       """
       extern void assert(int);
 
@@ -115,7 +115,7 @@ Feature: W0694
           assert("should not be reached" == ""); /* OK */
       }
       """
-    When I successfully run `adlint W0694.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0442 | 3    | 1      |

data/features/code_check/W0695.feature

@@ -0,0 +1,78 @@
+Feature: W0695
+
+  W0695 detects that the function named `assert' is called because standard
+  `assert' macro is undefined.
+
+  Scenario: undefining `assert' macro and then declaring `assert' function
+    Given a target source named "fixture.c" with:
+      """
+      #undef assert /* W0695 */
+      extern void assert(int);
+      """
+    When I successfully run `adlint fixture.c` on noarch
+    Then the output should exactly match with:
+      | mesg  | line | column |
+      | W0695 | 1    | 8      |
+      | W0118 | 2    | 13     |
+
+  Scenario: undefining `assert' macro in function and then declaring `assert'
+            function
+    Given a target source named "fixture.c" with:
+      """
+      extern void foo(void)
+      {
+      #undef assert
+          extern void assert(int);
+      }
+      """
+    When I successfully run `adlint fixture.c` on noarch
+    Then the output should exactly match with:
+      | mesg  | line | column |
+      | W0695 | 3    | 8      |
+      | W0117 | 1    | 13     |
+      | W0118 | 4    | 17     |
+      | W0622 | 4    | 17     |
+      | W0624 | 3    | 1      |
+      | W0628 | 1    | 13     |
+
+  Scenario: calling `assert' macro
+    Given a target source named "fixture.c" with:
+      """
+      #include <assert.h>
+
+      void foo(void)
+      {
+          assert("should not be reached" == ""); /* OK */
+      }
+      """
+    When I successfully run `adlint fixture.c` on noarch
+    Then the output should exactly match with:
+      | mesg  | line | column |
+      | W0117 | 3    | 6      |
+      | W0085 | 5    | 5      |
+      | W0628 | 3    | 6      |
+      | W9003 | 5    | 5      |
+
+  Scenario: `assert' function declared but calling `assert' macro
+    Given a target source named "fixture.c" with:
+      """
+      extern void assert(int);
+
+      #define assert(expr) ((void *) 0) /* to simulate #include <assert.h> */
+
+      void foo(void)
+      {
+          assert("should not be reached" == ""); /* OK */
+      }
+      """
+    When I successfully run `adlint fixture.c` on noarch
+    Then the output should exactly match with:
+      | mesg  | line | column |
+      | W0442 | 3    | 1      |
+      | W0118 | 1    | 13     |
+      | W0117 | 5    | 6      |
+      | W0567 | 7    | 5      |
+      | W0085 | 7    | 5      |
+      | W0628 | 5    | 6      |
+
+# vim:ts=2:sw=2:sts=2:et:

data/features/{message_detection → code_check}/W0697.feature

@@ -4,13 +4,13 @@ Feature: W0697
   `return' statements in the non-void function.
 
   Scenario: no `return' statement in non-void function
-    Given a target source named "W0697.c" with:
+    Given a target source named "fixture.c" with:
       """
       extern int func(void) /* W0697 */
       {
       }
       """
-    When I successfully run `adlint W0697.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0117 | 1    | 12     |
@@ -18,7 +18,7 @@ Feature: W0697
       | W0628 | 1    | 12     |
 
   Scenario: a `return' statement is only in a `if' statement
-    Given a target source named "W0697.c" with:
+    Given a target source named "fixture.c" with:
       """
       extern int func(int value) /* W0697 */
       {
@@ -27,7 +27,7 @@ Feature: W0697
           }
       }
       """
-    When I successfully run `adlint W0697.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0117 | 1    | 12     |
@@ -37,7 +37,7 @@ Feature: W0697
       | W0628 | 1    | 12     |
 
   Scenario: `return' statements are only in a `if-else-if' statements chain
-    Given a target source named "W0697.c" with:
+    Given a target source named "fixture.c" with:
       """
       extern int func(int value) /* W0697 */
       {
@@ -48,7 +48,7 @@ Feature: W0697
           }
       }
       """
-    When I successfully run `adlint W0697.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0117 | 1    | 12     |
@@ -60,7 +60,7 @@ Feature: W0697
 
   Scenario: `return' statements are in all `case' clauses but not in the
             `default` clause
-    Given a target source named "W0697.c" with:
+    Given a target source named "fixture.c" with:
       """
       extern int func(int value) /* W0697 */
       {
@@ -76,7 +76,7 @@ Feature: W0697
           }
       }
       """
-    When I successfully run `adlint W0697.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0117 | 1    | 12     |
@@ -86,21 +86,21 @@ Feature: W0697
       | W0628 | 1    | 12     |
 
   Scenario: a `return' statement in non-void function
-    Given a target source named "W0697.c" with:
+    Given a target source named "fixture.c" with:
       """
       extern int func(void) /* OK */
       {
           return 1;
       }
       """
-    When I successfully run `adlint W0697.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0117 | 1    | 12     |
       | W0628 | 1    | 12     |
 
   Scenario: no implicit termination in all execution paths
-    Given a target source named "W0697.c" with:
+    Given a target source named "fixture.c" with:
       """
       extern int func(int value) /* OK */
       {
@@ -110,7 +110,7 @@ Feature: W0697
           return 1;
       }
       """
-    When I successfully run `adlint W0697.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0117 | 1    | 12     |
@@ -119,7 +119,7 @@ Feature: W0697
       | W0628 | 1    | 12     |
 
   Scenario: no implicit termination in `if-else-if' statements chain
-    Given a target source named "W0697.c" with:
+    Given a target source named "fixture.c" with:
       """
       extern int func(int value) /* OK */
       {
@@ -132,7 +132,7 @@ Feature: W0697
           }
       }
       """
-    When I successfully run `adlint W0697.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0117 | 1    | 12     |
@@ -141,7 +141,7 @@ Feature: W0697
       | W0628 | 1    | 12     |
 
   Scenario: no implicit termination with `switch' statement
-    Given a target source named "W0697.c" with:
+    Given a target source named "fixture.c" with:
       """
       extern int func(int value) /* OK */
       {
@@ -158,7 +158,7 @@ Feature: W0697
           return 10;
       }
       """
-    When I successfully run `adlint W0697.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0117 | 1    | 12     |
@@ -167,7 +167,7 @@ Feature: W0697
       | W0628 | 1    | 12     |
 
   Scenario: no implicit termination with `goto' statement
-    Given a target source named "W0697.c" with:
+    Given a target source named "fixture.c" with:
       """
       extern int func(int value) /* OK */
       {
@@ -178,7 +178,7 @@ Feature: W0697
           return 1;
       }
       """
-    When I successfully run `adlint W0697.c` on noarch
+    When I successfully run `adlint fixture.c` on noarch
     Then the output should exactly match with:
       | mesg  | line | column |
       | W0117 | 1    | 12     |