# Type hints resolution?

- Thread: https://externals.io/message/9854
- Original archive: https://news-web.php.net/php.internals/9854
- Started by Hans Lellelid on 2004-05-14T14:53:44+00:00
- Messages: 2
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #9854 — Hans Lellelid — 2004-05-14T14:53:44+00:00

URL: https://externals.io/message/9854#9854

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.

I just want to know if I should start stripping out typehints from 
optional params in preparation for RC3.

Thanks,
Hans

---

## #9856 — Marcus Boerger — 2004-05-14T18:25:58+00:00

URL: https://externals.io/message/9854#9856 · In reply to: #9854

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