Re: Re: Should PEAR code emit notices/warnings?

On Tue, 2008-11-03 at 19:23 -0500, Gregory Beaver wrote: > Christian Schmidt wrote: > > If a PEAR package calls a native PHP function that emits a > > notice/warning, should that error be silenced using @function() or similar? > > > > Packages like Net_Socket and MDB2 silence all native errors and indicate > > error conditions only using PEAR_Error. Personally I prefer this > > approach, but Till thinks that people should rather turn display_errors > > off or use a lower error_reporting level: > > http://pear.php.net/pepr/pepr-comments-show.php?id=527 > <snip> > > Till is incorrect, coding standards forbid PEAR packages from warnings > or notices, regardless of their source. Till has a point about error suppression though. I've run into a problem in PEAR before where error suppression was used on a conditional include. The returned PEAR_Error object had a message about the driver class not being found. It took me forever to determine that the driver was being found and just had a parse error. Mike