Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:9626
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Reply-To: john@coggeshall.org
To: Marcus Boerger <helly@php.net>
Cc: PHP Internals <internals@lists.php.net>
In-Reply-To: <243202120.20040501220932@marcus-boerger.de>
References: <243202120.20040501220932@marcus-boerger.de>
Content-Type: text/plain
Message-ID: <1083446852.2709.24.camel@coogle.localdomain>
Mime-Version: 1.0
Date: Sat, 01 May 2004 17:27:32 -0400
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Type hints
From: john@coggeshall.org (John Coggeshall)

I agree with the idea that it would be nice to force an instance of a
particular class, etc. to be passed. However, if we are going to
introduce another keyword anyway why not keep BC intact by by
introducing the 'force' keyword:

function myfunction(force ClassName $param, NextClass $another) {

}

Where 'force' would prevent $param from being passed as anything but an
acceptable ClassName. Alternatively, for the sake of parsing you could
do:

function myfunction(Classname forced $foo) {

}

I remember discussing 'array' as a typehint (big +1 there), but I don't
see anything gained from such a type-hint. When exactly would you use it
(that you couldn't use the existing type hinting).. I guess the obvious
answer is when you don't know the type of class being passed, but if you
don't know that how do you plan on actually using the parameter at all? 

John

-- 
-=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=-
John Coggeshall                   http://www.coggeshall.org/
The PHP Developer's Handbook    http://www.php-handbook.com/
-=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=--=~=-