Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68103 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 60567 invoked from network); 11 Jul 2013 20:48:26 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Jul 2013 20:48:26 -0000 Authentication-Results: pb1.pair.com header.from=php@golemon.com; sender-id=softfail Authentication-Results: pb1.pair.com smtp.mail=php@golemon.com; spf=softfail; sender-id=softfail Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.220.46 as permitted sender) X-PHP-List-Original-Sender: php@golemon.com X-Host-Fingerprint: 209.85.220.46 mail-pa0-f46.google.com Received: from [209.85.220.46] ([209.85.220.46:52671] helo=mail-pa0-f46.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A9/F6-03322-81A1FD15 for ; Thu, 11 Jul 2013 16:48:25 -0400 Received: by mail-pa0-f46.google.com with SMTP id fa11so8309556pad.33 for ; Thu, 11 Jul 2013 13:48:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=SE7WIh/YYesoez4z8sOgEZU2EBhVyy7VzJfWyf+03qE=; b=jy+Io4TrCiwWvvIWjTDPcPXq3PHb+Oy7oRTl2Enp33hapEh8x94qWydMRhDq77YySz 6WzdgsZBWvF85hguQhykJZSNSdAOrCtfsaeWC4xQfHTEI49902jb3Te5TVOwqoYiv0DK TBHH0PaBviNuCKLY99meS/bAIfFqeq1fRfpUEGM9w7rdP4F/pgSGivuE/X5WL8BZjScJ e3OmrBYhcnQzjDVPnRVIC3m/KPAltEWukFO+uIAkQd0NEHprqEgPl67Jg5COBvQDB68R MTgZZb95tMqnOTEYfkmuAZOeWYpp9EhRkARzp4oHm6f2A5JlTJBvXx7ZgWqNSpqIfWWh NR4A== MIME-Version: 1.0 X-Received: by 10.68.203.137 with SMTP id kq9mr38186536pbc.190.1373575701742; Thu, 11 Jul 2013 13:48:21 -0700 (PDT) Sender: php@golemon.com Received: by 10.70.132.105 with HTTP; Thu, 11 Jul 2013 13:48:21 -0700 (PDT) X-Originating-IP: [2620:0:1cfe:18:22c9:d0ff:fe87:295b] In-Reply-To: <51DF17FD.5030401@sugarcrm.com> References: <1372258135.2410.22.camel@guybrush> <51DF0CDD.7060108@sugarcrm.com> <51DF17FD.5030401@sugarcrm.com> Date: Thu, 11 Jul 2013 13:48:21 -0700 X-Google-Sender-Auth: rmlJ0jnmnQDewpLKjnM-cKLbWT4 Message-ID: To: Stas Malyshev Cc: Florin Patan , "RQuadling@gmail.com" , PHP internals Content-Type: multipart/alternative; boundary=047d7b15aabdc6590304e14283c7 X-Gm-Message-State: ALoCoQktU2mWfsS8oduPElPgnuwLV4VBrRk12RicihhnfYVDqbDoD1tTuHH8p/PEfC5b2avR+xep Subject: Re: [PHP-DEV] Request for comments - new PHP feature: return typing From: pollita@php.net (Sara Golemon) --047d7b15aabdc6590304e14283c7 Content-Type: text/plain; charset=ISO-8859-1 > > > 1) HHVM isn't just running FB. A number of sites have either already > started using HHVM, or intend to soon. > > Were could I read about those? > > I didn't list any because I don't know how they individually feel about sharing that info. I realize that takes the wind out of my statement, but there it is. > > 2) The "static compilation" description is grossly outdated information. > > I guess my knowledge about HHVM is a bit out of date, which is no wonder > as I wasn't following latest developments for some time. Could you send > a link where I (and everybody interested of course :) could read about > the current state of affairs? > > Apart from the documentation distributed with HHVM, you could look at our blog http://www.hiphop-php.com/ which includes a walkthrough in getting WordPress running http://www.hiphop-php.com/wp/?p=113 > > however, as with Generators, I think that we should endeavor to keep the > > implementations close together by the most appropriate means. I don't > > want two versions of PHP syntax. > > I don't think whatever HHVM does without input from PHP community should > be any argument for any change in PHP. If it is good for PHP, it can > stand on its own merit, if it's not, then the fact that HHVM team did it > for some internal reasons that we do not know can not be an argument. > > If we want a common PHP syntax that will be followed by different > implementations, it's a great idea, but it can not start with "we > already did it, so you have to do it too". I don't want many versions of > PHP syntax either, but I don't think HHVM team should be the one > deciding how the one version looks like. If they use syntax that is good > (I think this specific one is not, but that's beside the point, as it is > only my personal opinion) it can and should be argued on its own merits, > not on the argument that it is in HHVM. > > I never stated, not intended to state, "we already did it, so you have to do it too". Please do not put words into my mouth. I think it should be a part of the conversation, not a dominant part, but a part. Of course every new feature should be argued on its own merits. Please do not suggest that I think otherwise. --047d7b15aabdc6590304e14283c7--