Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:80493 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 53986 invoked from network); 14 Jan 2015 20:40:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Jan 2015 20:40:17 -0000 Authentication-Results: pb1.pair.com header.from=dmitry@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=dmitry@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.180 as permitted sender) X-PHP-List-Original-Sender: dmitry@zend.com X-Host-Fingerprint: 209.85.220.180 mail-vc0-f180.google.com Received: from [209.85.220.180] ([209.85.220.180:41081] helo=mail-vc0-f180.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6E/FC-19120-034D6B45 for ; Wed, 14 Jan 2015 15:40:16 -0500 Received: by mail-vc0-f180.google.com with SMTP id im6so3632995vcb.11 for ; Wed, 14 Jan 2015 12:40:13 -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=Liqf3T5jIZVitXhnNjr3k+OlnOW/RfZcI/THB1hZoCQ=; b=GGQWEG9V/m9o5agNFspb4CwVTfjP+0kPEHWFwRX6ceJdczqls0ofHs8G2QSHEAb40n vBVAFHJG4qErMoazeWpPgkxJG0mqBdcO+r4+i1H2U7nSjbcaMv144kyZ1WUYRkkqK900 30Y1hE7PmD1/PY4TfBTyFx+uMNBOj5uL/8h8x1i7Bctk55ogodPWC4H+H67Xrit6OcLu Uqm1uhTGZOMupRUwBjoGHTPe7+dTB+Zwlv8TggWbRbtJZ1GONPE7JMPdAw8dBq5hld7T GNXB8RLJ+HEuzuugk7eDudX9xwJwLuC21e+eTO0NigoDayN4rgI5c/nRQlhF7olI7dH8 M3dw== X-Gm-Message-State: ALoCoQk439SDwp7dDufxXdo3Fyl9YGX7t9F4WOL5tSHtcipgSC5UcTi2gowac83s0fQTUaLqKdNd0WRNWT82ZeFaFq9WaSvHM6iOf2KtX7VRvIvy7kEQix5CeTyKwhWe76fYOGNpvrUji8gTt7aH34KDmcfjwTMILw== MIME-Version: 1.0 X-Received: by 10.220.69.68 with SMTP id y4mr3925906vci.21.1421268013075; Wed, 14 Jan 2015 12:40:13 -0800 (PST) Received: by 10.52.26.40 with HTTP; Wed, 14 Jan 2015 12:40:12 -0800 (PST) In-Reply-To: <8DCD1B72-C81D-499E-B455-E4A042CD76E6@ajf.me> References: <8DCD1B72-C81D-499E-B455-E4A042CD76E6@ajf.me> Date: Thu, 15 Jan 2015 00:40:12 +0400 Message-ID: To: Andrea Faulds Cc: PHP Internals List Content-Type: multipart/alternative; boundary=047d7b3a92520ce8db050ca2bfc0 Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints v0.2 From: dmitry@zend.com (Dmitry Stogov) --047d7b3a92520ce8db050ca2bfc0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable In my opinion, version 0.1 was consistent enough. handling two different approaches just makes mess... We have internal function strlen(string $s), and it may be called with integer argument e.g. strlen(123) -> 3 I think user functions should follow the same rules. If some rules are "bad", lets change that rules for both internal and user functions. But it's better to do it in a separate RFC (after scalar type hinting 0.1 accepted), or we will stick forever. Thanks. Dmitry. On Wed, Jan 14, 2015 at 3:16 AM, Andrea Faulds wrote: > Good evening, > > I=E2=80=99ve made some quite significant changes to my Scalar Type Hints = RFC, and > bumped its version to 0.2. > > Here: https://wiki.php.net/rfc/scalar_type_hints > > This is a new thread because I=E2=80=99ve made a significant revision to = the RFC, > so it=E2=80=99d be sensible to separate discussion of the updated RFC fro= m the v0.1 > RFC. > > Please tell me your thoughts. > > Thanks! > -- > Andrea Faulds > http://ajf.me/ > > > > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --047d7b3a92520ce8db050ca2bfc0--