Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71962 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 9442 invoked from network); 2 Feb 2014 02:06:29 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Feb 2014 02:06:29 -0000 Authentication-Results: pb1.pair.com smtp.mail=kontakt@beberlei.de; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=kontakt@beberlei.de; sender-id=unknown Received-SPF: error (pb1.pair.com: domain beberlei.de from 74.125.82.177 cause and error) X-PHP-List-Original-Sender: kontakt@beberlei.de X-Host-Fingerprint: 74.125.82.177 mail-we0-f177.google.com Received: from [74.125.82.177] ([74.125.82.177:64272] helo=mail-we0-f177.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F2/2E-30967-328ADE25 for ; Sat, 01 Feb 2014 21:06:29 -0500 Received: by mail-we0-f177.google.com with SMTP id t61so918854wes.8 for ; Sat, 01 Feb 2014 18:06:24 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=alS9g3fsIN6QWGdfkqi0MDGWIL7kAhhTA9pjR+vnP2c=; b=ZtSjSxIX+nL6CjeZX3VwL83nOsmrtrBO50HOF5nnyFL1+FhSiEiW7ELYfuaYWy43bW 6vE55x6Dg2v/0d0rU2Ajrncgoem7bkG43VKzhM6IAjTZJ3KqvQlXTapgZ8da9ljngYEP xniMmn8nKD439Co/nAvuWBrsUiXA1sZfbR1Tqgi9GEm9eoGOvz99mCKfanaXtltQ+a4m ZWtWCJMzx8Typ3RZp+sJXxDSMyM9CKm+5rfjHMOUnp/5dGZzwD4qR8kRgOKh+swFYZ2M aD/3dNMifJ73uEQOSWzMnY3ZD2G1HAfUfHPcbhIv1J0ydPzNbLEQfKwfhG0NqBd954fX OnXw== X-Gm-Message-State: ALoCoQn4wFqr2Rysts5e/Gjpz50elbcGsnCKh3LZtaM7eWUDqpCxSbwtXXbxJYeSSvz8utNN2IAf MIME-Version: 1.0 X-Received: by 10.194.142.170 with SMTP id rx10mr3998907wjb.13.1391306784851; Sat, 01 Feb 2014 18:06:24 -0800 (PST) Received: by 10.194.124.211 with HTTP; Sat, 1 Feb 2014 18:06:24 -0800 (PST) X-Originating-IP: [77.180.243.239] In-Reply-To: References: <98.E0.35265.E17FBE25@pb1.pair.com> <52ED66CC.8070304@ajf.me> <52ED9D74.8080807@ajf.me> Date: Sun, 2 Feb 2014 03:06:24 +0100 Message-ID: To: Sara Golemon Cc: Andrea Faulds , Gordon Oheim , PHP internals Content-Type: multipart/alternative; boundary=089e013a22ccaf67af04f162daf5 Subject: Re: [PHP-DEV] [VOTE] Automatic Property Initialization From: kontakt@beberlei.de (Benjamin Eberlei) --089e013a22ccaf67af04f162daf5 Content-Type: text/plain; charset=ISO-8859-1 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. Also with typehints or - unlikely but possible - property-accesors the hhvm syntax will become very verbose for the __construct line, wheras this RFC can handle those cases without having to think about future compatibility. On Sun, Feb 2, 2014 at 2:32 AM, Sara Golemon wrote: > On Sat, Feb 1, 2014 at 5:20 PM, Andrea Faulds wrote: > > On 02/02/14 01:18, Sara Golemon wrote: > >> Who said anything about blocking? I just don't think the approaches > >> have been contrasted enough to be able to say we've done due > >> diligence. Don't put words in my mouth. > > > > I don't know who said anything about blocking, where does my email > mention > > it? > > > My bad, that was Gordon. Just getting peeved at having my motivations > and intentions called into question for having the audacity to want to > keep our implementations consistent. But hey, let's just all invent > random bits of syntax, who cares about the users, right? > > -Sara > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --089e013a22ccaf67af04f162daf5--