Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:34377
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain sambarrow.com from 205.234.132.11 cause and error)
To: Stanislav Malyshev <stas@zend.com>
Cc: internals@lists.php.net
In-Reply-To: <477D58ED.6030101@zend.com>
References: <200801031903.01980.tomi@cumulo.fi>
	 <1199380881.15292.11.camel@sbarrow-desktop>
	 <20080103172813.GQ7861@mint.phcomp.co.uk> <477D2B40.9010302@fischer.name>
	 <477D2CDB.3000005@zend.com>
	 <alpine.DEB.0.98.0801032022110.4763@kossu.ez.no>
	 <477D452A.9090906@zend.com> <1199392531.15292.64.camel@sbarrow-desktop>
	 <477D4ACF.3030006@zend.com> <1199395138.15292.72.camel@sbarrow-desktop>
	 <477D58ED.6030101@zend.com>
Content-Type: text/plain
Date: Thu, 03 Jan 2008 19:25:33 -0500
Message-ID: <1199406333.5889.2.camel@e-vectra>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RE: Optional scalar type hinting
From: sam@sambarrow.com (Sam Barrow)

The value is this:

With type hinting:

function a(string $mystring, num $mynum, object $myobject) {

}

Without type hinting:

function a($mystring, $mynum, $myobject) {
if (!is_string($mystring)) {
trigger_error('Parameter 1 of function a() must be a string.',
E_USER_WARNING) ;
}
if (!is_int($mynum) and !is_float($mynum)) {
trigger_error('Parameter 2 of function a() must be a number.',
E_USER_WARNING) ;
}
if (!is_object($myobject) {
trigger_error('Parameter 3 of function a() must be an object.',
E_USER_WARNING) ;
}
}

On Thu, 2008-01-03 at 13:51 -0800, Stanislav Malyshev wrote: 
> > There aren't two code models here at all. You can have a function
> > parameter, or you can have a type-enforced function parameter. PHP
> 
> So now to use such function you'd have to check your variables for 
> typing - otherwise your application blows up. And the type-checking 
> should be total - otherwise you miss some call to some function or some 
> code path bringing wrong value and your application blows up at runtime 
> - since static type checking is not available. Meaning, unless all of 
> your code is type-enforced, you'd have to write a wrapper around each 
> type-enforced function manually checking that wrong value didn't get in. 
>   But you can do the same checks now, so what is the added value?