Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:34416
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.186 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=L3zeZ4DzoU5F1ZmAz299dZK+R7tV/5TY3VJr2WI1wDbc7yAtwDmusr7v7/+8GZAmvNxuzmE18bgd7F/H+cueiKJXUqKUzyV6uuSwKupNcDvVaQuupuxqgNhh6Tt0c8weArNDqS7aDFxsn+qaThximATKTOMltQ90d99/jjhpfu4=
Message-ID: <fe05d1540801040909p243f1099m511178ea96f149aa@mail.gmail.com>
Date: Fri, 4 Jan 2008 18:09:02 +0100
To: "Sam Barrow" <sam@sambarrow.com>
Cc: "Gregory Beaver" <greg@chiaraquartet.net>, 
	"Alain Williams" <addw@phcomp.co.uk>, 
	"internals Mailing List" <internals@lists.php.net>
In-Reply-To: <1199466070.15292.140.camel@sbarrow-desktop>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <477DB7BF.10201@chiaraquartet.net>
	 <20080104105558.GC7861@mint.phcomp.co.uk>
	 <477E5649.2080104@chiaraquartet.net>
	 <fe05d1540801040853q1b053a04gf4ad028e19a84e4d@mail.gmail.com>
	 <fe05d1540801040853w20c9f054i2e697764761431c9@mail.gmail.com>
	 <1199466070.15292.140.camel@sbarrow-desktop>
Subject: Re: [PHP-DEV] type hinting
From: pierre.php@gmail.com (Pierre)

On Jan 4, 2008 6:01 PM, Sam Barrow <sam@sambarrow.com> wrote:
>
> On Fri, 2008-01-04 at 17:53 +0100, Pierre wrote:
> > On Jan 4, 2008 5:53 PM, Pierre <pierre.php@gmail.com> wrote:
> > > On Jan 4, 2008 4:52 PM, Gregory Beaver <greg@chiaraquartet.net> wrote:
> > >
> > > > But I *don't* want my functions to take an argument of arbitrary type -
> > > > it is in fact you who are missing the point.  A type hint is a poor
> > > > solution to a real problem that is much more easily solved via simple
> > > > input validation and graceful error handling.  The current situation in
> > > > PHP provides a much more flexible solution to the same problem.
> > >
> > > Unlike our OO strictness (E_FATAL!!), nothing will prevent you to use
> >
> > Read: othing will prevent you to >do not< use it :)
> >
>
> So you're saying if you don't like it just don't use it?

Yes, that's the meaning of "optional" I suppose :)

My idea about it (I did not test the patch, so correct me if I
misunderstood the proposal) was to leave the default as it is now:

function($a) > what Greg likes to always use ;)
function(mixed $a) > little syntax sugar, same as the previous one
function(int $a)
etc.

-- 
Pierre
http://blog.thepimp.net | http://www.libgd.org