Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58343
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.24.166 as permitted sender) client-ip=10.180.24.166;
MIME-Version: 1.0
In-Reply-To: <de418e115ec35d6471a9143753be164a.squirrel@www.l-i-e.com>
References: <CAG=uTXEfTBqX7n0_zfGjB_txQFKtZXF4MOo6RHHPSRPerGeKZA@mail.gmail.com>
	<CAH-PCH6Bre5yzc6r3zxEj3=zZY0PHDOCVQ0s=f8JBDSPnK+5Fw@mail.gmail.com>
	<CAAyV7nFmfhb97CGAK1ZAkp9qb3oCPxbUDnS-Z-v3cP2APcYs=g@mail.gmail.com>
	<CAKOpQSwTGMcuGs5fDvA0kF7QJamooU7hnqtDFMaCh80amt7kcQ@mail.gmail.com>
	<CAKOpQSx_tJfrRx4uRDfcP94bN1qYw=WOktCKf3Xt-AizN=Lk0A@mail.gmail.com>
	<ee25d764561a39bb5b4459b3bd7e7089.squirrel@www.l-i-e.com>
	<A633CF2D7C7BED41B41F1E64F25507B8069DC46C3A@MAILR001.mail.lan>
	<CAKOpQSyxDDqiaXQbVZHE-5K_hOS8dOx4g6Bsj+yJ9BjmTOMh8Q@mail.gmail.com>
	<693e15008681dfe7372eaea66214f8a8.squirrel@www.l-i-e.com>
	<CAKOpQSxh78xMqm=aQ1jBx1T4VJ-BfKHQkxha4B=mHe6TAeiQGw@mail.gmail.com>
	<A633CF2D7C7BED41B41F1E64F25507B8069DC46CEF@MAILR001.mail.lan>
	<CAKOpQSyyXfuCmcx63EgoQa-pkUxT+STS=TNOJvTQ1JEwG=VKow@mail.gmail.com>
	<4F4D5D44.5090307@developersdesk.com>
	<CAGovj_MuUqMaVb_dPTNvTPkD3BcNPGkx88i5uQbbVe=j+dGA8Q@mail.gmail.com>
	<CAKOpQSx0mgixv3DA8FS0hL5QNb-8p5v6u=jYQ5d7HRuAVr6P1Q@mail.gmail.com>
	<de418e115ec35d6471a9143753be164a.squirrel@www.l-i-e.com>
Date: Wed, 29 Feb 2012 11:09:45 -0800
Message-ID: <CAKOpQSx56j=TFnbcbxJvW5-jPBAHyBXs=RK87rN9pU+gXssNfg@mail.gmail.com>
To: Richard Lynch <ceo@l-i-e.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary=f46d041826102fa24f04ba1f16f4
Subject: Re: [PHP-DEV] Scalar type hinting
From: kris.craig@gmail.com (Kris Craig)

--f46d041826102fa24f04ba1f16f4
Content-Type: text/plain; charset=ISO-8859-1

@Richard I think you made a very good point.  Should we treat a float =>
int mismatch the same as we would a string => int mismatch, or should the
former fail more gracefully?  I can see good arguments for both.

--Kris


On Wed, Feb 29, 2012 at 10:02 AM, Richard Lynch <ceo@l-i-e.com> wrote:

> On Tue, February 28, 2012 5:17 pm, Kris Craig wrote:
>
> Some cases I would find interesting to be explained:
>
> (using 'streak' for strong and/or weak, feel free to separate the two)
>
> streak int $i = 123.456; //Common idiom for floor()
> streak int $i = "123.456"; //In contrast to previous
> streak int $i = "1 "; //value="1 " is ridiculously common HTML
>
> It's all well and good to say that any loss of data is "bad" and to
> raise some E_* for it, but there are some idioms so common that feel
> "wrong" as I consider them...
>
> If everyone "for" the new type hinting/forcing can reach consensus on
> these sorts of cases, it would help clarify any RFCs a bit, I think
>
> wrt E_RECOVERABLE_ERROR vs E_WARNING
>
> If current type hinting raises E_RECOVERABLE_ERROR, I have no
> objection to following that lead, with the explicit caveat that a
> change to the existing type-hinting to E_WARNING, as unlikely as that
> seems, would pull the new "streak" with it.
>
> I don't even object to using E_ERROR for the "strong" variant, if that
> passes review, really, since "strong" is, errr, strong. :-)
>
> Anybody who doesn't like the E_* can re-define them in a custom error
> handler anyway, though allowing PHP to continue after E_ERROR is like
> playing russian roulette...
>
> --
> brain cancer update:
> http://richardlynch.blogspot.com/search/label/brain%20tumor
> Donate:
>
> https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=FS9NLTNEEKWBE
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--f46d041826102fa24f04ba1f16f4--