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

From: Date: Mon, 17 Dec 2012 23:48:05 +0000
Subject: Re: Re: [PEPr] -1 for RFC::Uploadcare
References: 1 2 3 4 5  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-55119@lists.php.net to get a copy of this message
On Dec 18, 2012, at 12:44 AM, Lester Caine <lester@lsces.co.uk> 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. Evert

« previous php.pear.dev (#55119) next »