Re: what happened to that new isset() like language
| From: | Sean Coates | Date: | Sun, 30 Oct 2005 03:32:47 +0000 |
| Subject: | Re: what happened to that new isset() like language | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-19842@lists.php.net to get a copy of this message | ||
Bob Silva wrote:
> It should be a function and not a language construct IMHO. Either ifsetor or
> overload the isset statement (which may not be possible within the engine).
It _has_ to be a language construct, and not a function (otherwise, we'd
get a notice when first using the variable).
It could, however, be a language construct that LOOKS like a function.
This is how isset() and empty() work.
Also, if this was possible as a function, it could be solved in
user-space, and we wouldn't be having this conversation.
(not that I claim to be an internals expert.. if I'm wrong, feel free to
correct me)
To pitch in my 0.02 CAD: this functionality is valuable to me, but I
don't care what we name it, or how it works. I could also live without
it: isset() + ternary + redundant typing.
S