Re: Construct Request
| From: | Derick Rethans | Date: | Thu, 15 Apr 2004 20:07:01 +0000 |
| Subject: | Re: Construct Request | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-9221@lists.php.net to get a copy of this message | ||
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.
Derick