Hello Derick, Thursday, April 15, 2004, 10:07:01 PM, you wrote:
> On Thu, 15 Apr 2004, Jason Garber wrote: >> I see. I was basing the spec on the functionality of isset() which does >> not (obviously) throw an E_NOTICE when you pass an undefined variable to >> it. However, do you see any reason that this would not reliably work? > I wrote this (I underlined the relevant parts for you): >> >You'll need something more clever, because >> >an undefined key 'CUST_ID' in $_POST['CUST_ID'] will strill throw a > =============================================== >> >warning, even if you pass it to a language construct. Changing that >> >behavior is not trivial. Not really hard, we have several modes ofr accessing values. Some of them allow error free access. Furthermore you can implement it in the following way: $var = $val ?: $else; $var = if (isset($val)) $val else $else; in contrast to $var = if ($val) $val else $else; Notice that the former implementation does not need any change in access methods. It simply uses a different access for the test or better said it creates a different test. Best regards, Marcus mailto:[EMAIL PROTECTED] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
