Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58269
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.170 as permitted sender)
Received-SPF: pass (google.com: domain of kris.craig@gmail.com designates 10.180.80.71 as permitted sender) client-ip=10.180.80.71;
MIME-Version: 1.0
In-Reply-To: <CAGovj_PECsXWH3=a6DvAgnUNGR7e_LyhCpM44ryPQyvyM3=Whw@mail.gmail.com>
References: <CAG=uTXEfTBqX7n0_zfGjB_txQFKtZXF4MOo6RHHPSRPerGeKZA@mail.gmail.com>
	<CAKOpQSwP_VXazO1WgQgOWiKTmgiwzorg2=ii+Mdz58a=TKs6VA@mail.gmail.com>
	<CAGovj_O5UQx9aAaYg302i-kKp13CtBKNLmQ48OLHNvk61rM1sw@mail.gmail.com>
	<1330357150.2159.30.camel@guybrush>
	<CAGovj_MUt60EJfG8a7r-cqrC2PKsi8mqh6v_iyNoRDq8q-jh2Q@mail.gmail.com>
	<CAH-PCH6Bre5yzc6r3zxEj3=zZY0PHDOCVQ0s=f8JBDSPnK+5Fw@mail.gmail.com>
	<CAAyV7nFmfhb97CGAK1ZAkp9qb3oCPxbUDnS-Z-v3cP2APcYs=g@mail.gmail.com>
	<CAH-PCH5mYpAJAyMoyODDSwTvmgpf6ZN_dmC58v0b=K-s-mL0EA@mail.gmail.com>
	<CAAyV7nEpCWE2Gg5MCvfyhGGspgMGB+oYORKK=BKfm48sgXkROA@mail.gmail.com>
	<4F4C1324.2040905@gmail.com>
	<CAKOpQSzop8NuwnD1gPYmgzE2=E5_AHj_N+-ezTp4DFpHXktTqw@mail.gmail.com>
	<A633CF2D7C7BED41B41F1E64F25507B8069DC46C55@MAILR001.mail.lan>
	<CAKOpQSyptTG2=+QtxZoDAB9uh=T=Jgw0DzsAEpTSPv5fGLY7mw@mail.gmail.com>
	<CAL0xaBE9Gnw0teC_VBkGU9Z99g0yZKcu4gnVKqQk6FpfiKt0UQ@mail.gmail.com>
	<CAMyk_Abp7F+EgQe-0o4r79-6=QS_hpm54D4vDEgHzpJdWA9=1A@mail.gmail.com>
	<A633CF2D7C7BED41B41F1E64F25507B8069DC46CAE@MAILR001.mail.lan>
	<CAGovj_PECsXWH3=a6DvAgnUNGR7e_LyhCpM44ryPQyvyM3=Whw@mail.gmail.com>
Date: Tue, 28 Feb 2012 12:09:34 -0800
Message-ID: <CAKOpQSxEenePVK-M37utGzcDg+CTT2kGNauJ2+VpjG35nVkfeg@mail.gmail.com>
To: Michael Morris <dmgx.michael@gmail.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>, Lazare Inepologlou <linepogl@gmail.com>, 
	Arvids Godjuks <arvids.godjuks@gmail.com>
Content-Type: multipart/alternative; boundary=f46d0442887c423d0e04ba0bce3c
Subject: Re: [PHP-DEV] Scalar type hinting
From: kris.craig@gmail.com (Kris Craig)

--f46d0442887c423d0e04ba0bce3c
Content-Type: text/plain; charset=ISO-8859-1

@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 <dmgx.michael@gmail.com>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 <johncrenshaw@priacta.com>
> 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
>
>

--f46d0442887c423d0e04ba0bce3c--