Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69385
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <A8.C4.28456.E2C35425@pb1.pair.com>
References: <524530F4.7010806@php.net> <A8.C4.28456.E2C35425@pb1.pair.com>
Date: Fri, 27 Sep 2013 12:02:46 +0200
Message-ID: <CALtuQzARtGTY_yW7B-4PWEKNJZtK=o7SFO0pbn9TeWcN-gmC3w@mail.gmail.com>
To: Matthieu Napoli <matthieu@mnapoli.fr>
Cc: PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e01228058f5daea04e75a98dd
Subject: Re: [PHP-DEV] Re: RFC: Automatic Property Initialization
From: krebs.seb@gmail.com (Sebastian Krebs)

--089e01228058f5daea04e75a98dd
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

2013/9/27 Matthieu Napoli <matthieu@mnapoli.fr>

> Le 27/09/2013 09:17, Gordon Oheim a =E9crit :
>
>
>> Independent but related to
>>
>> - https://wiki.php.net/rfc/**constructor-promotion<https://wiki.php.net/=
rfc/constructor-promotion>
>>
>> I wrote an RFC about porting Dart-like Automatic Property Initialization
>> to PHP. Nikic was so generous to provide an initial PoC for it (since I
>> don't do C):
>>
>> - https://wiki.php.net/rfc/**automatic_property_**initialization<https:/=
/wiki.php.net/rfc/automatic_property_initialization>
>> - https://github.com/php/php-**src/pull/474<https://github.com/php/php-s=
rc/pull/474>
>>
>
> I really like the proposal.
>
> I just wonder about how it could mix/conflict with the named parameters
> proposal? Given what you said about Reflection ($this->foo is treated lik=
e
> $foo), then I guess it's not a problem then.
>
> However maybe the RFC should reflect that you can't use:
>
> public function __construct($this->foo, $foo) { =85 }
>
> Also, at first glance I didn't find the "methodless constructor" very
> useful (since it's only saving "{}"), but actually the possibility to use
> this feature in setters too looks very good, it would avoid a lot of
> boilerplate code.


Actually I would prefer to get rid of getters/setters completely and
finally get _real_ accessor methods like in
https://wiki.php.net/rfc/propertygetsetsyntax-v1.2
The ability to shorten the setters is interesting, but it makes them look
"asymetric" to their corresponding getter (which still requires a
body/code) and anyway: It just patches the symptom, that they are required
at all.


>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


--=20
github.com/KingCrunch

--089e01228058f5daea04e75a98dd--