Hey,
Coming into this a bit late (took me a while to read the gazillion emails on
the topic.
First of all, I agree that we can find some middle ground which should make
everyone happy.
I don't think that making interfaces have additional semantics is the way to
go though. I personally don't think
Zeev Suraski wrote:
It's my list actually, so I'm definitely +1 on that :)
Sorry, did not want to take away credit from you Zeev :)
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
At 10:49 04/08/2006, Lukas Smith wrote:
Derick Rethans wrote:
- Add a new flag to methods (at the implementation level) that
will allow to flag them as 'strict'
- In case such a strict method is improperly overridden - error
out (E_ERROR)
- In case a non-strict method is improperly overri
Hi all,
Since I've been looking at is_numeric_[string|unicode], I found a weird
thing it causes; probably doesn't make sense to users; bug? Look:
abs(-1e500) // float(INF)
abs('-1e500') // int(1) WRONG
abs('-1e100') // float(1.0E+100)
is_finite(1e500) // bool(false)
is_finite('1e500') // bool(t
