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.
40 lines
859 B
Plaintext
40 lines
859 B
Plaintext
== Why is this an issue?
|
|
|
|
Restricting the number of ``++CONTINUE++``, ``++EXIT++`` and ``++CHECK++`` statements in a loop is done in the interest of good structured programming.
|
|
|
|
|
|
One ``++CONTINUE++``, ``++EXIT++`` and ``++CHECK++`` statement is acceptable in a loop, since it facilitates optimal coding. If there is more than one, the code should be refactored to increase readability.
|
|
|
|
=== Noncompliant code example
|
|
|
|
[source,abap]
|
|
----
|
|
DO counter TIMES.
|
|
IF sy-index = 2.
|
|
CONTINUE.
|
|
ENDIF.
|
|
IF sy-index = 10.
|
|
EXIT.
|
|
ENDIF.
|
|
WRITE sy-index.
|
|
ENDDO.
|
|
----
|
|
|
|
ifdef::env-github,rspecator-view[]
|
|
|
|
'''
|
|
== Implementation Specification
|
|
(visible only on this page)
|
|
|
|
include::../message.adoc[]
|
|
|
|
include::../highlighting.adoc[]
|
|
|
|
'''
|
|
== Comments And Links
|
|
(visible only on this page)
|
|
|
|
include::../comments-and-links.adoc[]
|
|
|
|
endif::env-github,rspecator-view[]
|