Re: PEAR's Error Handling and PHP5

> We keep saying since day #1 (despite my typo in my last answer, but > you seem to do not read any answer anyway) that we have nothing > against exceptions, but we do not want to *force* Eceptions usages. We > want to leave this choice to the developer. Yes, and my point is that in my opinion this would be a very short-sighted decision. What makes a framework *work* is the shared guidelines ("coding standards", if you will) that allow package developers to make assumptions about how other packages are going to work. IMO the single most important thing there is to know about a class you are importing & using is how it will alert you of errors. For a PHP5 package to be free to use PEAR_Error or PEAR_Exception at their discretion would be to lose one of the most significant benefits that the PEAR coding standards could possibly provide to users of PEAR packages. If PEAR is a framework, then it needs to make a decision about error handling -- whether that decision be PEAR_Error or PEAR_Exception. Hans