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
730 B
Plaintext
40 lines
730 B
Plaintext
== Why is this an issue?
|
|
|
|
Empty statements, i.e. ``++:++``, are usually introduced by mistake, for example because:
|
|
|
|
* It was meant to be replaced by an actual statement, but this was forgotten.
|
|
* There was a typo which resulted in the colon being doubled, i.e. ``++::++``.
|
|
|
|
=== Noncompliant code example
|
|
|
|
[source,vb6]
|
|
----
|
|
Dim i, j As Integer
|
|
i = 1 :: j=2 ' Noncompliant - double :
|
|
----
|
|
|
|
=== Compliant solution
|
|
|
|
[source,vb6]
|
|
----
|
|
Dim i, j As Integer
|
|
i = 1 : j=2
|
|
----
|
|
|
|
|
|
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[]
|