Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:48397
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 63.205.162.117 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 22 May 2010 14:46:32 -0700
Message-ID: <698DE66518E7CA45812BD18E807866CE0427ED12@us-ex1.zend.net>
In-Reply-To: <93EFAEF4-26F3-44A1-85ED-5E71E665B966@pooteeweet.org>
Thread-Topic: [PHP-DEV] Type hinting
Thread-Index: Acr571d+UILgGxmOThKV3FY/x2dsYwACMX+w
References: <7.0.1.0.2.20100522175819.0a601c68@zend.com> <AANLkTinbzzKJlnCvJvunbxyJK_sufCi4sDcfH008evtx@mail.gmail.com> <93EFAEF4-26F3-44A1-85ED-5E71E665B966@pooteeweet.org>
To: "Lukas Kahwe Smith" <mls@pooteeweet.org>,
	"Josh Davis" <phpwnd@gmail.com>
Cc: "Zeev Suraski" <zeev@zend.com>,
	<internals@lists.php.net>
Subject: RE: [PHP-DEV] Type hinting
From: andi@zend.com ("Andi Gutmans")

So which RFC should I be reviewing? Does this RFC reflect what Ilia's
patch does? I just want to be sure we are talking about the same thing
and can review and comment on it in detail. We've had many discussions
on this topic over the years and different people had different things
in mind so we need to make sure we have a good structured discussion
(and documented via RFC).

Andi

> -----Original Message-----
> From: Lukas Kahwe Smith [mailto:mls@pooteeweet.org]
> Sent: Saturday, May 22, 2010 1:39 PM
> To: Josh Davis
> Cc: Zeev Suraski; internals@lists.php.net
> Subject: Re: [PHP-DEV] Type hinting
>=20
>=20
> On 22.05.2010, at 18:30, Josh Davis wrote:
>=20
> > As you wrote, you worked on PHP's _type system_ which is dynamic,
> > really cool, juggles strings with ints and what not. However, the
> > topic here is the _type hinting system_. As far as I know, there's
no
> > "weak" type hinting; if a method signature hints for an array and is
> > given an integer, it throws a catchable fatal error. Therefore, as a
> > user, what I am familiar to is a strict _type hinting system_.
> > Anything else would feel inconsistent to me.
>=20
>=20
> can we please just stop calling a something a "type hinting" system,
which leads
> to a catchable fatal error when the type does not strictly match?
thats a very
> misleading euphemism. its simply strict typing, it has nothing to do
with hinting.
>=20
> anyway, yes there is a proposal for an actual hinting system as Zeev
has pointed
> out just a few mails early in the thread than yours:
> http://wiki.php.net/rfc/typecheckingstrictandweak
>=20
> regards,
> Lukas Kahwe Smith
> mls@pooteeweet.org
>=20
>=20
>=20
>=20
> --
> PHP Internals - PHP Runtime Development Mailing List To unsubscribe,
visit:
> http://www.php.net/unsub.php