50% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have
checked you do not need it.
The code might also have been commented out for debugging purposes. In this case it is vital that
someone uncomments it again or your project may behave in very unexpected ways in production.
This check looks for comments that seem to be mostly valid code and reports them.
Loading history...
17
1
$prefix = 'dambuk\\';
18
// base directory for the namespace prefix
19
1
$base_dir = __DIR__ . '/src/';
20
// does the class use the namespace prefix?
21
1
$len = strlen($prefix);
22
1
if (strncmp($prefix, $class, $len) !== 0) {
23
// no, move to the next registered autoloader
24
return;
25
}
26
// get the relative class name
27
1
$relative_class = substr($class, $len);
28
// replace the namespace prefix with the base directory, replace namespace
29
// separators with directory separators in the relative class name, append
dambuk /
CFlashMessages
Damian Bukowski
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.
The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.
This check looks for comments that seem to be mostly valid code and reports them.