For interfaces and abstract methods it is generally a good practice to add a @return annotation even if it is just @return void or @return null, so that implementors know what to do in the overridden method.
For interface and abstract methods, it is impossible to infer the return type
from the immediate code. In these cases, it is generally advisible to explicitly
annotate these methods with a @return doc comment to communicate to implementors
of these methods what they are expected to return.
Loading history...
12
13
15
protected function writeFunctionStatement(RoutineInterface $model) {
The string literal } does not require double quotes, as per coding-style, please use single quotes.
PHP provides two ways to mark string literals. Either with single quotes 'literal' or with
double quotes "literal". The difference between these is that string literals in double quotes
may contain variables with are evaluated at run-time as well as escape sequences.
String literals in single quotes on the other hand are evaluated very literally and the only two
characters that needs escaping in the literal are the single quote itself (\') and the
backslash (\\). Every other character is displayed as is.
Double quoted string literals may contain other variables or more complex escape sequences.
<?php$singleQuoted='Value';$doubleQuoted="\tSingle is $singleQuoted";print$doubleQuoted;
will print an indented: SingleisValue
If your string literal does not contain variables or escape sequences, it should be defined
using single quotes to make that fact clear.
For more information on PHP string literals and available escape sequences see the PHP core
documentation.
For interface and abstract methods, it is impossible to infer the return type from the immediate code. In these cases, it is generally advisible to explicitly annotate these methods with a
@returndoc comment to communicate to implementors of these methods what they are expected to return.