Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75560 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 18517 invoked from network); 15 Jul 2014 19:48:26 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Jul 2014 19:48:26 -0000 Authentication-Results: pb1.pair.com header.from=ajf@ajf.me; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=ajf@ajf.me; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.216 as permitted sender) X-PHP-List-Original-Sender: ajf@ajf.me X-Host-Fingerprint: 192.64.116.216 imap10-3.ox.privateemail.com Received: from [192.64.116.216] ([192.64.116.216:55269] helo=imap10-3.ox.privateemail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 70/D6-15121-98585C35 for ; Tue, 15 Jul 2014 15:48:25 -0400 Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id 9CCB124005D; Tue, 15 Jul 2014 15:48:22 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at imap10.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap10.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id tPk_L1CMFicm; Tue, 15 Jul 2014 15:48:22 -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 464552400C7; Tue, 15 Jul 2014 15:48:17 -0400 (EDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) In-Reply-To: Date: Tue, 15 Jul 2014 20:48:13 +0100 Cc: Rowan Collins , Stas Malyshev , "internals@lists.php.net" Content-Transfer-Encoding: quoted-printable Message-ID: <54536191-1B92-4933-973F-0C8289D13A4C@ajf.me> References: <08503591-EFC8-48E6-984E-FFC292C5EA5F@ajf.me> <16D48604-0C0A-4613-91A4-21392E3A2636@ajf.me> <05CE2216-C5D9-4937-9F2E-AA1407284D9F@ajf.me> <53C460DF.5040304@sugarcrm.com> <53C53A96.2040303@gmail.com> <53C55342.1010207@sugarcrm.com> <53C563B3.6060905@gmail.com> To: Andrey Andreev 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 15 Jul 2014, at 20:43, Andrey Andreev wrote: > I'm sorry, I know what you mean here and I'm not criticizing you > specifically (in fact, I'm intentionally taking it ouf of context), > but that's "PHP internals", not "PHP community". >=20 > The PHP community that I know, wants to have _both_ type cast hinting > and strict type declarations. I=92m not sure that=92s quite the case. There are camps wanting one, = there are camps wanting the other, I suppose some want both, but to me = that seems like a not-a-compromise compromise solution. The point of = this RFC, to some extent, is to be a reasonable compromise between = completely strict declarations and cast hinting, providing the safety of = the first and the flexibility of the second. I think it strikes the = balance well. It=92s also that I, myself, actually would prefer this proposal to = either cast hinting or strict declarations=85 so that=92s three ways to = support if we=92re going down that route. Really, I think we should settle on a compromise, not on one way, the = other, or both. This RFC is a compromise. -- Andrea Faulds http://ajf.me/