Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:42164
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <F3.E8.21579.2CF4D394@pb1.pair.com>
To: internals@lists.php.net
Date: Mon, 08 Dec 2008 14:48:00 -0200
User-Agent: Thunderbird 2.0.0.18 (X11/20081105)
MIME-Version: 1.0
References: <B3.D4.15656.6A00D394@pb1.pair.com> <493D425C.6010104@zend.com> <938983775.20081208172740@marcus-boerger.de>
In-Reply-To: <938983775.20081208172740@marcus-boerger.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Problem with (namespaced) code extending ReflectionProperty
 - possible bug?
From: rodrigo.saboya@bolsademulher.com (Rodrigo Saboya)

> Which reminds me that we still have no way to do that in userland.
> In userland you cannot write:
>   function foo(Object $bla = NULL).
> The missing part is 'Object' as a type hint. I once long ago suggested
> using 'class' as in 'any class member'. But people felt it wouldn't be
> self explanatory enough. And unfortunately we cannot use 'Object' for
> obvious reasons. We simply cannot turn that into a reserved word not
> can we expect no one to have a class named Object already.
> 
> So my suggestion holds: Let's add type hint 'class' to allow hints for
> objects.
> 
> marcus
> 
>>> This is my test code:
>>>  ---- snip ----
>>> <?php
>>> class PropertyReflection extends ReflectionProperty {
>>>     public function getValue(stdclass $object) {}
>>> }
>>> ?>
> 
>> Use public function getValue($object = null) {} instead.
>> -- 
>> Stanislav Malyshev, Zend Software Architect
>> stas@zend.com   http://www.zend.com/
>> (408)253-8829   MSN: stas@zend.com
> 
> 
> 
> 
> Best regards,
>  Marcus
> 

I don't think having a Object class built in is such a big issue with 
namespaces around. Anyone using object type-hinting should have a clue.

--
Rodrigo Saboya