Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92726
Return-Path: <lester@lsces.co.uk>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 28241 invoked from network); 25 Apr 2016 11:49:28 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 25 Apr 2016 11:49:28 -0000
Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown
Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error)
X-PHP-List-Original-Sender: lester@lsces.co.uk
X-Host-Fingerprint: 217.147.176.214 mail4-2.serversure.net Linux 2.6
Received: from [217.147.176.214] ([217.147.176.214:38365] helo=mail4.serversure.net)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id AF/45-00233-6440E175 for <internals@lists.php.net>; Mon, 25 Apr 2016 07:49:27 -0400
Received: (qmail 436 invoked by uid 89); 25 Apr 2016 11:49:23 -0000
Received: by simscan 1.3.1 ppid: 424, pid: 432, t: 0.0757s
         scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677
Received: from unknown (HELO ?10.0.0.7?) (lester@rainbowdigitalmedia.org.uk@81.138.11.136)
  by mail4.serversure.net with ESMTPA; 25 Apr 2016 11:49:23 -0000
To: internals@lists.php.net
References: <BY2PR0201MB178479B3AF8BD49583233034BF6E0@BY2PR0201MB1784.namprd02.prod.outlook.com>
 <CA+kxMuSxAWkNXai0kgW1b1anSohn63frjw76puo1PyCB=xWx=g@mail.gmail.com>
 <571DD85B.50500@zend.com>
Message-ID: <571E0443.3070904@lsces.co.uk>
Date: Mon, 25 Apr 2016 12:49:23 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <571DD85B.50500@zend.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] PHP Attributes
From: lester@lsces.co.uk (Lester Caine)

On 25/04/16 09:42, Dmitry Stogov wrote:
> I know, any syntax is going to be loved by ones and hated by others...
> It's not possible to satisfy everyone.

If one takes a step back, current well used annotation IS provided but
not cleanly documented in the docbloc material that is a major element
of legacy code. There is clearly a case for improving the usage of this
style of working, and adding 'attributes' to the rest of the rest of
this annotation seems to me to be the best way forward for a STOCK PHP
install. Every current IDE I've seen will correctly display docbloc
annotation and has the option to disable tags in that code if required.

I'm looking at the <?hh examples in hack and thinking that this is an
example of where an 'hack compatibility' extension to PHP may have a
place, but adoption some hack rules such as <<>> then imples that <?
code should work the same as <?hh code. That does not seem the right way
forward for users who have no intention to use hack and have no access
to it on their hosting? More important, and subtle differences will
cause even more problems? So can we not maintain a more flexible roadmap
that cherry picking other languages directly?

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk