On 18/09/15 21:32, Rowan Collins wrote: > It would not be a replacement for is_null, nor for isset(), but a way of > writing a completely new type of code, which examined not a variable's value, > but its state within the Engine.
Rowan ... why is using is_null() and isset() after using array_key_exists() to identify the variable exists any different to wanting to use them after having used extract() on the same array? I get that you would prefer to convince users to use the pre-extract variables, but then why would you need extract? If you have extract, then checking that an extracted variable exists and if it is set or not are simply natural mirrors of the same function on the array? I don't see any 'completely new type of code' ... only a different frame in which the variables are held. -- 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
