Hi!
> would tell you that accessing an uninitialized variable triggers an
> error. You can argue that a 'notice' is not an error but, in practice,
> everybody considers it this way. Nobody will tell you : 'Oh, that's just
> a notice, just disable E_NOTICE in your php.ini'.
In fact, that's exactly what notice is meant for - something that can be
easily ignored. Otherwise, there's no different between notice and warning.
> element exists will send you to hell." won't change anything. People
> currently writing 'isset($foo['bar'])' won't change it for
> 'array_key_exists('bar',$foo)'. Just because it is longer, less
> readable, and you need to remember argument order (which is quite
> counter-intuitive).
If you insist on using wrong tool for the job, despite right tool being
available right next to you, then complaining about tool being wrong and
needing to change is not the right way to go.
--
Stas Malyshev
smalys...@gmail.com
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
