51369b610e
When an include is not surrounded by empty lines, its content is inlined on the same line as the adjacent content. That can lead to broken tags and other display issues. This PR fixes all such includes and introduces a validation step that forbids introducing the same problem again.
29 lines
663 B
Plaintext
29 lines
663 B
Plaintext
== Why is this an issue?
|
|
|
|
``++GOTO++`` is an unstructured control flow statement. It makes code less readable and maintainable, and should only be used to branch to defined ``++ENDSR++`` points within the source. For normal loop functions use ``++ITER++`` or ``++LEAVE++`` instead.
|
|
|
|
=== Noncompliant code example
|
|
|
|
[source,rpg]
|
|
----
|
|
C LOOP1 TAG
|
|
...
|
|
C GOTO LOOP1
|
|
----
|
|
|
|
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[]
|