Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:82500 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 90546 invoked from network); 11 Feb 2015 23:08:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Feb 2015 23:08:37 -0000 Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.213.180 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 209.85.213.180 mail-ig0-f180.google.com Received: from [209.85.213.180] ([209.85.213.180:53760] helo=mail-ig0-f180.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B2/F3-02515-4F0EBD45 for ; Wed, 11 Feb 2015 18:08:37 -0500 Received: by mail-ig0-f180.google.com with SMTP id b16so215918igk.1 for ; Wed, 11 Feb 2015 15:08:33 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=c7PeKB0KmJJMWbHZFy6nSpzj0LuMlObAfceYtBOOmN8=; b=kK1gLHw3BFGKx79/bPedGntssygrvbuNm9oIDEyPiwvW66Xv0i+gukeLXa1OZFAZeV XI1mwe4B6wUnufeTtnnffFeFp+rsB4Kkj+6ZQpGMeIzo3smoyIWm7yCZAb84FyQyrG1J Y01x0Y/iiLWuUO6a5lpU76sWV+cssZ+oVyekXJEimsavQO8YJkMxqBPgR3yILySXifWN TrcBCinRgz46YoEb655Iu/fkK66UnypSEn/XCkUmADbrOV+feiVQ2lONnDmcypp760m6 SUF3RTsYBHpt6wUKUMTIY1smjrmdUN1PVBK/ELyV/IwaWDPG06kbwU2tNahlVJTk+UKx Ulyw== X-Gm-Message-State: ALoCoQnJVTsbjfFNWqo94DR0byyhQHhx1xqDs1SbtiB5WtbmHGxYflYFM81qgyIw2X5tB1s9uqbdBPuPLqSNxBROHYw6zBWE4VOikftO2v3Z5TFTLKDi3IHxjNYTrJkMPZIfngWsh+q1cqb7oHU//kfxB+Fr4I0GEw== X-Received: by 10.42.211.200 with SMTP id gp8mr5584040icb.93.1423696107843; Wed, 11 Feb 2015 15:08:27 -0800 (PST) References: <8703B53E-2C4A-4AC6-95C4-D4F19C6D5221@ajf.me> <54DAF884.7000508@lerdorf.com> <203e611c8e0b03568a868b8d931aec37@mail.gmail.com> In-Reply-To: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQJMIZG9mXkdirFXmuP9r5ZK3xIuzQJbJJA/AzCIQggCYWllLQKBurkXAYsw6s4B6qYCMgHjX/2Gm3YXPnA= Date: Thu, 12 Feb 2015 01:08:26 +0200 Message-ID: To: guilhermeblanco@gmail.com Cc: Rasmus Lerdorf , PHP Internals Content-Type: multipart/alternative; boundary=20cf301d41c4c6cf2f050ed81439 Subject: RE: [PHP-DEV] [VOTE] Scalar Type Hints From: zeev@zend.com (Zeev Suraski) --20cf301d41c4c6cf2f050ed81439 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I said numerous times that I think that v0.1 of Andrea=E2=80=99s RFC was ri= ght on the mark. I=E2=80=99d vote in its favor in a heartbeat. It gives the exac= t same value from an API author=E2=80=99s point of view. It gives the exact same = value in terms of potential performance improvements/JITting/compilation insight. But unlike the current RFC, v0.1 doesn=E2=80=99t introduce an IMHO alien co= ncept into a language that considered dynamic typing to be a core principle since its birth. Zeev *From:* guilhermeblanco@gmail.com [mailto:guilhermeblanco@gmail.com] *Sent:* Thursday, February 12, 2015 12:46 AM *To:* Andrea Faulds *Cc:* Zeev Suraski; Rasmus Lerdorf; PHP Internals *Subject:* Re: [PHP-DEV] [VOTE] Scalar Type Hints Hi all, @Zeev and @Rasmus: Seriously, you both mentioned that consider the idea of scalar type hint, but I've never seen which idea would you consider. Andrea built a very flexible way to operate and even though I don't fully agree either, it's the best so far. This approach does have headaches, but would you ever consider a strict or weak only approach? --20cf301d41c4c6cf2f050ed81439--