Thanks for the response, but my main question is whether or not it is more efficient to leave the notices or to add the extra functions required to not produce them. Let's say, with the default error handler, would it take more overhead for PHP to evaluate all the extra isset() calls and if statements required to eliminate notices or for all the checking it has to do with the notices there. If it isn't considerably more efficient to leave the notices in, then I'd lean towards the side of good practice and code out possible notice errors as I've already begun doing.It's more efficient not to have a custom error handler... when your code fires notices and warnings etc. Well written code won't fire any errors or warnings. Well maintained code won't fire notices. So if you have well written and well maintained code... the overhead is negligible since your error handler will never be used except for the odd notice/warning that you'll be sure to fix if your code is well maintained :) Personally I like to run with E_ALL enabled.
Cheers,
Rob.
Again, thanks for the input.
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
