Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71995 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 75490 invoked from network); 2 Feb 2014 12:31:15 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Feb 2014 12:31:15 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.204 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.204 mail4.serversure.net Linux 2.6 Received: from [217.147.176.204] ([217.147.176.204:47915] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 09/5A-30967-09A3EE25 for ; Sun, 02 Feb 2014 07:31:13 -0500 Received: (qmail 12085 invoked by uid 89); 2 Feb 2014 12:31:10 -0000 Received: by simscan 1.3.1 ppid: 12078, pid: 12081, t: 0.1263s scanners: attach: 1.3.1 clamav: 0.96/m:52 Received: from unknown (HELO linux-dev4.lsces.org.uk) (lester@rainbowdigitalmedia.org.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 2 Feb 2014 12:31:09 -0000 Message-ID: <52EE3B2E.5040307@lsces.co.uk> Date: Sun, 02 Feb 2014 12:33:50 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 SeaMonkey/2.23 MIME-Version: 1.0 To: internals@lists.php.net References: <98.E0.35265.E17FBE25@pb1.pair.com> <52ED66CC.8070304@ajf.me> <52ED9D74.8080807@ajf.me> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [VOTE] Automatic Property Initialization From: lester@lsces.co.uk (Lester Caine) Sara Golemon wrote: >> Imho HHVMs syntax has the massive flaw that you cannot use docblocks on >> >those properties anymore, which is not the case with this RFC. All other >> >things equal, this is why this RFC should clearly be favored. > Inclined to agree on the matter of getters/setters (though I regard > the docblock issue as trivially solvable, and the typehint/verbosity > issue as a non-issue). Having 10+ years of legacy code which is built on a base of previous PHP4 code, docblock is central to my own work practices. PHPEclipse simply picks up these and provides annotation from them but is still a little behind on the 'newer' changes which are now causing problems with third party libraries. I did have a look at HHVM and failed because of the legacy code, but that was a little while ago and I've not reviewed it recently. However I'm sure that there is probably as much work moving the code to HHVM as there is remaining still to move it forward toPHP5.5. It is all these little incremental changes which unless one spends time actually clearing things each version update, eventually catch up to the point where even PHP will not run code, let alone being cross compatible with things like HHVM? Making even simple PHP code runnable everywhere is a little of a pipe dream at the moment. Even if you know how to configure the ini file to enable legacy code to run, you then have to find the correct versions of third party libraries to run with it. -- 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