Re: [PEAR-DEV] [PEPr] -1 for RFC::Uploadcare

[email protected] (Evert Pot)
Newsgroups php.pear.dev
Message-ID <[email protected]>
On Dec 18, 2012, at 12:48 AM, Evert Pot <[email protected]> wrote:

> On Dec 18, 2012, at 12:44 AM, Lester Caine <[email protected]> wrote:
> 
>> Mike van Riel wrote:
>>> AFAIK The PEAR Coding Standards (and its predecessor: Horde Coding Standards)
>>> has always had spaces for indentation. And given that a reasonable amount of
>>> projects have used the PEAR Coding Standards as inspiration[1] does spaces appear
>>> to be the dominating type of indentation style in userland code.
>> 
>>> [1] Examples include but are not limited to: Zend Framework, Symfony 1 and 2,
>>>    Doctrine, the PSR1 coding standard, Aura Framework, etc.
>> 
>> It was the suggestion that the PSR coding standards should be supported by core that brought this up. It does not make it right and it is totally illogical to be using a different standard JUST for one type of file over the rest? *IF* spaces is adopted as the official standard, then EVERY file in the core project needs to be rewritten - and that is just as insane? This does need sorting out, and perhaps convincing FIR that the CORE coding standards should be followed properly is the right way forward? Certainly something is wrong here and with libraries now looking to switch FROM tabbed files just because another defacto standard is being pushed seems just as wrong?
>> 
>> I don't accept that 'userland can work to a different standard' is a realistic state of play. There should either be a single documented standard - or anarchy?
> 
> Actually, the only person on the internals list ever suggesting that php-src should adopt it was you.

Let me re-phrase that:

Nobody ever suggested that PHP-src should adopt the PSR-1 or 2 coding standards; the only one arguing against it was you, while others tried to convince you it wasn't the topic at and.

The idea behind the PSR group is to come up with common interfaces between projects. Introducing coding standards was a bit deviated from that goal, but the member projects saw some value in agreeing with them. So be it ;).

We're now voting on a standard logging interface, and there's talk about standardizing caching and http request/response abstractions. 

It was brought up in the internals list to have a contact, or a line of communication with php internals, and the PSR group. Nothing more. So you can calm down a bit; as Rasmus said: nothing will change.

Evert
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.