16f6c0aecf
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.
47 lines
1.0 KiB
Plaintext
47 lines
1.0 KiB
Plaintext
== Why is this an issue?
|
|
|
|
Shared coding conventions allow teams to collaborate effectively. This rule checks that there are no whitespaces between an ``++@++`` character and what it precedes.
|
|
|
|
|
|
=== Noncompliant code example
|
|
|
|
[source,cpp]
|
|
----
|
|
@ interface // Noncompliant
|
|
@ end // Noncompliant
|
|
----
|
|
|
|
|
|
=== Compliant solution
|
|
|
|
[source,cpp]
|
|
----
|
|
@interface
|
|
@end
|
|
----
|
|
|
|
|
|
|
|
ifdef::env-github,rspecator-view[]
|
|
|
|
'''
|
|
== Implementation Specification
|
|
(visible only on this page)
|
|
|
|
=== Message
|
|
|
|
Remove this whitespace.
|
|
|
|
|
|
'''
|
|
== Comments And Links
|
|
(visible only on this page)
|
|
|
|
=== on 19 Sep 2014, 13:20:53 Freddy Mallet wrote:
|
|
@Ann, would be great to know if placing a whitespace after a "@" is tolerated by and only by the CLang compiler or if the language itself really allows to do that. According to the answer to this question, this might slightly impact the rule description.
|
|
|
|
=== on 25 Sep 2014, 06:37:09 Ann Campbell wrote:
|
|
According to Evgeny, CLang is "the reference and mostly used compiler for Objective-C"
|
|
|
|
endif::env-github,rspecator-view[]
|