Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to report
a bug at http://bugs.php.net/how-to-report.php

http://php.net/trigger_error

Ok I fail to see the logic as why this would not be considered a bug? 

If a function only excepts 2 paramenters and works as expected and you add a 3rd (that shouldn't be there) then I would expect that function to ignore the 3rd parameter and still function as intended.

So what you are saying is this?

function security($foo, $bar) {
   return ($foo && $bar ) ? true :false;
}

security(1,1);

This function would return true, but if we did this?

security(1,1,1);

It would return false? Even though there is no 3rd parameter in the function. Sorry but that isn't logical at all and any script that requires this to work correctly would fail all because of a 3rd value that shouldn't be there?

Because that is what is happening with trigger_error.

>If a function only excepts 2 paramenters and works as expected 
>and you add a 3rd (that shouldn't be there) then I would expect 
>that function to ignore the 3rd parameter and still function as intended.

Your expectations are wrong, none of internal funcs work this way.
They have certain number of required and accepted parameters and passing more arguments than can accepted is clearly your mistake.

That is my whole point,it was a mistake on my part and it took me half an hour trying to find out why my errorhandler was not working correctly. When I removed the 3rd parameter from the function it worked as it should. Adding that third value totally rendered this function unworkable. 

Did you even test this? Did you even go and see how this error affects the workablity of this function?

Anyway thanks for your time.