rspec/rules/S1713/cobol/rule.adoc

== Why is this an issue?

``++PERFORM paragraph1++`` is preferred over ``++PERFORM paragraph1 THRU paragraph2++`` because it adheres more closely to the structured programming precepts of having a single entry point and a single exit point. Additionally, mixing the two approaches can lead to errors. 

ifdef::env-github,rspecator-view[]

'''
== Implementation Specification
(visible only on this page)

=== Message

Use "PERFORM" instead


endif::env-github,rspecator-view[]
migrate rule descriptions to new education format 2023-05-03 11:06:20 +02:00			`== Why is this an issue?`

Restructure one-lang rspecs 2021-04-28 16:49:39 +02:00			``++PERFORM paragraph1++`` is preferred over ``++PERFORM paragraph1 THRU paragraph2++`` because it adheres more closely to the structured programming precepts of having a single entry point and a single exit point. Additionally, mixing the two approaches can lead to errors.
Fix the missing default metadata fields 2021-04-28 18:08:03 +02:00
RULEAPI-666: Migrate the "List of parameters", "Highlighting" and "Message" fields from jira RSPEC (#346) 2021-09-20 15:38:42 +02:00			`ifdef::env-github,rspecator-view[]`

			`'''`
			`== Implementation Specification`
			`(visible only on this page)`

Inline adoc when include has no additional value (#1940) Inline adoc files when they are included exactly once. Also fix language tags because this inlining gives us better information on what language the code is written in. 2023-05-25 14:18:12 +02:00			`=== Message`

			`Use "PERFORM" instead`

RULEAPI-666: Migrate the "List of parameters", "Highlighting" and "Message" fields from jira RSPEC (#346) 2021-09-20 15:38:42 +02:00
			`endif::env-github,rspecator-view[]`