Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50688
Return-Path: <pierre.php@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 15706 invoked from network); 29 Nov 2010 12:22:51 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 29 Nov 2010 12:22:51 -0000
Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass; domainkeys=bad
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.42 as permitted sender)
DomainKey-Status: bad
X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01
X-PHP-List-Original-Sender: pierre.php@gmail.com
X-Host-Fingerprint: 209.85.161.42 mail-fx0-f42.google.com  
Received: from [209.85.161.42] ([209.85.161.42:37533] helo=mail-fx0-f42.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 32/01-09925-91B93FC4 for <internals@lists.php.net>; Mon, 29 Nov 2010 07:22:50 -0500
Received: by fxm11 with SMTP id 11so3273571fxm.29
        for <internals@lists.php.net>; Mon, 29 Nov 2010 04:22:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:received:in-reply-to
         :references:date:message-id:subject:from:to:cc:content-type;
        bh=3Jax/EzFmMYthG/JpMpT2pdiC4rPL5eH1Bngw9TNYiQ=;
        b=UdYvvUXspUQEqvkMvI+Cwi58wG+WaTaNaKZxgZ0vS/wYVqAv4DJiC/gblbasEcNwC6
         I1rzs1Fn84DnSYhSrEEvVn+5XA3sG28hYOxlQu20x4PH9lAmPoc3CMMu9tlYYBVibynE
         ddm9aKvZ8D3Rs95wTXClTRKySixnejxvD3tcI=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=oDME35JkXc+M0tz3w5XQ7M6EZ2opn/wsFnNYKF3bBjRQQ/hiIXf6WxuhTYMi95fiq3
         p5m/00Gb46BAkBW4vKtUpDG9HHwriwKO/aWU4QSE5s444fiXFO/a5m7qBpe5K65fSYPb
         AXFI9AUJgXSC8pgyCuieHnDDPSuR4uoMpGhuY=
MIME-Version: 1.0
Received: by 10.223.70.131 with SMTP id d3mr2953937faj.73.1291033365140; Mon,
 29 Nov 2010 04:22:45 -0800 (PST)
Received: by 10.223.83.142 with HTTP; Mon, 29 Nov 2010 04:22:45 -0800 (PST)
In-Reply-To: <AANLkTikVexGwOe2Yktn7y2pqfVgGpVOsv+Ekfu72tTu=@mail.gmail.com>
References: <1290879624.7033.826.camel@guybrush>
	<AANLkTinBkG5560r0tkqqwXkUyCt-HkC74MXNQAJmsPyd@mail.gmail.com>
	<AANLkTikVexGwOe2Yktn7y2pqfVgGpVOsv+Ekfu72tTu=@mail.gmail.com>
Date: Mon, 29 Nov 2010 13:22:45 +0100
Message-ID: <AANLkTi=9qdPvTZioVhyApEJxo_tAwg-WcpFykR=8Yu20@mail.gmail.com>
To: Pierrick Charron <pierrick@webstart.fr>
Cc: =?ISO-8859-1?Q?Johannes_Schl=FCter?= <johannes@schlueters.de>, 
	PHP internals list <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] RFC: Making T_FUNCTION optional in method declarations
From: pierre.php@gmail.com (Pierre Joye)

my +1 for new major version only, btw :)

2010/11/27 Pierre Joye <pierre.php@gmail.com>:
> +1 if "While technically possible this RFC suggests that the following
> shall NOT be valid for keeping the code readable " also means that the
> patch implements it as well (force the function visibility property
> usage).

Cheers,
-- 
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org