Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:58270 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 46161 invoked from network); 28 Feb 2012 20:15:33 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Feb 2012 20:15:33 -0000 Authentication-Results: pb1.pair.com smtp.mail=ircmaxell@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ircmaxell@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.49 as permitted sender) X-PHP-List-Original-Sender: ircmaxell@gmail.com X-Host-Fingerprint: 209.85.216.49 mail-qw0-f49.google.com Received: from [209.85.216.49] ([209.85.216.49:63328] helo=mail-qw0-f49.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B8/B1-36673-4E53D4F4 for ; Tue, 28 Feb 2012 15:15:33 -0500 Received: by qafi29 with SMTP id i29so1085354qaf.8 for ; Tue, 28 Feb 2012 12:15:30 -0800 (PST) Received-SPF: pass (google.com: domain of ircmaxell@gmail.com designates 10.224.111.16 as permitted sender) client-ip=10.224.111.16; Authentication-Results: mr.google.com; spf=pass (google.com: domain of ircmaxell@gmail.com designates 10.224.111.16 as permitted sender) smtp.mail=ircmaxell@gmail.com; dkim=pass header.i=ircmaxell@gmail.com Received: from mr.google.com ([10.224.111.16]) by 10.224.111.16 with SMTP id q16mr15475103qap.56.1330460130199 (num_hops = 1); Tue, 28 Feb 2012 12:15:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VZ8vuVzfXfJFaZAdF072orWN55WipnQ9f92lwy1XZh4=; b=TcnK6YMcEwBiviQ99PnaFWkAy5uxcp/bKK8koa7JGYlLONc+ezvyCMutWd8NIbsR02 0g7nYwtWiP4PWPszyvX8R9IsHsBxyBWbQMdGD1hKkHV6dDrAGVTzYB4SsBsgYRqUXoDQ Fe2F5qWi3KJa5VahF/Si0KCmun9RmV2vU+EVI= MIME-Version: 1.0 Received: by 10.224.111.16 with SMTP id q16mr13051032qap.56.1330460130062; Tue, 28 Feb 2012 12:15:30 -0800 (PST) Received: by 10.229.166.202 with HTTP; Tue, 28 Feb 2012 12:15:29 -0800 (PST) Received: by 10.229.166.202 with HTTP; Tue, 28 Feb 2012 12:15:29 -0800 (PST) In-Reply-To: References: <1330357150.2159.30.camel@guybrush> <4F4C1324.2040905@gmail.com> Date: Tue, 28 Feb 2012 15:15:29 -0500 Message-ID: To: Kris Craig Cc: "internals@lists.php.net" , Arvids Godjuks , Michael Morris , Lazare Inepologlou Content-Type: multipart/alternative; boundary=20cf3074d9e070b2bb04ba0be31f Subject: Re: [PHP-DEV] Scalar type hinting From: ircmaxell@gmail.com (Anthony Ferrara) --20cf3074d9e070b2bb04ba0be31f Content-Type: text/plain; charset=ISO-8859-1 Can I make a suggestion? Instead of an rfc, can we collate the existing discussion into an easier to digest format (historical as well). Summarize the conversations and existing rfcs with the discussion around them (including the pros/cons and problems). That way we have a point of reference and comparison with which to base the rfc on, and a way to judge and rate the rfc... Anthony On Feb 28, 2012 3:09 PM, "Kris Craig" wrote: > @Michael Would you be willing to delay that? Rather than create a bunch of > new RFC's, I was thinking it might be better if all interested parties came > together on some other communication medium and worked on a single, > collaborative RFC instead. > > --Kris > > > On Tue, Feb 28, 2012 at 12:00 PM, Michael Morris >wrote: > > > Thank you. > > > > Now I'm going to go work up a detailed RFC for what I posted earlier > > with some additional clarification as to when errors should and > > shouldn't be thrown. > > > > On Tue, Feb 28, 2012 at 2:53 PM, John Crenshaw > > > wrote: > > > OK everyone, it seems that some people have forgotten or missed the > > original agreement that this thread started with. There is a > communication > > disconnect ("strict typing" means horribly different things to different > > people right now). Please read through and understand the following > > terminology before continuing to post on this thread. We've agreed to the > > following terms: > > > > > > - "Strict Typing" means the super strict old C style typing *with no > > implicit conversions*. (If you really think this is what you want, you > are > > probably mistaken. Look through prior discussions on this topic. This > fails > > for numerous reasons, including the fact that almost every input to PHP > is > > a string.) > > > - "Weak Typing" means types in the same sense that the PHP > documentation > > uses types (for example, the docs indicate substr(string, integer), and > > substr(12345, "2") == "345".) (If you think you want "strict typing", > this > > is probably what you mean.) > > > - "No Scalar Typing" should be used to indicate the current system > > (where there is no provision for hinting at scalar types.) > > > > > > In addition, if someone potentially new expresses support for "Strict > > Typing", please assume that they really mean weak typing unless proven > > otherwise (this is by far the more likely intent.) Don't get mean, > politely > > clarify terminology so that everyone can be on the same page. If someone > > still insists that they want "Strict Typing" (as defined above), point > them > > to the prior discussions on the topic which explain exactly what the > > problems with this are. > > > > > > John Crenshaw > > > Priacta, Inc. > > > > -- > > PHP Internals - PHP Runtime Development Mailing List > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > --20cf3074d9e070b2bb04ba0be31f--