That's the way to do it. If you have an idea, such as this, write it up, and
let's discuss. If we don't, we end up talking about things (like scalar type
hinting) that has been beaten to death on more than 100 occasions (sarcasm, but
not really...). We can then have a reference to point to showing that the
discussion is dead. After 6 months, feel free to bring it up again.
On Dec 22, 2011, at 2:52 PM, Christian Kaps wrote:
> Hi internals,
>
> someone in the "Return Type Hinting for Methods RFC" thread had the idea of a
> "numeric" type hint. I will capture this idea and propose a "scalar" type
> hint. I understand the problem of the current discussion about scalar type
> hints(int, float, string, double, ...). But there should be a possibility to
> define a "scalar" type hint to restrict arguments to scalar types.
>
> function setName(scalar $name) {}
>
> class Foo {
> public function __toString() {}
> }
>
> setName(1) // pass
> setName(true) //pass
> setName('Christian') // pass
> setName(new Foo) // pass
> setName(array()) //fail
> setName(new stdClass) //fail
>
> Why this isn't possible?
>
> Christian
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
