Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:4033 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 9599 invoked by uid 1007); 16 Aug 2003 22:39:25 -0000 Message-ID: <20030816223925.9598.qmail@pb1.pair.com> To: internals@lists.php.net References: <1060813541.901.336.camel@ali> Date: Sun, 17 Aug 2003 00:39:38 +0200 Lines: 17 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Posted-By: 80.126.21.70 Subject: Re: variable_exists() patch From: abies@php.net ("Ard Biesheuvel") > A few weeks ago I submitted a patch in the bug db for a > variable_exists() construct, which parallels the function_exists() > one but for variables. In short, it returns TRUE if a variable > exists, regardless of its value. In other words, it's an isset() > which doesn't care if the variable's value is NULL. Nice work. However, if your application relies on unset variables to be distinguishable from variables that are null, you should probably fix your application first, and then consider 'fixing' the language. Ard