Re: Re: PEAR_Warning proof of concept

Hans Lellelid wrote:

4) Provide a throwing/filtering method so it is possible to silence specific subclasses of PEAR_Exception.

I have a hard time with this requirement, mostly because it feels like a kludgy solution to faciliate sloppy coding. Do people really disable error handling while developing? I have never done this & just in general feel that PHP provides *plenty* of RAD features for developers. Generally I find that I like error handling to be *more* verbose during development than less. Exceptions provide much better context than PEAR_Error so hopefully the point of disabling error handling altogether will be removed, since it will (IMO) be much easier to *fix* the errors themselves. Implementing a workaround for a built-in language feature -- i.e. throw() -- for such a questionable purpose just seems like a bad idea.

Here is an example: You have build an application that fetches data from an external source. Now suddenly this external source is down. Still your application provides useful features without this external source, but your application wasnt build to cope with it missing. So now your application craps out until you refactored the entire code .. regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07