Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71915 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 10532 invoked from network); 1 Feb 2014 08:57:29 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Feb 2014 08:57:29 -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 Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.181 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.217.181 mail-lb0-f181.google.com Received: from [209.85.217.181] ([209.85.217.181:61860] helo=mail-lb0-f181.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C4/80-04352-8F6BCE25 for ; Sat, 01 Feb 2014 03:57:29 -0500 Received: by mail-lb0-f181.google.com with SMTP id z5so4155498lbh.12 for ; Sat, 01 Feb 2014 00:57:25 -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:content-transfer-encoding; bh=ZRAIDNam+ULxlKN+yFP24b5TzeOlsBG5ehlk3Vb5+pw=; b=C9WZaZwe8irG0xLqSVowIY5qevR7lS2EziAHkMhFmhLq0Ev+3v+J/PCqk+DF6+SVOZ 1R1nxIonqCnF9PjOLQ8kQtzOjXkVFxUDH0Q2WFX4vu59DGhx9ULfqNmqeN+h2dVyoNd8 vEiyPyu9xtq2UDlxQdRraFGY/H7zmkqcRhSFlp39f1IsAMC158b4KkE6N1IFkob0BytX pYVw9s8/6v3B1HfX1BHZA0M+kGCcD78lc623XQTkoU19ttSzg9bqqqbS4YawDFCqOPYK 4PkWXYp+RxnU/r1Z5AEGiGAWgjE/kt51ULUy68wxlaKMSeygrk6leYvFHSueDIk9l4yW 5wlw== MIME-Version: 1.0 X-Received: by 10.112.56.237 with SMTP id d13mr16285593lbq.2.1391245045333; Sat, 01 Feb 2014 00:57:25 -0800 (PST) Received: by 10.112.35.163 with HTTP; Sat, 1 Feb 2014 00:57:25 -0800 (PST) In-Reply-To: <1391203805.2941.173.camel@guybrush> References: <98.E0.35265.E17FBE25@pb1.pair.com> <1391203805.2941.173.camel@guybrush> Date: Sat, 1 Feb 2014 09:57:25 +0100 Message-ID: To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= Cc: gooh , PHP internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [VOTE] Automatic Property Initialization From: pierre.php@gmail.com (Pierre Joye) On Fri, Jan 31, 2014 at 10:30 PM, Johannes Schl=C3=BCter wrote: > On Fri, 2014-01-31 at 20:18 +0100, gooh wrote: >> Hi, >> >> I've opened the voting for Automatic Property Initialization: >> >> - https://wiki.php.net/rfc/automatic_property_initialization > > This has the same issue as the 64bit RFC: > "This feature is proposed for inclusion in PHP 5.6" > > For 5.6 we have an alpha out. We created a new release process after > learning that changes late in the game delay our releases and offer a > stronger guarantee that the following release is not in unforeseeable > future to make it a viable thing to delay changes by a release. Exactly, however the idea is to give common sense a chance. We explicitly did not specify that RFCs cannot be accepted after the 1st alpha but before the beta phase (feature freeze). > This is no evaluation of the feature itself. And here I have to agree, language changes (syntax, new language features, etc.) need much more time to be evaluated correctly. This is then the RMs role to decide if this evaluation has been done correctly or not. But I did not check the time plan to see if it is even possible now to accept any new RFC. Cheers, --=20 Pierre @pierrejoye | http://www.libgd.org