Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:34372
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.184 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=uKksfQHhLvtf053V3RUbRxUuwd+XkoJ5kU3VnxBD3K7N6SJ/1n6Lq6mJlbkfL1l/3SivFLPJ0iUdUftZfMsKHpCZfZvYUW5o3I3ytzg//ZYm7V66sVP/NUTTl+evE6j7r0MRJ0cS2ZjoNLG6OuAE0hpGlxUxs783I+ORQr+meyA=
Message-ID: <fe05d1540801031546o7b8c9720ifc0b24f9beab3d2e@mail.gmail.com>
Date: Fri, 4 Jan 2008 00:46:42 +0100
To: "Stanislav Malyshev" <stas@zend.com>
Cc: "=?ISO-8859-2?Q?Pawe=B3_Stradomski?=" <pstradomski@gmail.com>, 
	internals@lists.php.net
In-Reply-To: <477D6E68.5090501@zend.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <200801031903.01980.tomi@cumulo.fi>
	 <cd5680a20801031412p387103d5k694eed0f2978eeda@mail.gmail.com>
	 <477D66B4.2000107@zend.com> <200801040008.43944.pstradomski@gmail.com>
	 <477D6E68.5090501@zend.com>
Subject: Re: [PHP-DEV] RE: Optional scalar type hinting
From: pierre.php@gmail.com (Pierre)

On Jan 4, 2008 12:23 AM, Stanislav Malyshev <stas@zend.com> wrote:
> > This code is just a good argument *FOR* type hints. When foo is:
> > function foo(int $bar) {...}
> > and you want the code to die if $bar is not integer, then foo($bar) would be
>
> Why would you want it? I wouldn't want my code to die, I would want it
> to work.
>
> > you have either an int or string representing an integer in $bar, then
> > foo((integer)$bar) would work just well.
>
> And then how exactly strict typing helps you? You can not control at
> development time if everybody uses (integer) or not, since being
> interpreted PHP has no static type checking. So only option to find it
> out is to leave a minefield behind hoping that testers and not actual
> users would be ones who make it blow up. What if testers fail to find it?

Check google for all fatal errors we introduced about OO strictness
(or getter/setter) and you will see what does that mean to be unclear
about how strict one should be.

I'm not arguing to force strictness but I would love to have it, on a
per class basis for example (</dream>).

--
Pierre
http://blog.thepimp.net | http://www.libgd.org