Re: Re: PHP Standards and Best Practices for PHP 5.3+ Frameworks and Libraries

Hi all, While I disagree with Hannes about the SHOULD, aren't re-hashing a discussion? It was my understanding that what was agreed upon in the meeting had been voted on and is now accepted. Let's not re-open things that have already been agreed upon. FWIW, I disagree because if we say SHOULD then it's not a standard it's a good idea. this is a Standards group not a Good Idea group. People will take what we say very seriously so we should be very clear on what we say. It is my belief that we should never release an "optional standard" (isn't that like an optimized RAILS app?) and we should never release a standard that has multiple ways of doing something. If we can't get a majority vote on something, let's just leave it alone. Ok, I'm now starting to hijack the thread so maybe I'll type this screed up and post it to the mailing list. =C= On Tue, May 26, 2009 at 10:57 PM, Brett Bieber <brett.bieber@gmail.com>wrote: > On Tue, May 26, 2009 at 3:47 PM, Matthew Weier O'Phinney > <matthew@zend.com> wrote: > >> Matthew Weier O'Phinney wrote: > >> > -- Hannes Magnusson <hannes.magnusson@gmail.com> wrote > >> > (on Tuesday, 26 May 2009, 10:09 PM +0200): > >> > > > **Exceptions and Exception Handling** > >> > > > Each package must provide a base exception of the following name: > >> > > > vendor\package\Exception > >> > > > > >> > > Err. So every package namespace must have an Exception > class/interface > >> > > called literally 'Exception'? > >> > > That feels a bit of an overkill. > >> > > How about "SHOULD provide"? >