Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71932
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.192.173 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <98.E0.35265.E17FBE25@pb1.pair.com>
References: <98.E0.35265.E17FBE25@pb1.pair.com>
Date: Sat, 1 Feb 2014 11:25:55 -0800
Message-ID: <CAESVnVrRQO=fQyLBKjomn00DK3fivFYT6qBQOGb1yxdQmBur=w@mail.gmail.com>
To: gooh <gooh@php.net>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] [VOTE] Automatic Property Initialization
From: pollita@php.net (Sara Golemon)

On Fri, Jan 31, 2014 at 11:18 AM, gooh <gooh@php.net> wrote:
> I've opened the voting for Automatic Property Initialization:
>
> - https://wiki.php.net/rfc/automatic_property_initialization
>
> There was little feedback on internals regarding this RFC but the few
> responses that have been made were generally in favor of this feature. The
> notable and understandable exception being the HHVM team that would prefer
> their own implementation of constructor promotion. No particular extra
> features have been rejected or strongly favored, which is why I am excluding
> from the vote.
>
FYI, I'm voting "No" as I don't think
https://wiki.php.net/rfc/constructor-promotion was considered
adequately.  They both seek to accomplish the same goal, but one
introduces conflicting syntax while the other does not.

If we're to go with the conflicting syntax, I'd like to see a
reasonable argument why.

-Sara