rspec/rules/S1669/pli/rule.adoc

42 lines
887 B
Plaintext
Raw Normal View History

== Why is this an issue?
2020-06-30 12:47:33 +02:00
PL/I, unlike many other programming languages, does not reserve any word's usage.
2021-02-02 15:02:10 +01:00
2021-01-27 13:42:22 +01:00
This implies that it is syntaxically valid to use the keyword ``++IF++`` as variable names for instance.
2021-02-02 15:02:10 +01:00
2020-06-30 12:47:33 +02:00
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
2020-06-30 12:47:33 +02:00
2022-02-04 17:28:24 +01:00
[source,pli]
2020-06-30 12:47:33 +02:00
----
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;
----
ifdef::env-github,rspecator-view[]
'''
== Implementation Specification
(visible only on this page)
include::../message.adoc[]
'''
== Comments And Links
(visible only on this page)
include::../comments-and-links.adoc[]
endif::env-github,rspecator-view[]