Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:48396
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 188.40.37.16 cause and error)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <AANLkTinbzzKJlnCvJvunbxyJK_sufCi4sDcfH008evtx@mail.gmail.com>
Date: Sat, 22 May 2010 22:39:09 +0200
Cc: Zeev Suraski <zeev@zend.com>,
 internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <93EFAEF4-26F3-44A1-85ED-5E71E665B966@pooteeweet.org>
References: <7.0.1.0.2.20100522175819.0a601c68@zend.com> <AANLkTinbzzKJlnCvJvunbxyJK_sufCi4sDcfH008evtx@mail.gmail.com>
To: Josh Davis <phpwnd@gmail.com>
Subject: Re: [PHP-DEV] Type hinting
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 22.05.2010, at 18:30, Josh Davis wrote:

> 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.


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.

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