Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64309
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.160.42 cause and error)
Message-ID: <50CE3197.90403@lerdorf.com>
Date: Sun, 16 Dec 2012 12:39:51 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Lester Caine <lester@lsces.co.uk>
CC: PHP internals <internals@lists.php.net>
References: <EAA1F7DF-374E-4AB4-9ACD-F2C0CC3AE821@strojny.net> <50CDDA20.8090400@lsces.co.uk> <CAEZPtU7T5sx3V29PY1koGU4L_=_RXSD21T5aoeFtu10oEtxwCw@mail.gmail.com> <50CE252D.5060305@lsces.co.uk> <CAKxcST9yCidYjXw4yptEch5vToRFPVpAorjXGxjpiRRpk1jt3A@mail.gmail.com> <CAAyV7nGdGzdBZyuMaX+TkVExQeS+gneRVLjc11cGVWWkSKcgbw@mail.gmail.com> <50CE2ECB.5030804@lsces.co.uk>
In-Reply-To: <50CE2ECB.5030804@lsces.co.uk>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Core liason for PHP FIG
From: rasmus@lerdorf.com (Rasmus Lerdorf)

On 12/16/2012 12:27 PM, Lester Caine wrote:
> Anthony Ferrara wrote:
>> can we please keep superfluous discussions like coding standards
>> off-list? I
>> have no issue with representation of fig discussion, but whitespace
>> discussions
>> have no place on this list...
> 
> The standards being dictated by FIG are at odds with those adopted here
> for many years? So should we be asking them to change the standard to
> comply with already documented standards, or alternatively should we be
> bowing to their proposals and rewriting the core standards? So the
> discussion should be "Do we accept that they are a legitimate standards
> authority?" or simply ask them to indicate that they ARE at odds with
> the existing adopted standards?

Lester, please stop arguing every point here. Especially really silly
stuff like this. These are not even the same languages. The main core
coding standards are all about C-specific things like freeing memory,
zero-terminated strings, never using strncat, macro usage, preprocessor
usage, internal naming, C-commenting, K&R style stuff, testing, folding,
and yes there is a single line about tabs vs. spaces which is the one
thing you zeroed in on and could possibly apply to both C code and PHP
code, but the fact is that the core coding standards have nothing to do
with user-space PHP coding standards and were written specifically to
apply to the PHP core code written in C.

-Rasmus