Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64305
Return-Path: <dragoonis@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 87223 invoked from network); 16 Dec 2012 19:49:48 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 16 Dec 2012 19:49:48 -0000
Authentication-Results: pb1.pair.com header.from=dragoonis@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=dragoonis@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.170 as permitted sender)
X-PHP-List-Original-Sender: dragoonis@gmail.com
X-Host-Fingerprint: 209.85.223.170 mail-ie0-f170.google.com  
Received: from [209.85.223.170] ([209.85.223.170:59867] helo=mail-ie0-f170.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id EF/FA-27715-BD52EC05 for <internals@lists.php.net>; Sun, 16 Dec 2012 14:49:48 -0500
Received: by mail-ie0-f170.google.com with SMTP id k10so8738578iea.29
        for <internals@lists.php.net>; Sun, 16 Dec 2012 11:49:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        bh=E4H4DOXpmaUkLGc7C0IhWFELglWi2/YYAgvR5gMmrCY=;
        b=FuC9jMUqGewed4ky/bfHZfMQgW1O7uL/TGM1NrqibVND+mG9kNfujNlmRXM1/ITvIt
         yFr6oESZyq7+uT49EUV+FbpC5+x/BQRwUPCmodEOap6OBjr+4HF32UIyUvMDMaJdZaT/
         +GK9jV8nNtFOhSaBRCSAcOj5YlHVXCYgqWgsAT7a0wt2K4ImovNMklN2r4BuTq+h63Dd
         LuvJn3Hg4/8VtSUkIaAfsozG+0pv41Z6WAkmoxk2yq/SShxRIppFfwdPMoqvJ2DiKP7I
         x7dPTBaWIlpA5NLeXz3bRzAtUCaKg9843UAlIToInSfxfTzprr1pHxTqspaVVJxRqf+g
         lRwA==
MIME-Version: 1.0
Received: by 10.43.4.70 with SMTP id ob6mr9554693icb.56.1355687385573; Sun, 16
 Dec 2012 11:49:45 -0800 (PST)
Received: by 10.64.19.81 with HTTP; Sun, 16 Dec 2012 11:49:45 -0800 (PST)
In-Reply-To: <50CE252D.5060305@lsces.co.uk>
References: <EAA1F7DF-374E-4AB4-9ACD-F2C0CC3AE821@strojny.net>
	<50CDDA20.8090400@lsces.co.uk>
	<CAEZPtU7T5sx3V29PY1koGU4L_=_RXSD21T5aoeFtu10oEtxwCw@mail.gmail.com>
	<50CE252D.5060305@lsces.co.uk>
Date: Sun, 16 Dec 2012 19:49:45 +0000
Message-ID: <CAKxcST9yCidYjXw4yptEch5vToRFPVpAorjXGxjpiRRpk1jt3A@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=bcaec50fe2270b277f04d0fd91e4
Subject: Re: [PHP-DEV] Core liason for PHP FIG
From: dragoonis@gmail.com (Paul Dragoonis)

--bcaec50fe2270b277f04d0fd91e4
Content-Type: text/plain; charset=ISO-8859-1

On Sun, Dec 16, 2012 at 7:46 PM, Lester Caine <lester@lsces.co.uk> wrote:

> Pierre Joye wrote:
>
>> On Sun, Dec 16, 2012 at 3:26 PM, Lester Caine<lester@lsces.co.uk>  wrote:
>> <snip>
>>
>>> >
>>>
>> Once again this is totally off base. We are not discussing anything
>> proposed or adopted by the FIG group but how php.net can better
>> cooperate with this group. I urge you to stay on topic and move any
>> other topics to the right place.
>>
>
> Actually the question is perfectly valid ... why do we standardise on
> using TAB in the core code, but then use spaces in the php files?
> It would seem that FIG group standards have been adopted in some areas of
> PHP when the real standard is something different?
> I've just realised why I have been having problems with some area which
> USED to use the TAB standard but which have been switched to 'spaces'
> instead! So what IS the standard for file style in core code files? While
> ignoring white space on comparisons does work, it also results in problems
> when trying to commit changes to files which are using different white
> space standards.
>
> OK - scanning a few more files it would seem that spaces are an exception
> (fetch.php for example), and I've found the guideline calling for tab
> rather than spaces, but does that guideline apply transparently to .php
> files as well? Certainly .phpt files are consistently tabbed.
>
> It's not the only difference that FIG are pushing which is opposite to the
> style standards on the core code, so perhaps we should be lobbying them to
> come in line with the documented standards?


We done a survey on all the major projects and what their standards were
and went with the majority of what already existed. It doesn't matter what
we at FIG as long as it was consistent.


>
>
> --
> Lester Caine - G8HFL
> -----------------------------
> Contact - http://lsces.co.uk/wiki/?page=**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<http://rainbowdigitalmedia.co.uk>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--bcaec50fe2270b277f04d0fd91e4--