On 19/09/15 00:20, Stanislav Malyshev wrote:
>> 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.PLEASE ... There is no debate over isset($foo['bar']) ... no problem with that at all! The problem is with isset($bar) where $bar is a simple variable perhaps expected or not as a result of using expand() but that is not the only path. I first hit this particular one becuase of notices appearing on what had been clean code. And NO switching off those notices is not the right fix, but it is the ONLY fix at the moment. So IS there another fix for is_null($bar) not throwing a notice if it has not been created in my example for the current template. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
