Products
In-IDE
IDE extension that lets you fix coding issues before they exist!
Discover SonarLint
SaaS
Setup is effortless and analysis is automatic for most languages
Discover SonarCloud
Self-Hosted
Fast, accurate analysis; enterprise scalability
Discover SonarQube

PL/I static code analysis

Unique rules to find Bugs and Code Smells in your PL/I code

All rules 25

Bug1

Code Smell24

Filtered: 2 rules found

pitfall

Keywords should not be used as variable names

Code Smell

BlockerSonarSource default severity
click to learn more

PL/I, unlike many other programming languages, does not reserve any word’s usage.

This implies that it is syntaxically valid to use the keyword IF as variable names for instance.

But doing so results in confusing code which is hard to read, especially in editors without proper PL/I syntax highlighting support.

Noncompliant Code Example

foo: proc options(main);
  declare if fixed decimal init (42); /* Non-Compliant */

  if if = 42 then do; /* Cconfusing */
    put list ('if = 42');
  end;

  go to goto; /* Confusing */

  goto: /* Non-Compliant */
  ;
end;

Available In:

Catch issues on the fly,
in your IDE

Enterprise
Edition

In-IDE

SaaS

Self-Hosted