Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92041
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.52 as permitted sender)
To: internals@lists.php.net
References: <CABDNdAHwgx+LJRc_gi9citiypxxWVGFMB+6hrmU+vVYDWCDV_g@mail.gmail.com>
 <3F.70.02405.6803BE65@pb1.pair.com> <56F01545.8080008@gmail.com>
 <CAF+90c-Z82kBT18ivvKejD5_dBf=dtbNYN-cZcyO1K=0C1WcLA@mail.gmail.com>
 <56F14572.701@gmail.com> <56F15EF5.80006@telia.com>
 <56F16023.1010002@gmail.com>
 <CAPhkiZxYwXKLp8ASkjiwXgzDtjKxJ8rYROCM-t=8sU5=efhg2w@mail.gmail.com>
 <CAPhkiZwOJOkNu4N=h+wQRX4w8-KV=zg9x4khhLRLu199YcqZxw@mail.gmail.com>
 <CABDNdAGh4OjkkEQim6oYK=sZ=zj1Q==HzE=SLJ1E8=a=ku1DqA@mail.gmail.com>
 <CY1PR0201MB17863E4B9D9F53151A900DCDBF870@CY1PR0201MB1786.namprd02.prod.outlook.com>
 <CAL=_i_mNwmpg0PWmrm3nTZxn6s33u2QUzavk8w0Fk1OGvbWJtA@mail.gmail.com>
 <CY1PR0201MB1786AAFDC6170AB1585CA7F5BF870@CY1PR0201MB1786.namprd02.prod.outlook.com>
 <CY1PR0201MB17867DAC10D401EE9EC49CBCBF870@CY1PR0201MB1786.namprd02.prod.outlook.com>
 <CAL=_i_knwzrcXdx1k4ii8YKzrgaREBFcHYGC9ZV_J05ZWVWmzg@mail.gmail.com>
 <56FC4ED6.6050701@telia.com>
 <CAL=_i_ksOzCV1SUtB2jwSYPm1SL2y3jy43+JSZ3k6KRywsizUg@mail.gmail.com>
Message-ID: <56FCEBCC.8040205@gmail.com>
Date: Thu, 31 Mar 2016 10:20:12 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CAL=_i_ksOzCV1SUtB2jwSYPm1SL2y3jy43+JSZ3k6KRywsizUg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC Discussion] Typed Properties
From: rowan.collins@gmail.com (Rowan Collins)

Hi Joe,

Just my €0.02

Joe Watkins wrote on 31/03/2016 09:34:
> public $bar, int $foo;
>
> What does this mean?
>
> If it's not an error, what does this mean ?

To me, that should be an error; why would you want to group typed and 
untyped properties on one line?


> public $bar, int $foo, $qux;
>
> If it's an error, why is it an error ?

Again, an error, because you are grouping the properties but giving them 
different types. It's an error for the same reason that "public $foo, 
private $bar" is an error - the keywords should all come before the list 
of names, not in the middle of it.


>
> Both of these examples are just as ambiguous as
>
> public int $foo, $bar, $qux;

To me, this is completely unambiguous - you have three properties, 
you've grouped them together, so they're all the same. It reads 
naturally to me as "three properties, with public visibility and int 
type, called $foo, $bar, and $qux".


> Access modifiers are assumed to apply to all declarations in a group,
> because that's what grouping is actually for.
>
> We don't need to make grouping about types, we need to make type
> declarations unambiguous.

It's not "making grouping about types", it's applying the same rules for 
grouping types as we apply for grouping visibilities.


Regards,
-- 
Rowan Collins
[IMSoP]