Re: Re: PHP Standards and Best Practices for PHP 5.3+ Frameworks and Libraries
| From: | Stig Bakken | Date: | Thu, 28 May 2009 06:57:53 +0000 |
| Subject: | Re: Re: PHP Standards and Best Practices for PHP 5.3+ Frameworks and Libraries | ||
| References: | 1 2 3 4 5 6 | Groups: | php.standards |
| Request: | Send a blank email to standards-+get-21@lists.php.net to get a copy of this message | ||
On Wed, May 27, 2009 at 1:21 AM, Cal Evans <cal@calevans.com> wrote:
> 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..
Oh come on. Using the term "SHOULD" is clear. The IETF even goes as
far as to document the proper interpretation-for-RFCs of the word
SHOULD in RFC 2026. The word SHOULD leaves something to the reader's
judgement, because the standard can never cover every conceivable
scenario.
Standards should not be too rigid, nor too loose, which is why there
is a need for terms like SHOULD, SHOULD NOT, MAY and MAY NOT.
- Stig