
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.
24 lines
900 B
Plaintext
24 lines
900 B
Plaintext
== Why is this an issue?
|
|
|
|
----
|
|
setColorPoint(Point p, String Color); //violation
|
|
void setColorPoint(Point p, String Color); //Ok
|
|
----
|
|
If you do not specify a return type, the compiler will assume either void or int, depending on the compiler. You should explicitly declare the return type so that the result will be unambiguous. (Readability)
|
|
|
|
|
|
ifdef::env-github,rspecator-view[]
|
|
'''
|
|
== Comments And Links
|
|
(visible only on this page)
|
|
|
|
=== duplicates: S820
|
|
|
|
=== on 22 Apr 2014, 21:48:32 Evgeny Mandrikov wrote:
|
|
As far as I know {cpp} standard requires a type specifier for all declarations, so I'm wondering which compiler allows specification of function without type in {cpp} mode?
|
|
|
|
=== on 28 Apr 2014, 22:29:55 Evgeny Mandrikov wrote:
|
|
\[~ann.campbell.2] moreover - maybe this ticket duplicate of RSPEC-820? Which again for some unknown reason targets {cpp}.
|
|
|
|
endif::env-github,rspecator-view[]
|