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

Justin Patrin wrote:

On Fri, 27 Aug 2004 13:20:02 +0100, Sergio Carvalho <sergio.carvalho@portugalmail.com> wrote:

Lukas Smith wrote:

So anyway can we save ourselves the why now emails? Our goal is to make a decision on a very critical part. Expect it to be difficult. Expect it to be lengthy. Expect it to be changed later. We are doing opensource. We can afford to strive for the right thing (tm). At the same time lets try to find a working interim solution atleast. Whatever it maybe, nobody can claim to know the full effects of either decision just yet (however I claim to know that nobody knows the full effects ..).

So true. We can all sit around, discuss the pros and cons of exceptions, the all too many different prisms on the expected outcome of exception usage within PHP, and do nothing for months. Or we can try one approach, one that does not impose too many constraints, and see where we'll be heading. The option of assigning alpha or beta states to RFCs is an excellent solution to go along this path.

A quick comment about that. Would an RFC need to go through another comment and voting period to upgrade its status or to release a new version?

Only if there are major changes. I think mailing list emails can resolve most disputes, but if there is an argument, voting can do it. Greg