Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:66227 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24889 invoked from network); 26 Feb 2013 00:33:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Feb 2013 00:33:11 -0000 Authentication-Results: pb1.pair.com smtp.mail=php@golemon.com; spf=softfail; sender-id=softfail Authentication-Results: pb1.pair.com header.from=php@golemon.com; sender-id=softfail Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.210.173 as permitted sender) X-PHP-List-Original-Sender: php@golemon.com X-Host-Fingerprint: 209.85.210.173 mail-ia0-f173.google.com Received: from [209.85.210.173] ([209.85.210.173:43360] helo=mail-ia0-f173.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0B/6A-10787-6C20C215 for ; Mon, 25 Feb 2013 19:33:11 -0500 Received: by mail-ia0-f173.google.com with SMTP id h37so2990601iak.4 for ; Mon, 25 Feb 2013 16:33:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:sender:x-originating-ip:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:x-gm-message-state; bh=J/dDWmFYDCd9clUmgcvTWpBZkIucCBq6M2Zpd5oKPJY=; b=bOeBLVITSNFmmNV1a53dth5dn/MpIRBqy2O03qCiauxI9EqDiwoOlM1eILU5AXfpcK 0sWfmQd/wyVYFHah2ombQg93mz8kwtY3EFUMQ6NQ/vdAfUEXIzoOVWA25wJzYrr8CO9u Sq4lzdl68/51AfM134oiWR3QJzNp4e2HGcNDKc49jp1WRQmIyM6WSXIStWnXeETvCVF4 1IfnbxZAVj5lwJF9uGT9nugsYUVTPjg9Vi7S3HsezkVuUpdZDbUy1BVzD6r1VvqCKD5T 4obBukpBPwtGrd2snqEwHhEgFfKLT+gnw+JvyWwNs3FCqgyZHF/+A7tl9bW64Cxu9/2N Di1w== MIME-Version: 1.0 X-Received: by 10.50.190.233 with SMTP id gt9mr4360346igc.80.1361838787948; Mon, 25 Feb 2013 16:33:07 -0800 (PST) Sender: php@golemon.com Received: by 10.64.25.168 with HTTP; Mon, 25 Feb 2013 16:33:07 -0800 (PST) X-Originating-IP: [64.134.69.68] In-Reply-To: <48CE1F85-5C7E-4BB6-B42C-01D0F7751036@strojny.net> References: <512BA9A6.6030006@oracle.com> <48CE1F85-5C7E-4BB6-B42C-01D0F7751036@strojny.net> Date: Mon, 25 Feb 2013 16:33:07 -0800 X-Google-Sender-Auth: gicpNTe3B8MFQOLUH0hQEUTarag Message-ID: To: Lars Strojny Cc: Bob Weinand , PHP List Developers Mailing Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkux9AHRIueOO60zifG/mkzjr9k2Leq/lQywufz9iaJPrzjzQYGtcC/hY2YZzA7KFFrcMz0 Subject: Re: [PHP-DEV] Allow (...)->foo() expressions not only for `new` From: pollita@php.net (Sara Golemon) >>> When it comes to changing syntax, there is no such thing as too small >>> of an RFC IMO. Runtime changes can occasionally be hand-waved, but >>> syntax changes are serious business. > Seeing this quoted makes me realize I expressed myself poorly. What I meant to convey was: When it comes to syntax changes, there's no such thing as too small of a change to need an RFC. Which I think most parsed out correctly, but I want to be clear on that position. Bugfix or not, a parser change is a parser change.