Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84595 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 42907 invoked from network); 11 Mar 2015 22:46:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Mar 2015 22:46:30 -0000 Authentication-Results: pb1.pair.com header.from=bobwei9@hotmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=bobwei9@hotmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain hotmail.com designates 65.55.111.95 as permitted sender) X-PHP-List-Original-Sender: bobwei9@hotmail.com X-Host-Fingerprint: 65.55.111.95 blu004-omc2s20.hotmail.com Received: from [65.55.111.95] ([65.55.111.95:55753] helo=BLU004-OMC2S20.hotmail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AD/D8-32765-2C5C0055 for ; Wed, 11 Mar 2015 17:46:27 -0500 Received: from BLU437-SMTP96 ([65.55.111.73]) by BLU004-OMC2S20.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Wed, 11 Mar 2015 15:46:24 -0700 X-TMN: [IGV3iq31Ku/UADenyRR4JiGq+xsNagRS] X-Originating-Email: [bobwei9@hotmail.com] Message-ID: Content-Type: multipart/alternative; boundary="Apple-Mail=_EBB7D30B-CEE9-4306-92E1-A48DFD0700D5" MIME-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) In-Reply-To: Date: Wed, 11 Mar 2015 23:46:19 +0100 CC: PHP internals References: To: Pierre Joye X-Mailer: Apple Mail (2.2070.6) X-OriginalArrivalTime: 11 Mar 2015 22:46:22.0391 (UTC) FILETIME=[328A5C70:01D05C4D] Subject: Re: [PHP-DEV] [RFC] Basic Scalar Types From: bobwei9@hotmail.com (Bob Weinand) --Apple-Mail=_EBB7D30B-CEE9-4306-92E1-A48DFD0700D5 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="us-ascii" > Am 11.03.2015 um 23:23 schrieb Pierre Joye : > On Mar 12, 2015 8:30 AM, "Bob Weinand" > wrote: > > > > Hi all, > > > > after all, some people are not happy with the current proposals = about scalar types. So, they both still possibly may fail. > > > > Thus, I'd like to come up with a fallback proposal in case both = proposals fail: > > > > https://wiki.php.net/rfc/basic_scalar_types = > > > > It shouldn't prevent any future improvements and still give use all = the advantages of scalar types. >=20 > Besides what I think of proposing yet another RFC, -1 because it is = basically what the initial idea from the opponents of optional strict = mode wanted before they go with the latest one. It also totally ignore = what the Anthony's proposes. >=20 Correct. It's just for the case where the other two fail. We still can add strict mode in a later version if people need it. All the RFC does is the most basic scalar type hinting you can build = everything on. (for example adding the declare(strict_types=3D1); would = work without any BC break on top of it) I see that it doesn't fit all the users, but there's still room for = improvement in later versions. Bob= --Apple-Mail=_EBB7D30B-CEE9-4306-92E1-A48DFD0700D5--