Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75388 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 12312 invoked from network); 13 Jul 2014 10:59:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Jul 2014 10:59:07 -0000 Authentication-Results: pb1.pair.com smtp.mail=ajf@ajf.me; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ajf@ajf.me; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.207 as permitted sender) X-PHP-List-Original-Sender: ajf@ajf.me X-Host-Fingerprint: 192.64.116.207 imap2-2.ox.privateemail.com Received: from [192.64.116.207] ([192.64.116.207:50836] helo=imap2-2.ox.privateemail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9E/00-10122-97662C35 for ; Sun, 13 Jul 2014 06:59:06 -0400 Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id CA6288C0080; Sun, 13 Jul 2014 06:59:02 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at imap2.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap2.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id GZ7eauYj0ttJ; Sun, 13 Jul 2014 06:59:02 -0400 (EDT) Received: from [192.168.0.15] (unknown [90.210.122.167]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id AD6D68C007B; Sun, 13 Jul 2014 06:59:01 -0400 (EDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) In-Reply-To: <53C2178E.7070705@sugarcrm.com> Date: Sun, 13 Jul 2014 11:58:58 +0100 Cc: PHP internals Content-Transfer-Encoding: quoted-printable Message-ID: <59D96FE4-29F5-4562-AF45-9646E73C7CB6@ajf.me> References: <08503591-EFC8-48E6-984E-FFC292C5EA5F@ajf.me> <53C2178E.7070705@sugarcrm.com> To: Stas Malyshev X-Mailer: Apple Mail (2.1878.6) Subject: Re: [PHP-DEV] [RFC] Scalar Type Hinting With Casts (re-opening) From: ajf@ajf.me (Andrea Faulds) On 13 Jul 2014, at 06:22, Stas Malyshev wrote: > I have one request: could we please stop calling it "hinting"? > The dictionary says (http://www.thefreedictionary.com/hint) that > the word "hint" means: >=20 > 1. A slight indication or intimation: wanted to avoid any hint of = scandal. > 2. > a. A brief or indirect suggestion; a tip: stock-trading hints. > b. A statement conveying information in an indirect fashion; a clue: > Give me a hint about the big news. > 3. A barely perceptible amount: just a hint of color. >=20 > What we have in PHP and what is being proposed it not a "slight > indication", not "suggestion" and not "conveying information in = indirect > fashion" (what Python does in PEP-3107 could be called that way, but > it's not what is proposed here). It is very direct specification of > either strict parameter typing or coercive parameter typing. I don't > think using confusing terminology helps anything here. I think it was = a > mistake to introduce this term from the start and we should stop > propagating it. I agree that =93type hinting=94 is a bad name for it. Perhaps =93optional = typing=94 would be better. It conveys that these specifiers are = completely optional, and that there is a system of typing, but it = doesn=92t say anything about its strictness. Regardless, this RFC will stick with the current terminology, but = changing the terminology would be quite simple, you could just update = the manual and possibly change some of the internal names. -- Andrea Faulds http://ajf.me/