Function QcubedHandleError
has a Cognitive Complexity of 23 (exceeds 5 allowed). Consider refactoring. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
Cognitive Complexity
Cognitive Complexity is a measure of how difficult a unit of code is to intuitively understand. Unlike Cyclomatic Complexity, which determines how difficult your code will be to test, Cognitive Complexity tells you how difficult your code will be to read and comprehend.
A method's cognitive complexity is based on a few simple rules:
- Code is not considered more complex when it uses shorthand that the language provides for collapsing multiple statements into one
- Code is considered more complex for each "break in the linear flow of the code"
- Code is considered more complex when "flow breaking structures are nested"
Further reading
Method QcubedHandleError
has 72 lines of code (exceeds 25 allowed). Consider refactoring. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
Method QcubedHandleException
has 39 lines of code (exceeds 25 allowed). Consider refactoring. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
Function QcubedHandleException
has a Cognitive Complexity of 12 (exceeds 5 allowed). Consider refactoring. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
Cognitive Complexity
Cognitive Complexity is a measure of how difficult a unit of code is to intuitively understand. Unlike Cyclomatic Complexity, which determines how difficult your code will be to test, Cognitive Complexity tells you how difficult your code will be to read and comprehend.
A method's cognitive complexity is based on a few simple rules:
- Code is not considered more complex when it uses shorthand that the language provides for collapsing multiple statements into one
- Code is considered more complex for each "break in the linear flow of the code"
- Code is considered more complex when "flow breaking structures are nested"
Further reading
Method QcubedGetBacktrace
has 30 lines of code (exceeds 25 allowed). Consider refactoring. Open
function QcubedGetBacktrace($blnShowArgs = false, $intSkipTraces = 1) {
if (!$blnShowArgs) {
$b = debug_backtrace(DEBUG_BACKTRACE_IGNORE_ARGS);
} else {
$b = debug_backtrace(false);
Function QcubedGetBacktrace
has a Cognitive Complexity of 8 (exceeds 5 allowed). Consider refactoring. Open
function QcubedGetBacktrace($blnShowArgs = false, $intSkipTraces = 1) {
if (!$blnShowArgs) {
$b = debug_backtrace(DEBUG_BACKTRACE_IGNORE_ARGS);
} else {
$b = debug_backtrace(false);
- Read upRead up
Cognitive Complexity
Cognitive Complexity is a measure of how difficult a unit of code is to intuitively understand. Unlike Cyclomatic Complexity, which determines how difficult your code will be to test, Cognitive Complexity tells you how difficult your code will be to read and comprehend.
A method's cognitive complexity is based on a few simple rules:
- Code is not considered more complex when it uses shorthand that the language provides for collapsing multiple statements into one
- Code is considered more complex for each "break in the linear flow of the code"
- Code is considered more complex when "flow breaking structures are nested"
Further reading
Method QcubedHandleError
has 5 arguments (exceeds 4 allowed). Consider refactoring. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
Function QCubedShutdown
has a Cognitive Complexity of 6 (exceeds 5 allowed). Consider refactoring. Open
function QCubedShutdown() {
if (defined ('__TIMER_OUT_FILE__')) {
$strTimerOutput = QTimer::VarDump(false);
if ($strTimerOutput) {
file_put_contents(__TIMER_OUT_FILE__, $strTimerOutput . "\n", FILE_APPEND);
- Read upRead up
Cognitive Complexity
Cognitive Complexity is a measure of how difficult a unit of code is to intuitively understand. Unlike Cyclomatic Complexity, which determines how difficult your code will be to test, Cognitive Complexity tells you how difficult your code will be to read and comprehend.
A method's cognitive complexity is based on a few simple rules:
- Code is not considered more complex when it uses shorthand that the language provides for collapsing multiple statements into one
- Code is considered more complex for each "break in the linear flow of the code"
- Code is considered more complex when "flow breaking structures are nested"
Further reading
The function QcubedHandleError() has an NPath complexity of 512. The configured NPath complexity threshold is 200. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
NPathComplexity
Since: 0.1
The NPath complexity of a method is the number of acyclic execution paths through that method. A threshold of 200 is generally considered the point where measures should be taken to reduce complexity.
Example
class Foo {
function bar() {
// lots of complicated code
}
}
Source https://phpmd.org/rules/codesize.html#npathcomplexity
The function QcubedHandleException() has an NPath complexity of 288. The configured NPath complexity threshold is 200. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
NPathComplexity
Since: 0.1
The NPath complexity of a method is the number of acyclic execution paths through that method. A threshold of 200 is generally considered the point where measures should be taken to reduce complexity.
Example
class Foo {
function bar() {
// lots of complicated code
}
}
Source https://phpmd.org/rules/codesize.html#npathcomplexity
The function QcubedHandleError() has a Cyclomatic Complexity of 21. The configured cyclomatic complexity threshold is 10. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CyclomaticComplexity
Since: 0.1
Complexity is determined by the number of decision points in a method plus one for the method entry. The decision points are 'if', 'while', 'for', and 'case labels'. Generally, 1-4 is low complexity, 5-7 indicates moderate complexity, 8-10 is high complexity, and 11+ is very high complexity.
Example
// Cyclomatic Complexity = 11
class Foo {
1 public function example() {
2 if ($a == $b) {
3 if ($a1 == $b1) {
fiddle();
4 } elseif ($a2 == $b2) {
fiddle();
} else {
fiddle();
}
5 } elseif ($c == $d) {
6 while ($c == $d) {
fiddle();
}
7 } elseif ($e == $f) {
8 for ($n = 0; $n < $h; $n++) {
fiddle();
}
} else {
switch ($z) {
9 case 1:
fiddle();
break;
10 case 2:
fiddle();
break;
11 case 3:
fiddle();
break;
default:
fiddle();
break;
}
}
}
}
Source https://phpmd.org/rules/codesize.html#cyclomaticcomplexity
The function QcubedGetBacktrace() has a Cyclomatic Complexity of 10. The configured cyclomatic complexity threshold is 10. Open
function QcubedGetBacktrace($blnShowArgs = false, $intSkipTraces = 1) {
if (!$blnShowArgs) {
$b = debug_backtrace(DEBUG_BACKTRACE_IGNORE_ARGS);
} else {
$b = debug_backtrace(false);
- Read upRead up
- Exclude checks
CyclomaticComplexity
Since: 0.1
Complexity is determined by the number of decision points in a method plus one for the method entry. The decision points are 'if', 'while', 'for', and 'case labels'. Generally, 1-4 is low complexity, 5-7 indicates moderate complexity, 8-10 is high complexity, and 11+ is very high complexity.
Example
// Cyclomatic Complexity = 11
class Foo {
1 public function example() {
2 if ($a == $b) {
3 if ($a1 == $b1) {
fiddle();
4 } elseif ($a2 == $b2) {
fiddle();
} else {
fiddle();
}
5 } elseif ($c == $d) {
6 while ($c == $d) {
fiddle();
}
7 } elseif ($e == $f) {
8 for ($n = 0; $n < $h; $n++) {
fiddle();
}
} else {
switch ($z) {
9 case 1:
fiddle();
break;
10 case 2:
fiddle();
break;
11 case 3:
fiddle();
break;
default:
fiddle();
break;
}
}
}
}
Source https://phpmd.org/rules/codesize.html#cyclomaticcomplexity
The function QcubedHandleException() has a Cyclomatic Complexity of 10. The configured cyclomatic complexity threshold is 10. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CyclomaticComplexity
Since: 0.1
Complexity is determined by the number of decision points in a method plus one for the method entry. The decision points are 'if', 'while', 'for', and 'case labels'. Generally, 1-4 is low complexity, 5-7 indicates moderate complexity, 8-10 is high complexity, and 11+ is very high complexity.
Example
// Cyclomatic Complexity = 11
class Foo {
1 public function example() {
2 if ($a == $b) {
3 if ($a1 == $b1) {
fiddle();
4 } elseif ($a2 == $b2) {
fiddle();
} else {
fiddle();
}
5 } elseif ($c == $d) {
6 while ($c == $d) {
fiddle();
}
7 } elseif ($e == $f) {
8 for ($n = 0; $n < $h; $n++) {
fiddle();
}
} else {
switch ($z) {
9 case 1:
fiddle();
break;
10 case 2:
fiddle();
break;
11 case 3:
fiddle();
break;
default:
fiddle();
break;
}
}
}
}
Source https://phpmd.org/rules/codesize.html#cyclomaticcomplexity
Avoid using undefined variables such as '$__exc_objErrorAttributeArray' which will lead to PHP notices. Open
$__exc_objErrorAttributeArray[1] = $__exc_objErrorAttribute;
- Read upRead up
- Exclude checks
UndefinedVariable
Since: 2.8.0
Detects when a variable is used that has not been defined before.
Example
class Foo
{
private function bar()
{
// $message is undefined
echo $message;
}
}
Source https://phpmd.org/rules/cleancode.html#undefinedvariable
Avoid using undefined variables such as '$__exc_objErrorAttributeArray' which will lead to PHP notices. Open
$__exc_objErrorAttributeArray[0] = $__exc_objErrorAttribute;
- Read upRead up
- Exclude checks
UndefinedVariable
Since: 2.8.0
Detects when a variable is used that has not been defined before.
Example
class Foo
{
private function bar()
{
// $message is undefined
echo $message;
}
}
Source https://phpmd.org/rules/cleancode.html#undefinedvariable
Avoid using undefined variables such as '$__exc_objErrorAttributeArray' which will lead to PHP notices. Open
$__exc_objErrorAttributeArray[1] = $__exc_objErrorAttribute;
- Read upRead up
- Exclude checks
UndefinedVariable
Since: 2.8.0
Detects when a variable is used that has not been defined before.
Example
class Foo
{
private function bar()
{
// $message is undefined
echo $message;
}
}
Source https://phpmd.org/rules/cleancode.html#undefinedvariable
Missing class import via use statement (line '31', column '35'). Open
$__exc_objErrorAttribute = new QErrorAttribute("Database Error Number", $__exc_errno, false);
- Read upRead up
- Exclude checks
MissingImport
Since: 2.7.0
Importing all external classes in a file through use statements makes them clearly visible.
Example
function make() {
return new \stdClass();
}
Source http://phpmd.org/rules/cleancode.html#MissingImport
The method QcubedGetBacktrace has a boolean flag argument $blnShowArgs, which is a certain sign of a Single Responsibility Principle violation. Open
function QcubedGetBacktrace($blnShowArgs = false, $intSkipTraces = 1) {
- Read upRead up
- Exclude checks
BooleanArgumentFlag
Since: 1.4.0
A boolean flag argument is a reliable indicator for a violation of the Single Responsibility Principle (SRP). You can fix this problem by extracting the logic in the boolean flag into its own class or method.
Example
class Foo {
public function bar($flag = true) {
}
}
Source https://phpmd.org/rules/cleancode.html#booleanargumentflag
Missing class import via use statement (line '23', column '30'). Open
$__exc_objReflection = new ReflectionObject($__exc_objException);
- Read upRead up
- Exclude checks
MissingImport
Since: 2.7.0
Importing all external classes in a file through use statements makes them clearly visible.
Example
function make() {
return new \stdClass();
}
Source http://phpmd.org/rules/cleancode.html#MissingImport
Missing class import via use statement (line '35', column '36'). Open
$__exc_objErrorAttribute = new QErrorAttribute("Query", $__exc_objException->Query, true);
- Read upRead up
- Exclude checks
MissingImport
Since: 2.7.0
Importing all external classes in a file through use statements makes them clearly visible.
Example
function make() {
return new \stdClass();
}
Source http://phpmd.org/rules/cleancode.html#MissingImport
Missing class import via use statement (line '42', column '36'). Open
$__exc_objErrorAttribute = new QErrorAttribute("Query", $__exc_objException->Query, true);
- Read upRead up
- Exclude checks
MissingImport
Since: 2.7.0
Importing all external classes in a file through use statements makes them clearly visible.
Example
function make() {
return new \stdClass();
}
Source http://phpmd.org/rules/cleancode.html#MissingImport
The method QcubedHandleError uses an else expression. Else clauses are basically not necessary and you can simplify the code by not using them. Open
} else {
// Error in installer or similar - ERROR_PAGE_PATH constant is not defined yet.
echo "error: errno: ". $__exc_errno . "<br/>" . $__exc_errstr . "<br/>" . $__exc_errfile . ":" . $__exc_errline . "<br/>" . implode(', ', $__exc_errcontext) ;
}
- Read upRead up
- Exclude checks
ElseExpression
Since: 1.4.0
An if expression with an else branch is basically not necessary. You can rewrite the conditions in a way that the else clause is not necessary and the code becomes simpler to read. To achieve this, use early return statements, though you may need to split the code it several smaller methods. For very simple assignments you could also use the ternary operations.
Example
class Foo
{
public function bar($flag)
{
if ($flag) {
// one branch
} else {
// another branch
}
}
}
Source https://phpmd.org/rules/cleancode.html#elseexpression
The method QcubedHandleException uses an else expression. Else clauses are basically not necessary and you can simplify the code by not using them. Open
} else {
// Error in installer or similar - ERROR_PAGE_PATH constant is not defined yet.
echo "error: errno: ". $__exc_errno . "<br/>" . $__exc_strMessage . "<br/>" . $__exc_strFilename . ":" . $__exc_intLineNumber . "<br/>" . $__exc_strStackTrace ;
}
- Read upRead up
- Exclude checks
ElseExpression
Since: 1.4.0
An if expression with an else branch is basically not necessary. You can rewrite the conditions in a way that the else clause is not necessary and the code becomes simpler to read. To achieve this, use early return statements, though you may need to split the code it several smaller methods. For very simple assignments you could also use the ternary operations.
Example
class Foo
{
public function bar($flag)
{
if ($flag) {
// one branch
} else {
// another branch
}
}
}
Source https://phpmd.org/rules/cleancode.html#elseexpression
The method QcubedGetBacktrace uses an else expression. Else clauses are basically not necessary and you can simplify the code by not using them. Open
} else {
$b = debug_backtrace(false);
}
- Read upRead up
- Exclude checks
ElseExpression
Since: 1.4.0
An if expression with an else branch is basically not necessary. You can rewrite the conditions in a way that the else clause is not necessary and the code becomes simpler to read. To achieve this, use early return statements, though you may need to split the code it several smaller methods. For very simple assignments you could also use the ternary operations.
Example
class Foo
{
public function bar($flag)
{
if ($flag) {
// one branch
} else {
// another branch
}
}
}
Source https://phpmd.org/rules/cleancode.html#elseexpression
Avoid using static access to class 'JavaScriptHelper' in method 'QcubedGetBacktrace'. Open
$vals[] = JavaScriptHelper::toJsObject($val);
- Read upRead up
- Exclude checks
StaticAccess
Since: 1.4.0
Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.
Example
class Foo
{
public function bar()
{
Bar::baz();
}
}
Source https://phpmd.org/rules/cleancode.html#staticaccess
Avoid using static access to class 'QTimer' in method 'QCubedShutdown'. Open
$strTimerOutput = QTimer::VarDump(false);
- Read upRead up
- Exclude checks
StaticAccess
Since: 1.4.0
Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.
Example
class Foo
{
public function bar()
{
Bar::baz();
}
}
Source https://phpmd.org/rules/cleancode.html#staticaccess
Avoid unused local variables such as '$__exc_strObjectType'. Open
$__exc_strObjectType = $__exc_objReflection->getName();
- Read upRead up
- Exclude checks
UnusedLocalVariable
Since: 0.2
Detects when a local variable is declared and/or assigned, but not used.
Example
class Foo {
public function doSomething()
{
$i = 5; // Unused
}
}
Source https://phpmd.org/rules/unusedcode.html#unusedlocalvariable
Avoid unused local variables such as '$__exc_strMessage'. Open
$__exc_strMessage = $__exc_errstr;
- Read upRead up
- Exclude checks
UnusedLocalVariable
Since: 0.2
Detects when a local variable is declared and/or assigned, but not used.
Example
class Foo {
public function doSomething()
{
$i = 5; // Unused
}
}
Source https://phpmd.org/rules/unusedcode.html#unusedlocalvariable
Avoid unused local variables such as '$__exc_strStackTrace'. Open
$__exc_strStackTrace = QcubedGetBacktrace();
- Read upRead up
- Exclude checks
UnusedLocalVariable
Since: 0.2
Detects when a local variable is declared and/or assigned, but not used.
Example
class Foo {
public function doSomething()
{
$i = 5; // Unused
}
}
Source https://phpmd.org/rules/unusedcode.html#unusedlocalvariable
Avoid unused local variables such as '$__exc_strRenderedPage'. Open
$__exc_strRenderedPage = ob_get_contents();
- Read upRead up
- Exclude checks
UnusedLocalVariable
Since: 0.2
Detects when a local variable is declared and/or assigned, but not used.
Example
class Foo {
public function doSomething()
{
$i = 5; // Unused
}
}
Source https://phpmd.org/rules/unusedcode.html#unusedlocalvariable
Avoid unused local variables such as '$__exc_strRenderedPage'. Open
$__exc_strRenderedPage = ob_get_contents();
- Read upRead up
- Exclude checks
UnusedLocalVariable
Since: 0.2
Detects when a local variable is declared and/or assigned, but not used.
Example
class Foo {
public function doSomething()
{
$i = 5; // Unused
}
}
Source https://phpmd.org/rules/unusedcode.html#unusedlocalvariable
Avoid unused local variables such as '$__exc_strObjectType'. Open
$__exc_strObjectType = "E_ERROR";
- Read upRead up
- Exclude checks
UnusedLocalVariable
Since: 0.2
Detects when a local variable is declared and/or assigned, but not used.
Example
class Foo {
public function doSomething()
{
$i = 5; // Unused
}
}
Source https://phpmd.org/rules/unusedcode.html#unusedlocalvariable
The function QcubedHandleError() contains an exit expression. Open
exit();
- Read upRead up
- Exclude checks
ExitExpression
Since: 0.2
An exit-expression within regular code is untestable and therefore it should be avoided. Consider to move the exit-expression into some kind of startup script where an error/exception code is returned to the calling environment.
Example
class Foo {
public function bar($param) {
if ($param === 42) {
exit(23);
}
}
}
Source https://phpmd.org/rules/design.html#exitexpression
The function QcubedHandleException() contains an exit expression. Open
exit(); // HHVM bug. Will not display output if this gets executed here.
- Read upRead up
- Exclude checks
ExitExpression
Since: 0.2
An exit-expression within regular code is untestable and therefore it should be avoided. Consider to move the exit-expression into some kind of startup script where an error/exception code is returned to the calling environment.
Example
class Foo {
public function bar($param) {
if ($param === 42) {
exit(23);
}
}
}
Source https://phpmd.org/rules/design.html#exitexpression
Avoid unused local variables such as '$__exc_intLineNumber'. Open
$__exc_intLineNumber = $__exc_errline;
- Read upRead up
- Exclude checks
UnusedLocalVariable
Since: 0.2
Detects when a local variable is declared and/or assigned, but not used.
Example
class Foo {
public function doSomething()
{
$i = 5; // Unused
}
}
Source https://phpmd.org/rules/unusedcode.html#unusedlocalvariable
Avoid unused local variables such as '$__exc_strFilename'. Open
$__exc_strFilename = $__exc_errfile;
- Read upRead up
- Exclude checks
UnusedLocalVariable
Since: 0.2
Detects when a local variable is declared and/or assigned, but not used.
Example
class Foo {
public function doSomething()
{
$i = 5; // Unused
}
}
Source https://phpmd.org/rules/unusedcode.html#unusedlocalvariable
Avoid excessively long variable names like $__exc_strRenderedPage. Keep variable name length under 20. Open
$__exc_strRenderedPage = ob_get_contents();
- Read upRead up
- Exclude checks
LongVariable
Since: 0.2
Detects when a field, formal or local variable is declared with a long name.
Example
class Something {
protected $reallyLongIntName = -3; // VIOLATION - Field
public static function main( array $interestingArgumentsList[] ) { // VIOLATION - Formal
$otherReallyLongName = -5; // VIOLATION - Local
for ($interestingIntIndex = 0; // VIOLATION - For
$interestingIntIndex < 10;
$interestingIntIndex++ ) {
}
}
}
Source https://phpmd.org/rules/naming.html#longvariable
Avoid excessively long variable names like $__exc_objErrorAttributeArray. Keep variable name length under 20. Open
$__exc_objErrorAttributeArray[0] = $__exc_objErrorAttribute;
- Read upRead up
- Exclude checks
LongVariable
Since: 0.2
Detects when a field, formal or local variable is declared with a long name.
Example
class Something {
protected $reallyLongIntName = -3; // VIOLATION - Field
public static function main( array $interestingArgumentsList[] ) { // VIOLATION - Formal
$otherReallyLongName = -5; // VIOLATION - Local
for ($interestingIntIndex = 0; // VIOLATION - For
$interestingIntIndex < 10;
$interestingIntIndex++ ) {
}
}
}
Source https://phpmd.org/rules/naming.html#longvariable
Avoid excessively long variable names like $__exc_objErrorAttribute. Keep variable name length under 20. Open
$__exc_objErrorAttribute = new QErrorAttribute("Database Error Number", $__exc_errno, false);
- Read upRead up
- Exclude checks
LongVariable
Since: 0.2
Detects when a field, formal or local variable is declared with a long name.
Example
class Something {
protected $reallyLongIntName = -3; // VIOLATION - Field
public static function main( array $interestingArgumentsList[] ) { // VIOLATION - Formal
$otherReallyLongName = -5; // VIOLATION - Local
for ($interestingIntIndex = 0; // VIOLATION - For
$interestingIntIndex < 10;
$interestingIntIndex++ ) {
}
}
}
Source https://phpmd.org/rules/naming.html#longvariable
Avoid excessively long variable names like $__exc_strRenderedPage. Keep variable name length under 20. Open
$__exc_strRenderedPage = ob_get_contents();
- Read upRead up
- Exclude checks
LongVariable
Since: 0.2
Detects when a field, formal or local variable is declared with a long name.
Example
class Something {
protected $reallyLongIntName = -3; // VIOLATION - Field
public static function main( array $interestingArgumentsList[] ) { // VIOLATION - Formal
$otherReallyLongName = -5; // VIOLATION - Local
for ($interestingIntIndex = 0; // VIOLATION - For
$interestingIntIndex < 10;
$interestingIntIndex++ ) {
}
}
}
Source https://phpmd.org/rules/naming.html#longvariable
The parameter $__exc_errno is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseParameterName
Since: 0.2
It is considered best practice to use the camelCase notation to name parameters.
Example
class ClassName {
public function doSomething($user_name) {
}
}
Source
The parameter $__exc_objException is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseParameterName
Since: 0.2
It is considered best practice to use the camelCase notation to name parameters.
Example
class ClassName {
public function doSomething($user_name) {
}
}
Source
The parameter $__exc_errcontext is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseParameterName
Since: 0.2
It is considered best practice to use the camelCase notation to name parameters.
Example
class ClassName {
public function doSomething($user_name) {
}
}
Source
The parameter $__exc_errstr is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseParameterName
Since: 0.2
It is considered best practice to use the camelCase notation to name parameters.
Example
class ClassName {
public function doSomething($user_name) {
}
}
Source
Avoid variables with short names like $b. Configured minimum length is 3. Open
$b = debug_backtrace(DEBUG_BACKTRACE_IGNORE_ARGS);
- Read upRead up
- Exclude checks
ShortVariable
Since: 0.2
Detects when a field, local, or parameter has a very short name.
Example
class Something {
private $q = 15; // VIOLATION - Field
public static function main( array $as ) { // VIOLATION - Formal
$r = 20 + $this->q; // VIOLATION - Local
for (int $i = 0; $i < 10; $i++) { // Not a Violation (inside FOR)
$r += $this->q;
}
}
}
Source https://phpmd.org/rules/naming.html#shortvariable
The parameter $__exc_errline is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseParameterName
Since: 0.2
It is considered best practice to use the camelCase notation to name parameters.
Example
class ClassName {
public function doSomething($user_name) {
}
}
Source
The parameter $__exc_errfile is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseParameterName
Since: 0.2
It is considered best practice to use the camelCase notation to name parameters.
Example
class ClassName {
public function doSomething($user_name) {
}
}
Source
The variable $__exc_objReflection is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_objException is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strObjectType is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_intLineNumber is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strType is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_objErrorAttributeArray is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strObjectType is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_objException is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strFilename is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_objException is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_intLineNumber is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_objException is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strMessage is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strFilename is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strObjectType is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_errfile is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_errcontext is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_objException is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strType is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_objException is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_errno is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strObjectType is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_objException is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_objException is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_objException is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strType is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strObjectType is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strStackTrace is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_objErrorAttribute is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_objErrorAttributeArray is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strRenderedPage is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strObjectType is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strRenderedPage is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_objException is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strStackTrace is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strObjectType is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strObjectType is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strObjectType is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strObjectType is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_objErrorAttribute is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_errstr is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strFilename is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_objException is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_errno is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strType is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strObjectType is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_errline is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_intLineNumber is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strObjectType is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strType is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strMessage is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_objReflection is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_objException is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_objErrorAttribute is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strMessage is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strObjectType is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_errline is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strStackTrace is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_errno is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strType is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_errno is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strObjectType is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strObjectType is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_objErrorAttribute is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_errno is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_errfile is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strObjectType is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_objErrorAttribute is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_objErrorAttributeArray is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_objErrorAttribute is not named in camelCase. Open
function QcubedHandleException($__exc_objException) {
if (class_exists('QApplicationBase'))
QApplicationBase::$ErrorFlag = true;
global $__exc_strType;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_errstr is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}
Source
The variable $__exc_strObjectType is not named in camelCase. Open
function QcubedHandleError($__exc_errno, $__exc_errstr, $__exc_errfile, $__exc_errline, $__exc_errcontext) {
// If a command is called with "@", then we should return
if (error_reporting() == 0)
return true;
- Read upRead up
- Exclude checks
CamelCaseVariableName
Since: 0.2
It is considered best practice to use the camelCase notation to name variables.
Example
class ClassName {
public function doSomething() {
$data_module = new DataModule();
}
}