Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64300
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50CDDA20.8090400@lsces.co.uk>
References: <EAA1F7DF-374E-4AB4-9ACD-F2C0CC3AE821@strojny.net> <50CDDA20.8090400@lsces.co.uk>
Date: Sun, 16 Dec 2012 15:30:45 +0100
Message-ID: <CAEU6NAdZPzf6ePQaR1iBMctuveW3QmyMUQYmRWT4AqP0oJsr_Q@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Core liason for PHP FIG
From: peter.e.lind@gmail.com (Peter Lind)

You realize that this is not the list of PHP FIG, right?

On 16 December 2012 15:26, Lester Caine <lester@lsces.co.uk> wrote:
> Lars Strojny wrote:
>>
>> for all of you who don=E2=80=99t know, PHP FIG (Framework Interoperabili=
ty
>> Group,http://www.php-fig.org/) discusses ways frameworks and libraries c=
an
>> work together and integrate much easier. Current PSRs are PSR-0 to
>> standardize autoloading, PSR-1 and PSR-2 that deal with coding styles. A=
ll
>> three are great initiatives so far in bridging gaps between projects and
>> making the PHP ecosystem, well, rounder.
>
>
> Well I'm already classed as a dinosaur, but I have been requesting a guid=
e
> to writing code these days, however some of the MUST elements of PSR-2 ar=
e
> totally opposite to the style guide that I have worked with for years and=
 I
> see no point in arbitrary having to restyle 10+ years of code. Trying to
> restyle for e_strict is bad enough.
>
> As an example ...
> "Code MUST use 4 spaces for indenting, not tabs."
> WHY - tab's has been the standard for all my C/C++ code and every other
> language and is automatically tidied up to that format by my editor. When
> did a switch of this 'rule' come in? Or is there a plan to switch all of =
the
> core code base to follow the same rule? ;)
>
> At the end of the day PHP FIG is simply an example of one style of workin=
g.
> It is perhaps the style that many developments in core are following as
> well? But it not the only way of working? Personally I prefer to avoid
> 'magic loading of files' and stick with specifying what files are load an=
d
> from where. Avoids problems with different distributions changing the rul=
es
> themselves! I see no hope of promoting a 'flat platform' staring point,
> since each distribution loves to promote it's own style of working, and
> running PHP on top of THEIR version of the world makes some standards
> academic? Where ARE files loaded tends to be the first problem when
> debugging a new distribution :(
>
> --
> Lester Caine - G8HFL
> -----------------------------
> Contact - http://lsces.co.uk/wiki/?page=3Dcontact
> 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
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>



--=20
<hype>
WWW: plphp.dk / plind.dk
CV: careers.stackoverflow.com/peterlind
LinkedIn: plind
Twitter: kafe15
</hype>