On 16.06.2008, at 23:02, Stanislav Malyshev wrote:
So you just ignored the "special cases" part. Yes, if you have special
case where you interface with very brain-dead strictly typed system
that
absolutely can't understand that '1' and 1 is the same - then you
need to _convert_. So how failing when you get '1' instead of 1
helps you? You'd need _conversion_, not _failure_ - and if you write
strictly-typed API, you'd move the conversion responsibility to the
user, instead of having it where it belongs - in the API. That's
*exactly* why I see strict typing in PHP so dangerous - it promotes
lazyness and sloppiness in API writing, and those APIs will be a
nightmare to use, since they would bomb out on slightest
disagreement about internal engine types, which the API user
shouldn't care about at all. What happened with "be liberal at what
you accept"?
In strict compiled languages, the compiler and IDE will guide you
through this, in PHP you'd just have it explode in your face in
production. How this is good for anybody?
amen.
regards,
Lukas Kahwe Smith
[EMAIL PROTECTED]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
