-
Type:
Code Smell Detection
-
Status: Active
-
Resolution: Unresolved
-
Labels:
-
Message:Remove this use of "[goto|GOTO|GoTo]".
-
Default Severity:Major
-
Impact:Low
-
Likelihood:High
-
Default Quality Profiles:Sonar way
-
Legacy Key:GotoUsage, Goto, PlSql.Goto
-
Targeted languages:Python
-
Covered Languages:C#, C, C++, Objective-C, PHP, PL/I, PL/SQL, RPG, T-SQL, VB.Net, VB6
-
Remediation Function:Constant/Issue
-
Constant Cost:10min
-
Analysis Scope:Main Sources, Test Sources
-
Implementation details:
-
PC-Lint:801, 1801
goto is an unstructured control flow statement. It makes code less readable and maintainable. Structured control flow statements such as if, for, while, continue or break should be used instead.
- is implemented by
-
CPP-267 MISRA C 14.4: The goto statement shall not be used
-
- Closed
-
-
SONARRPG-36 Rule: "[goto|GOTO]" statement should not be used
-
- Closed
-
-
SONARTSQL-35 Rule: "GOTO" statement should not be used
-
- Closed
-
-
SONARVBSIX-178 Rule: "[goto|GOTO]" statement should not be used
-
- Closed
-
-
CPP-707 Create Objective-C rules repository containing targeted rules
-
- Closed
-
- is related to
-
RSPEC-1119 Labels should not be used
- Active
1.
|
PL/SQL: "GOTO" statements should not be used | RSPEC-2403 |
|
Active | Unassigned | |
2.
|
VB6: "GoTo" statements should not be used | RSPEC-2404 |
|
Active | Unassigned | |
3.
|
RPG: "GOTO" statements should not be used | RSPEC-2405 |
|
Active | Unassigned | |
4.
|
C-Family | RSPEC-2406 |
|
Active | Unassigned | |
5.
|
PHP | RSPEC-2407 |
|
Active | Unassigned | |
6.
|
PL/I: "GO TO" statements should not be used | RSPEC-3307 |
|
Active | Unassigned | |
7.
|
T-SQL: "GOTO" statements should not be used | RSPEC-4088 |
|
Active | Unassigned | |
8.
|
VB.Net: "GoTo" statements should not be used | RSPEC-5763 |
|
Active | Unassigned |