Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64306
Return-Path: <ircmaxell@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 89028 invoked from network); 16 Dec 2012 19:54:09 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 16 Dec 2012 19:54:09 -0000
Authentication-Results: pb1.pair.com header.from=ircmaxell@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=ircmaxell@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.170 as permitted sender)
X-PHP-List-Original-Sender: ircmaxell@gmail.com
X-Host-Fingerprint: 209.85.220.170 mail-vc0-f170.google.com  
Received: from [209.85.220.170] ([209.85.220.170:64493] helo=mail-vc0-f170.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 91/6B-27715-1E62EC05 for <internals@lists.php.net>; Sun, 16 Dec 2012 14:54:09 -0500
Received: by mail-vc0-f170.google.com with SMTP id fl11so6534855vcb.29
        for <internals@lists.php.net>; Sun, 16 Dec 2012 11:54:06 -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=Edfmfl5MbYyk7LGfydCgtu2kzJDRNOKyrmixneGS7Zc=;
        b=uaxpb/YJdq3NDZKxc5/mSJfxSKfqREkUB+H1030D/I7H4WZJ0JNr13CwSWFI5RfnG0
         WcnMzRT0DNJ8xsvc4u78Nq44CYrLaY0IONoaKqMoEQ1e9smq+h+WajDpG1Kmw85VoGA8
         yD3zT3wukX6BnT7RnIHDcBKphhLP5dAl+zfo9OoA7MTYJ4pwU6gLXX8fIpqtJQvKiRUi
         ewcrd4Vab8yLUZc7fU3yCN76ZzBESttA8NpMkeo/wqy0fuSgTKsVxvjZCsHfL9E4jVEJ
         zUqt0/hf5h+beuZEnFx3eMW2nGGKITn3F6kTX/uUsWVmmFyJzLvUN/QXo5Hg/uUdA9YY
         tFnQ==
MIME-Version: 1.0
Received: by 10.59.6.70 with SMTP id cs6mr20027497ved.60.1355687646790; Sun,
 16 Dec 2012 11:54:06 -0800 (PST)
Received: by 10.58.200.130 with HTTP; Sun, 16 Dec 2012 11:54:06 -0800 (PST)
Received: by 10.58.200.130 with HTTP; Sun, 16 Dec 2012 11:54:06 -0800 (PST)
In-Reply-To: <CAKxcST9yCidYjXw4yptEch5vToRFPVpAorjXGxjpiRRpk1jt3A@mail.gmail.com>
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>
Date: Sun, 16 Dec 2012 14:54:06 -0500
Message-ID: <CAAyV7nGdGzdBZyuMaX+TkVExQeS+gneRVLjc11cGVWWkSKcgbw@mail.gmail.com>
To: Paul Dragoonis <dragoonis@gmail.com>
Cc: Lester Caine <lester@lsces.co.uk>, internals@lists.php.net
Content-Type: multipart/alternative; boundary=047d7bf0effe9d05ac04d0fda08b
Subject: Re: [PHP-DEV] Core liason for PHP FIG
From: ircmaxell@gmail.com (Anthony Ferrara)

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

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...

Anthony
On Dec 16, 2012 2:49 PM, "Paul Dragoonis" <dragoonis@gmail.com> wrote:

> 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
> >
> >
>

--047d7bf0effe9d05ac04d0fda08b--