Uploaded image for project: 'SonarCFamily'
  1. SonarCFamily
  2. CPP-707

Create Objective-C rules repository containing targeted rules

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.0
    • Component/s: Objective-C, Sonar Plugin
    • Labels:
      None

      Description

      Create a rule repository for Objective-C and add to it all of the rules which RSPEC contain objective-c as targeted language:

      1. RSPEC-1878
      2. RSPEC-1836
      3. RSPEC-1774
      4. RSPEC-1763
      5. RSPEC-1762
      6. RSPEC-1761
      7. RSPEC-1751
      8. RSPEC-1749
      9. RSPEC-1707
      10. RSPEC-1705
      11. RSPEC-1656
      12. RSPEC-1642
      13. RSPEC-1484
      14. RSPEC-1451
      15. RSPEC-1301
      16. RSPEC-1264
      17. RSPEC-1259
      18. RSPEC-1227
      19. RSPEC-1199
      20. RSPEC-1198
      21. RSPEC-1151
      22. RSPEC-1135
      23. RSPEC-1134
      24. RSPEC-1131
      25. RSPEC-1116
      26. RSPEC-1103
      27. RSPEC-1081
      28. RSPEC-1079
      29. RSPEC-1067
      30. RSPEC-1066
      31. RSPEC-1005
      32. RSPEC-1004
      33. RSPEC-999
      34. RSPEC-998
      35. RSPEC-991
      36. RSPEC-988
      37. RSPEC-987
      38. RSPEC-975
      39. RSPEC-968
      40. RSPEC-959
      41. RSPEC-958
      42. RSPEC-956
      43. RSPEC-955
      44. RSPEC-954
      45. RSPEC-953
      46. RSPEC-943
      47. RSPEC-929
      48. RSPEC-924
      49. RSPEC-923
      50. RSPEC-922
      51. RSPEC-921
      52. RSPEC-916
      53. RSPEC-913
      54. RSPEC-912
      55. RSPEC-911
      56. RSPEC-909
      57. RSPEC-908
      58. RSPEC-907
      59. RSPEC-882
      60. RSPEC-881
      61. RSPEC-878
      62. RSPEC-868
      63. RSPEC-841
      64. RSPEC-824
      65. RSPEC-818
      66. RSPEC-817
      67. RSPEC-799
      68. RSPEC-798
      69. RSPEC-797
      70. RSPEC-796
      71. RSPEC-788
      72. RSPEC-787
      73. RSPEC-140
      74. RSPEC-139
      75. RSPEC-138
      76. RSPEC-134
      77. RSPEC-131
      78. RSPEC-129
      79. RSPEC-128
      80. RSPEC-126
      81. RSPEC-125
      82. RSPEC-124
      83. RSPEC-122
      84. RSPEC-117
      85. RSPEC-113
      86. RSPEC-108
      87. RSPEC-105
      88. RSPEC-104
      89. RSPEC-103
      90. RSPEC-1706
      91. RSPEC-1141
      92. RSPEC-1046
      93. RSPEC-1036
      94. RSPEC-107
      95. RSPEC-100
      96. RSPEC-101
      97. RSPEC-1541
      98. RSPEC-1483
      99. RSPEC-1482
      100. RSPEC-1477
      101. RSPEC-793
      102. RSPEC-1314
      103. RSPEC-1543
      104. RSPEC-1760 - not applicable for now, because underlying C standard is fixed to C11
      105. RSPEC-1764
      106. RSPEC-1862

      partial

      1. RSPEC-109 , ticket created - CPP-754

      RSPECs created in arrears

      1. CPP-64 FileComplexity RSPEC-1908
      2. CPP-173 GotoLabelInNestedBlock RSPEC-1909
      3. CPP-154 / CANSI-184 ObsoletePosixFunction RSPEC-1911
      4. CPP-139 / CANSI-185 NonReentrantFunction RSPEC-1912
      5. CPP-212 SizeofSizeof RSPEC-1913
      6. CPP-216 PPErrorDirectiveReached RSPEC-1914
      7. CPP-313 PPDirectiveIndentation RSPEC-1915
      8. CPP-321 PPBackslashNotLastCharacter RSPEC-1916
      9. CPP-312 CommentMixedStyles RSPEC-1917

        Attachments

          Issue Links

          implements

          Language-Specification - Type used to overload a rule specification for a language RSPEC-1004 C-Family: Init-declarator-lists and member-declarator-lists should consist of single init-declarators and member-declarators respectively

          • Active

          Finding Detection - RSPEC-129 Analysis failure preventing from detecting quality flaws and bugs

          • Closed

          Finding Detection - RSPEC-788 The character sequence /* shall not be used within a comment

          • Closed

          Finding Detection - RSPEC-882 Assignment operators shall not be used in expressions that yield a Boolean value

          • Closed

          Finding Detection - RSPEC-908 Any label referenced by a goto statement shall be declared in the same block, or in a block enclosing the goto statement

          • Closed

          Finding Detection - RSPEC-911 The statement forming the body of a switch, while, do ... while or for statement shall be a compound statement

          • Closed

          Finding Detection - RSPEC-913 An if (expression) construct shall be followed by a compound statement. The else keyword shall be followed by either a compound statement, or another if statement

          • Closed

          Finding Detection - RSPEC-921 Each switch statement should have at least one "case"

          • Closed

          Finding Detection - RSPEC-975 The '\' character should not occur in a header file name

          • Closed

          Code Smell Detection - RSPEC-100 Method names should comply with a naming convention

          • Active

          Code Smell Detection - RSPEC-101 Class names should comply with a naming convention

          • Active

          Code Smell Detection - RSPEC-103 Lines should not be too long

          • Active

          Code Smell Detection - RSPEC-104 Files should not have too many lines of code

          • Active

          Code Smell Detection - RSPEC-105 Tabulation characters should not be used

          • Active

          Code Smell Detection - RSPEC-107 Functions should not have too many parameters

          • Active

          Code Smell Detection - RSPEC-108 Nested blocks of code should not be left empty

          • Active

          Code Smell Detection - RSPEC-109 Magic numbers should not be used

          • Active

          Code Smell Detection - RSPEC-113 Files should contain an empty newline at the end

          • Active

          Code Smell Detection - RSPEC-117 Local variable and function parameter names should comply with a naming convention

          • Active

          Code Smell Detection - RSPEC-122 Statements should be on separate lines

          • Active

          Finding Detection - RSPEC-124 Track comments matching a regular expression

          • Active

          Code Smell Detection - RSPEC-125 Sections of code should not be commented out

          • Active

          Code Smell Detection - RSPEC-126 "if ... else if" constructs should end with "else" clauses

          • Active

          Code Smell Detection - RSPEC-128 Switch cases should end with an unconditional "break" statement

          • Active

          Code Smell Detection - RSPEC-131 "switch" statements should have "default" clauses

          • Active

          Code Smell Detection - RSPEC-134 Control flow statements "if", "for", "while", "switch" and "try" should not be nested too deeply

          • Active

          Code Smell Detection - RSPEC-138 Functions should not have too many lines of code

          • Active

          Code Smell Detection - RSPEC-139 Comments should not be located at the end of lines of code

          • Active

          Finding Detection - RSPEC-140 Track breaches of an XPath rule

          • Active

          Code Smell Detection - RSPEC-787 Source code should only use /* ... */ style comments

          • Active

          Code Smell Detection - RSPEC-793 All uses of the #pragma directive should be documented

          • Active

          Bug Detection - RSPEC-796 Only escape sequences defined in the ISO C standard should be used

          • Active

          Code Smell Detection - RSPEC-797 Trigraphs should not be used

          • Active

          Code Smell Detection - RSPEC-798 Digraphs should not be used

          • Active

          Code Smell Detection - RSPEC-799 Identifiers should not be longer than 31 characters

          • Active

          Bug Detection - RSPEC-817 String literals with different prefixes should not be concatenated

          • Active

          Code Smell Detection - RSPEC-818 Literal suffixes should be upper case

          • Active

          Code Smell Detection - RSPEC-824 Functions should not be declared at block scope

          • Active

          Code Smell Detection - RSPEC-841 "enum" members other than the first one should not be explicitly initialized unless all members are explicitly initialized

          • Active

          Code Smell Detection - RSPEC-868 Operands of "&&" and "||" should be primary (C) or postfix (C++) expressions

          • Active

          Code Smell Detection - RSPEC-878 Comma operator should not be used

          • Active

          Code Smell Detection - RSPEC-881 Increment (++) and decrement (--) operators should not be used in a method call or mixed with other operators in an expression

          • Active

          Code Smell Detection - RSPEC-907 "goto" statement should not be used

          • Active

          Code Smell Detection - RSPEC-909 "continue" should not be used

          • Active

          Code Smell Detection - RSPEC-912 The right-hand operands of && and || should not contain side effects

          • Active

          Code Smell Detection - RSPEC-916 Switch labels should not be nested inside non-switch blocks

          • Active

          Bug Detection - RSPEC-922 Evaluation of the operand to the sizeof operator shall not contain side effects

          • Active

          Code Smell Detection - RSPEC-923 Functions should not be defined with a variable number of arguments

          • Active

          Code Smell Detection - RSPEC-924 Loops should not have more than one "break" or "goto" statement

          • Active

          Code Smell Detection - RSPEC-929 Functions without parameters should be declared with parameter type "void"

          • Active

          Code Smell Detection - RSPEC-943 Object declarations should contain no more than 2 levels of pointer indirection

          • Active

          Code Smell Detection - RSPEC-953 Unions should not be used

          • Active

          Code Smell Detection - RSPEC-954 #include directives in a file should only be preceded by other preprocessor directives or comments

          • Active

          Bug Detection - RSPEC-955 Non-standard characters should not occur in header file names in "#include" directives

          • Active

          Bug Detection - RSPEC-956 "#include" directives should be followed by either <filename> or "filename" sequences

          • Active

          Code Smell Detection - RSPEC-958 Macros should not be #define'd or #undef'd within a block

          • Active

          Code Smell Detection - RSPEC-959 "#undef" should be used with caution

          • Active

          Code Smell Detection - RSPEC-968 Preprocessor operators "#" and "##" should not be used

          • Active

          Bug Detection - RSPEC-987 "<signal.h>" should not be used

          • Active

          Code Smell Detection - RSPEC-988 "<stdio.h>" should not be used in production code

          • Active

          Code Smell Detection - RSPEC-991 "<time.h>" should not be used

          • Active

          Code Smell Detection - RSPEC-998 The name "main" should not be used for any function other than the global "main" function

          • Active

          Code Smell Detection - RSPEC-999 "goto" should jump to labels declared later in the same function

          • Active

          Code Smell Detection - RSPEC-1005 A function should have a single point of exit at the end of the function

          • Active

          Code Smell Detection - RSPEC-1036 Control should not be transferred into a complex logic block using a "goto" or a "switch" statement

          • Active

          Bug Detection - RSPEC-1046 Condition-specific "catch" handlers should not be used after the ellipsis (catch-all) handler

          • Active

          Code Smell Detection - RSPEC-1066 Collapsible "if" statements should be merged

          • Active

          Code Smell Detection - RSPEC-1067 Expressions should not be too complex

          • Active

          Vulnerability Detection - RSPEC-1079 "scanf()" and "fscanf()" format strings should specify a field width for the "%s" string placeholder

          • Active

          Vulnerability Detection - RSPEC-1081 Insecure functions should not be used

          • Active

          Code Smell Detection - RSPEC-1103 "/*" and "//" should not be used within comments

          • Active

          Code Smell Detection - RSPEC-1116 Empty statements should be removed

          • Active

          Code Smell Detection - RSPEC-1131 Lines should not end with trailing whitespaces

          • Active

          Finding Detection - RSPEC-1134 Track uses of "FIXME" tags

          • Active

          Finding Detection - RSPEC-1135 Track uses of "TODO" tags

          • Active

          Code Smell Detection - RSPEC-1141 Try-catch blocks should not be nested

          • Active

          Code Smell Detection - RSPEC-1151 "switch case" clauses should not have too many lines of code

          • Active

          Code Smell Detection - RSPEC-1198 Deprecated K&R syntax should not be used for function definition

          • Active

          Code Smell Detection - RSPEC-1199 Nested code blocks should not be used

          • Active

          Code Smell Detection - RSPEC-1227 break statements should not be used except for switch cases

          • Active

          Code Smell Detection - RSPEC-1259 "typedef" should be used for function pointers

          • Active

          Code Smell Detection - RSPEC-1264 A "while" loop should be used instead of a "for" loop

          • Active

          Code Smell Detection - RSPEC-1301 "switch" statements should have at least 3 "case" clauses

          • Active

          Code Smell Detection - RSPEC-1314 Octal values should not be used

          • Active

          Finding Detection - RSPEC-1451 Track lack of copyright and license headers

          • Active

          Code Smell Detection - RSPEC-1477 Source files should not have any duplicated blocks

          • Active

          Code Smell Detection - RSPEC-1482 Branches should have sufficient coverage by unit tests

          • Active

          Code Smell Detection - RSPEC-1483 Lines should have sufficient coverage by unit tests

          • Active

          Finding Detection - RSPEC-1484 Track instances of below-threshold comment line density

          • Active

          Code Smell Detection - RSPEC-1541 Cyclomatic Complexity of functions should not be too high

          • Active

          Code Smell Detection - RSPEC-1543 Macro names should comply with a naming convention

          • Active

          Code Smell Detection - RSPEC-1642 "struct" names should comply with a naming convention

          • Active

          Bug Detection - RSPEC-1656 Variables should not be self-assigned

          • Active

          Code Smell Detection - RSPEC-1705 The prefix increment/decrement form should be used

          • Active

          Code Smell Detection - RSPEC-1706 Exceptions should not be used

          • Active

          Finding Detection - RSPEC-1707 Track "TODO" and "FIXME" comments that do not contain a reference to a person

          • Active

          Code Smell Detection - RSPEC-1749 Type specifiers should be listed in a standard order

          • Active

          Bug Detection - RSPEC-1751 Loops with at most one iteration should be refactored

          • Active

          Code Smell Detection - RSPEC-1761 Pre-defined macros should not be defined, redefined or undefined

          • Active

          Code Smell Detection - RSPEC-1762 "#pragma warning (default: ...)" should not be used

          • Active

          Bug Detection - RSPEC-1763 All code should be reachable

          • Active

          Bug Detection - RSPEC-1764 Identical expressions should not be used on both sides of a binary operator

          • Active

          Code Smell Detection - RSPEC-1774 The ternary operator should not be used

          • Active

          Code Smell Detection - RSPEC-1836 "restrict" should not be used

          • Active

          Bug Detection - RSPEC-1862 Related "if/else if" statements should not have the same condition

          • Active

          Code Smell Detection - RSPEC-1878 "union" names should comply with a naming convention

          • Active

          Code Smell Detection - RSPEC-1909 "goto" statements should not be used to jump into blocks

          • Active

          Code Smell Detection - RSPEC-1911 Obsolete POSIX functions should not be used

          • Active

          Code Smell Detection - RSPEC-1912 Non-reentrant POSIX functions should be replaced with their reentrant versions

          • Active

          Finding Detection - RSPEC-1914 Track instances of the "#error" preprocessor directive being reached

          • Active

          Code Smell Detection - RSPEC-1915 Preprocessor directives should not be indented

          • Active

          Bug Detection - RSPEC-1916 Line continuation characters '\' should not be followed by trailing whitespace

          • Active

          Code Smell Detection - RSPEC-1917 Comment styles "//" and "/* ... */" should not be mixed within a file

          • Active

          Code Smell Detection - RSPEC-1908 Files should not be too complex

          • Deprecated

          Bug Detection - RSPEC-1913 "sizeof(sizeof(...))" should not be used

          • Deprecated
          is depended upon by

          New Feature - A new feature of the product, which has yet to be developed. CPP-555 Add support for Objective-C language

          • Major - Major loss of function.
          • Closed

            Activity

              People

              • Assignee:
                massimo.paladin Massimo PALADIN
                Reporter:
                massimo.paladin Massimo PALADIN
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Due:
                  Created:
                  Updated:
                  Resolved: