Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66220
Return-Path: <php@golemon.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 9467 invoked from network); 25 Feb 2013 22:07:55 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 25 Feb 2013 22:07:55 -0000
Authentication-Results: pb1.pair.com header.from=php@golemon.com; sender-id=softfail
Authentication-Results: pb1.pair.com smtp.mail=php@golemon.com; spf=softfail; sender-id=softfail
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.223.175 as permitted sender)
X-PHP-List-Original-Sender: php@golemon.com
X-Host-Fingerprint: 209.85.223.175 mail-ie0-f175.google.com  
Received: from [209.85.223.175] ([209.85.223.175:56779] helo=mail-ie0-f175.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id A6/C7-10787-AB0EB215 for <internals@lists.php.net>; Mon, 25 Feb 2013 17:07:55 -0500
Received: by mail-ie0-f175.google.com with SMTP id c12so3673182ieb.20
        for <internals@lists.php.net>; Mon, 25 Feb 2013 14:07:52 -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=K7ulZPW9sUs2NUWujAbPzSlJMorXldGzvfPR9Hf3/f0=;
        b=a3PPnRRsEmNveoAiom4GkmwBkmjNN2B2IkWarp24nxBlLSyXNr4jlfTtf03gpeXl/V
         eBqxbzlI1VxSIMflR+00NfS7MgQyyJb2cQyKXYls3lu1oWgMETmbMJHcfEVHZbUePFq+
         pnHNJa1Rqt+sTEQzbqGXzBxJ/+EvPIVvo+whdl0/mcRVOMgrXdyUlZmYJwb4QerpVim/
         oUxrfk+0pH+DeRmmA+OfmMXSNsRTil49hazCKzxqg5Y2e55fKlPsNNQWBZ251Ye+L8kJ
         jZjCxNPQ6qYDPW8p0Jh1ITwl2KgFRgMfsKftsPzRAwmIuCE4dG6R0qIZtMlRQjhQq5ud
         KjfA==
MIME-Version: 1.0
X-Received: by 10.43.83.74 with SMTP id af10mr5151564icc.38.1361830072285;
 Mon, 25 Feb 2013 14:07:52 -0800 (PST)
Sender: php@golemon.com
Received: by 10.64.25.168 with HTTP; Mon, 25 Feb 2013 14:07:52 -0800 (PST)
X-Originating-IP: [64.134.69.68]
In-Reply-To: <512BA9A6.6030006@oracle.com>
References: <CAF+90c8o=0u3deM6LA6TW9GjDeNrZA_16TAPBmHJQ7mN_P4v+A@mail.gmail.com>
	<512BA9A6.6030006@oracle.com>
Date: Mon, 25 Feb 2013 14:07:52 -0800
X-Google-Sender-Auth: -4mhdhxxqezJJUg5BR1vOYp0Ojo
Message-ID: <CAESVnVqX0xiu8CZ=Mpyftm2_D_W_qoqUMLvmNF2qpYJZqh9B9Q@mail.gmail.com>
To: Christopher Jones <christopher.jones@oracle.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQnW3fJTvwbPJJkMVNU5ntvKzBAcd1ga2jc9aPL+k2PrEJhrNfkIUIm55CgG9DA/UYqO7O6/
Subject: Re: [PHP-DEV] Allow (...)->foo() expressions not only for `new`
From: pollita@php.net (Sara Golemon)

> (For me, it's changes like Sara's trailing comma proposal that are too
> small to have needed an RFC)
>
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.

-Sara