Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:80450 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 61335 invoked from network); 14 Jan 2015 09:47:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Jan 2015 09:47:04 -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 74.125.82.51 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 74.125.82.51 mail-wg0-f51.google.com Received: from [74.125.82.51] ([74.125.82.51:37625] helo=mail-wg0-f51.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E1/00-61073-71B36B45 for ; Wed, 14 Jan 2015 04:47:04 -0500 Received: by mail-wg0-f51.google.com with SMTP id x12so7780087wgg.10 for ; Wed, 14 Jan 2015 01:46:59 -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 :content-transfer-encoding; bh=NMq/YSmHmAA1+/SceasAf//wVnyEtx+cbY7QV2j7amU=; b=YWunA7+qAPEA5jaXaJdm+rh4gtR7f7yx+vfyJPLW1L/rNv4PFl02356cAdUOsRZONo 4+9xzyv+PrHsoMGlbNpU6one4vPrhGF35iZet6cW+tXgBu9Pj9aheDChIEw92rulcOGL kDBcih5BDrPwWIXlIuhtFS2dEn+ov5RZ6sdG+5FUq1CJL58MkkKDlZ8eNRp95QzedvxX b3z0pFbtF4XWeudot5Mt+iNUI0GUWAArn52BlGiGJs8sl1xObqgWVO3cRLRgUPFyK6kd iXqR5ipgm/lbRstECs5AlNLImdovUHCU4ybnirIZUx1JWFdcWCPblKamFGLa+ENaJCzQ AuQw== X-Gm-Message-State: ALoCoQkr4zHh6/vol6Oiug0WLY471r1aHy2D1WBIarpBbEu24b1nDzlPypMAG23a3luzo35OIeen+cH+xo1ku7ZhWgwdfc8TuyYPLLRerM8LoO/+nqrMcWJO6RW2/FAUlGYwc6ER9nK1t4YuqQsG0PCNQbPCI5c7UA== X-Received: by 10.180.75.199 with SMTP id e7mr48924322wiw.21.1421228469140; Wed, 14 Jan 2015 01:41:09 -0800 (PST) References: <8DCD1B72-C81D-499E-B455-E4A042CD76E6@ajf.me> <4E2073DE-0951-498C-97BB-DDAC094F11FA@ajf.me> In-Reply-To: <4E2073DE-0951-498C-97BB-DDAC094F11FA@ajf.me> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQGo6gmoLPH7aNIVeHjTN7HPWATOMwFgXHbXAiinDCqc8Z80MA== Date: Wed, 14 Jan 2015 11:41:08 +0200 Message-ID: <9a033dd1f223f854e760924d118ab812@mail.gmail.com> To: Andrea Faulds , Leigh Cc: PHP Internals List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: RE: [PHP-DEV] [RFC] Scalar Type Hints v0.2 From: zeev@zend.com (Zeev Suraski) > -----Original Message----- > From: Andrea Faulds [mailto:ajf@ajf.me] > Sent: Wednesday, January 14, 2015 11:33 AM > To: Leigh > Cc: PHP Internals List > Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints v0.2 > > Hi Leigh, > > > On 14 Jan 2015, at 09:17, Leigh wrote: > > > > I really don't like this behaviour being changed at the call site. If > > I design a function that I _know_ should only take a string, then I > > want it to be an error if the user supplies anything else, so that > > they know they messed up. > > I don=E2=80=99t like the idea of being forced to use strict (or weak) typ= e > checking > because the API author decided as much. I don't either. But I don't like the user to do it either, it's something that is a part of the language definition. I completely agree with both Robert and Leigh. I liked the v0.1 one, but v0.2 is DOA from my point of view. Arguably, from my POV, it's the one option that's even worse than having strict typing exclusively. Zeev