Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58398
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.170 as permitted sender)
Received-SPF: pass (google.com: domain of linepogl@gmail.com designates 10.236.177.6 as permitted sender) client-ip=10.236.177.6;
MIME-Version: 1.0
In-Reply-To: <A633CF2D7C7BED41B41F1E64F25507B8069DC46DC7@MAILR001.mail.lan>
References: <CAG=uTXEfTBqX7n0_zfGjB_txQFKtZXF4MOo6RHHPSRPerGeKZA@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> <CAKOpQSx56j=TFnbcbxJvW5-jPBAHyBXs=RK87rN9pU+gXssNfg@mail.gmail.com>
 <A633CF2D7C7BED41B41F1E64F25507B8069DC46DC0@MAILR001.mail.lan>
 <f7238224c6b990a4930011352aa897c3.squirrel@www.l-i-e.com> <A633CF2D7C7BED41B41F1E64F25507B8069DC46DC6@MAILR001.mail.lan>
 <CAJWj5+GGZQx=Jq0NacxHxrvUuDhSiJ4b7LrNTtqGJcfQBbgprQ@mail.gmail.com> <A633CF2D7C7BED41B41F1E64F25507B8069DC46DC7@MAILR001.mail.lan>
Date: Thu, 1 Mar 2012 10:10:02 +0100
Message-ID: <CAMyk_AajE4-fBFAKSiLnKVcQ=jmrBiMtsr==9HBo066fFg=ezA@mail.gmail.com>
To: John Crenshaw <johncrenshaw@priacta.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=20cf3056390170aba504ba2ad4cb
Subject: Re: [PHP-DEV] PHP Philosophy (was RE: [PHP-DEV] Scalar type hinting)
From: linepogl@gmail.com (Lazare Inepologlou)

--20cf3056390170aba504ba2ad4cb
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

> That's what I was calling "inconsistent", specifically because (int)'foo'
> =3D=3D 0 with no warning whatsoever, but int $a =3D 'foo' would be 0 with=
 an
> error of some sort. Behavior with respect to when an error is raised is
> inconsistent. In both cases there is a very lossy conversion, why is ther=
e
> an error in one case and not the other? Inconsistent.
>

+1

However, I would love to have int $a =3D 'foo' cast to 0 without any error.

New functionality without breaking BC.



Lazare INEPOLOGLOU
Ing=C3=A9nieur Logiciel


2012/3/1 John Crenshaw <johncrenshaw@priacta.com>

> From: Simon Schick [mailto:simonsimcity@googlemail.com]
> >
> > Hi, John
> >
> > Just to add an idea to yours ..
> >
> > Do you think it's a compatibility-break if we'd decide to send a
> E_NOTICE or E_WARNING if we f.e. try to give a string to a method that ju=
st
> allows integer for this argument?
> No break at all, just a E_NOTICE or E_WARNING as the script can succeed
> anyways.
> >
> > Bye
> > Simon
>
> That's what I was calling "inconsistent", specifically because (int)'foo'
> =3D=3D 0 with no warning whatsoever, but int $a =3D 'foo' would be 0 with=
 an
> error of some sort. Behavior with respect to when an error is raised is
> inconsistent. In both cases there is a very lossy conversion, why is ther=
e
> an error in one case and not the other? Inconsistent.
>
> On the other hand if you add an error in the legacy case now that's a BC
> break. One might argue that it should always have given a notice, but it
> didn't, so it's a change, and a BC break. Pick your poison.
>
> John Crenshaw
> Priacta, Inc.
>

--20cf3056390170aba504ba2ad4cb--