Mark Clements

Sure. For the first one: ````php class MDB_Error { var $pErrorType; var $pErrorMsg; var $pFileName; var $pLineNumber; var $pContext; var $pBacktrace; var $pTimeStamp; // __construct() // This sets up all...

The args are being used, so that won't help things in this case. Having investigated the errors and decided they're false positives, they are easy to ignore, so no urgency...

I take the general point, and there are some other false positives that I'm explicitly not reporting here, e.g. when a variable is passed as a function parameter, as those...

fwiw, in both of the above examples there is at least one variable that is passed into the function, and which *is* used in a function call, and which I...

Point taken. For the record, I would expect example 3 or 4 to still throw the warning, as they involve a function call. Fixing those would involve having a dictionary...

heh - ask them to submit a pull request... ;-)

Fair point! Though in this case, I'm the one arguing *against* doing a full function dictionary, as the cost/benefit feels a bit too weighted in the wrong direction...

 I've been thinking about this on and off for a couple of weeks and have come up with the above idea. The main image is a chain of [PHP...

The main reason for not using the official version was that it wasn't clear what the official version was! The [PHP ElePHPant](http://php.net/elephpant.php), which you'd assume is the official location, has...

How would that work for the core PHPCompatibility project, which wouldn't include a framework logo? I somehow don't think "PHP logo with dropshadow" is going to be distinctive enough! :-)