rspec/rules/S2025/rpg/rule.adoc
2022-02-04 16:28:24 +00:00

28 lines
795 B
Plaintext

Shared coding conventions allow teams to collaborate effectively. While it is possible to omit the specification letter before a ``++/COPY++`` statement, it is advisable not to do so because including a specification on the line indicates to other developers what type of statements will be added to the program by the copybook. Further, using a specification letter on the line makes it clearer to those who might be skimming the file that the line is not just a comment, but does contain code.
== Noncompliant Code Example
[source,rpg]
----
/COPY MBR1
----
== Compliant Solution
[source,rpg]
----
I/COPY MBR1
----
ifdef::env-github,rspecator-view[]
'''
== Implementation Specification
(visible only on this page)
include::message.adoc[]
endif::env-github,rspecator-view[]