Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92827
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 74.125.82.68 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAOfKkdQa7o-WUh5PB+KVnKxwwjtCXuMX0MQUrnOycNCXfePrCg@mail.gmail.com>
References: <BY2PR0201MB178479B3AF8BD49583233034BF6E0@BY2PR0201MB1784.namprd02.prod.outlook.com>
	<CA+kxMuSxAWkNXai0kgW1b1anSohn63frjw76puo1PyCB=xWx=g@mail.gmail.com>
	<CAFMT4NrAshwagmGr6RcadbnLGoe71huA7yYcLYhW-Yf7ohFHGg@mail.gmail.com>
	<571DD94B.3060604@zend.com>
	<571E63D0.8080800@gmail.com>
	<9c24f969-cb0e-cb46-a23c-6e06e7de7d79@gmail.com>
	<571E7C08.6010309@gmail.com>
	<571F1B95.9030203@zend.com>
	<CAFKaYMqbPiHsWJpSKLgV-Yvtpwz9MiA_U243=NRtaTtOrXs+fw@mail.gmail.com>
	<CAFKaYMpzuA6suSDascKppspwAnqSpVviY9J01B=NqbpUfBUqJA@mail.gmail.com>
	<CAFKaYMpTM9VNkAUAKPqbDFjf+3AgJu1Yw1x_rR5-TOp64AjctA@mail.gmail.com>
	<CY1PR0201MB17867883CAF70F426788E531BF630@CY1PR0201MB1786.namprd02.prod.outlook.com>
	<CAOfKkdQa7o-WUh5PB+KVnKxwwjtCXuMX0MQUrnOycNCXfePrCg@mail.gmail.com>
Date: Wed, 27 Apr 2016 00:48:34 +0100
Message-ID: <CAFKaYMq4Z+Lv3j+ds=pc6iOK43fNCaz0cJX3tOt1WA0k2hpv5Q@mail.gmail.com>
To: Pierrick Charron <pierrick@adoy.net>
Cc: PHP internals <internals@lists.php.net>, Dmitry Stogov <dmitry@zend.com>
Content-Type: multipart/alternative; boundary=001a114b245a6946a605316bee9f
Subject: Re: [PHP-DEV] [RFC] PHP Attributes
From: codekestrel@googlemail.com (Dominic Grostate)

--001a114b245a6946a605316bee9f
Content-Type: text/plain; charset=UTF-8

It would, but the short array syntax followed by a function/method decl
would be unambiguous.

On dmitry's note, I'm not sure maintaining similarity with Hack is
justified.  While Facebook maintains it as an open source project, they
primarily built it for themselves, so I can only think they will prioritise
their own needs over that of the PHP community.

This make it an unattractive alternative to PHP in my eyes and it may
explain why there are still so few projects on github written in Hack.  I
don't see any reason why PHP should follow in their footsteps when it
concerns syntax.
On 26 Apr 2016 7:33 p.m., "Pierrick Charron" <pierrick@adoy.net> wrote:

> And it will probably be in conflict with the Short Array Syntax ?
>
> On 26 April 2016 at 13:14, Dmitry Stogov <dmitry@zend.com> wrote:
>
>> Just because HHVM is closer to PHP than C#.
>>
>>
>> ________________________________
>> From: Dominic Grostate <codekestrel@googlemail.com>
>> Sent: Tuesday, April 26, 2016 19:43
>> To: Dmitry Stogov
>> Cc: rowan.collins@gmail.com; PHP internals; Stanislav Malyshev
>> Subject: Re: [PHP-DEV] [RFC] PHP Attributes
>>
>>
>> Why not like C#?
>>
>> [Description("My Function")]
>> function my_function()
>> {}
>>
>> Without the semicolon, this wouldn't be valid in any other context.
>>
>> On 26 Apr 2016 8:41 a.m., "Dmitry Stogov" <dmitry@zend.com<mailto:
>> dmitry@zend.com>> wrote:
>>
>>
>> On 04/25/2016 11:20 PM, Stanislav Malyshev wrote:
>> Hi!
>>
>> No, but this is valid:
>>
>> @atrr(); function foo() { ... }
>>
>> That's perhaps a little too close for comfort...?
>> That's different syntax. If you put ; in the middle of statement, it can
>> change - "$c = $a + $b;" is not the same as "$c = $a; + $b;" - but
>> nobody thinks + can not be used because of that. As I said, << and >>
>> are existing operators too, so if you are creative enough, I'm sure you
>> can find cases like that too.
>>
>> Hi Stas,
>>
>> You may try to replace attribute syntax with @attr(...) (without
>> semicolon) into our PHP parser.
>> Note that we have LALR grammar + restrictions caused by semantic actions.
>> If you are able to do this, I'll add it into the RFC as an option.
>>
>> Thanks. Dmitry.
>>
>>
>> --
>> PHP Internals - PHP Runtime Development Mailing List
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>>
>

--001a114b245a6946a605316bee9f--