Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:9856
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Fri, 14 May 2004 20:25:58 +0200
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <196966242.20040514202558@marcus-boerger.de>
To: Hans Lellelid <hans@velum.net>
Cc: internals@lists.php.net
In-Reply-To: <52459.206.112.93.146.1084546424.spork@webmail.hozn.net>
References: <52459.206.112.93.146.1084546424.spork@webmail.hozn.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Type hints resolution?
From: helly@php.net (Marcus Boerger)

Hello Hans,

Friday, May 14, 2004, 4:53:44 PM, you wrote:

> Hi,

> I just wanted to find out what the final resolution was on the typehints 
> discussion for RC3.  I know that I (& others) will be sad to see typehints
>  disappear for optional parameters, but it seemed like there was a lot of 
> support for this from others on the list.

> I didn't get a clear sense of "majority" one way or another, but it 
> sounded like Andi said that for PHP5RC3 there would be no more typehints 
> + null allowed.

There was a majority on don't allow NULL by default (at least among
the engine developers). And as there was no good idea that could also
be implemented without sideeffects like creating problematic keywords
we decided to disallow NULL for typehints and care for it after 5.0
if enough people request it and somone has a good idea for the syntax.

> I just want to know if I should start stripping out typehints from 
> optional params in preparation for RC3.

For PHP 5.0 that si definitively the way to go.

regards
marcus