Re: [PEPr] -1 for RFC::Error Handling Guidelines for PHP5

On Fri, 27 Aug 2004 21:56:28 -0400, Greg Beaver <greg@chiaraquartet.net> wrote: > Justin Patrin wrote: > >>You call the RFC "Error Handling Guidelines for PHP5" but it only covers > >>a minute subset of what actually is error handling and raising. If you > >>want a +1 from me, it should be named "When To Use Exceptions in PHP5." > > [snip] > > > I don't see why this has to be handled in the same RFC. Warnings are a > > completely separate issue and should be handled in their own way and > > in their own RFC. If we add them to this RFC, its size will double and > > it will be that much harder to agree on it and get it done. Compare > > this to a programming project. If you have two different tasks, you > > make two different and separate functions. If you combine them, you > > risk making it that much harder to make a working and maintainable > > system. > > Read the quote of myself. This RFC was titled incorrectly, it has > something to do with only a subset of error handling, it is not a > comprehensive RFC to handle error handling. Anyone who sees a title > "Error handling in PHP5" will assume that it covers all problems. > I disagree. The RFC defines errors specifically so that they can be separated from warnings. But that's a simple semantic issue that has nothing to do with what I was talking about. Warnings *will* be handled differently from errors (exceptions). Therefore, it should be handled in a different RFC. -- DB_DataObject_FormBuilder - The database at your fingertips http://pear.php.net/package/DB_DataObject_FormBuilder paperCrane --Justin Patrin--