Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64314
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.20.131 cause and error)
Message-ID: <50CE572C.50305@lsces.co.uk>
Date: Sun, 16 Dec 2012 23:20:12 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120826 Firefox/15.0 SeaMonkey/2.12
MIME-Version: 1.0
To: 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> <50CE3197.90403@lerdorf.com>
In-Reply-To: <50CE3197.90403@lerdorf.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Core liason for PHP FIG
From: lester@lsces.co.uk (Lester Caine)

Rasmus Lerdorf wrote:
> 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.

Personally I use the same editor settings to edit C/C++ as I do PHP, Javascript 
and the like. I have always worked that way and following the same rules on PHP 
files as C/C++ files just made perfect sense. Having used that style for many 
year prior to even using PHP. Now some third party is proposing that THEIR view 
of the world is the one everybody should follow? The core project has always 
been flexible on accepting different views of things? If that is about to change 
surely there should be some statement as to whether that view is about to 
change? PHP FIG is being pushed more and more as THE standard, but without any 
legitimacy? Certainly projects are changing coding styles to comply without any 
real debate on whether their 'rules' are generally acceptable? There is nothing 
wrong with what I view as the current standard being used by the core project 
and I see no reason to change from that ... there is certainly no 'alternative' 
standard documented by the core project?

The call was whether there should be a representative on their 'team', but 
surely the debate should be about if it is the appropriate forum to decide 
standards that apply to the whole PHP infrastructure? i.e. does the standards 
being proposed there get endorsement from the core project? Does a 
representative from this project give that one 'official legitimacy' ?

One gets the impression that it's all too late, so from the other side, should 
all of the core files be changed to follow the new de-facto standard? And YES I 
classify using different white space standards for different file formats as 
more of a problem! Writing files in one format which are then used to create 
files for a different format is a recipe for confusion? It's bad enough trying 
to get EOL right between OS's without adding 'what tab standard are you using' :(

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk