Re: question about Warnings RFC
| From: | Sergio Carvalho | Date: | Tue, 24 Aug 2004 17:22:19 +0000 |
| Subject: | Re: question about Warnings RFC | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-32903@lists.php.net to get a copy of this message | ||
Greg Beaver wrote:
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc
Hi all, I have a nice, simple question after all the complex wrangling over exceptions: Couldn't we simply phrase an RFC as follows: "For all warnings, use PEAR_ErrorStack in php5" ...and in the process make the warnings RFC unnecessary? If this sentence were added to the exceptions RFC, it would solve a lot of issues (without confusing the exception debate either). I am happy to fix problems major and minor as users become familiar with PEAR_ErrorStack, and so this will become a community package. It's also a radically different model from PEAR_Error, and will take time to be fully tested Greg+0 from me: PEAR_ErrorStack does fill the shoes quite well. I just have to con points: 1) The naming makes people confuse error and warning treatment. Even moreso in mixed PHP4/5 environments, where PEAR_ErrorStack will get used for real error handling. 2) PEAR_ErrorStack is geared towards errors, and could be slimmed down to something more oriented towards warnings. Cheers, Sérgio Carvalho
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc