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

On Wed, Mar 12, 2008 at 1:23 AM, Gregory Beaver <greg@chiaraquartet.net> 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. On there? Couldn't really find it. http://pear.php.net/manual/en/standards.errors.php Anyway, even if the package is not supposed to "issue" a notice or warning, what about implementing a logger to catch them? I still don't think that generally silencing them is a good idea (TM). @Christian Schmidt If it's allowed, ignore my request. Till