#47032 [Opn->Csd]: contradictions in isset docs

From: Date: Fri, 08 May 2009 19:06:30 +0000
Subject: #47032 [Opn->Csd]: contradictions in isset docs
References: 1  Groups: php.doc.bugs 
Request: Send a blank email to doc-bugs+get-2222@lists.php.net to get a copy of this message
ID: 47032 Updated by: danbrown@php.net Reported By: charles at chaoslizard dot org -Status: Open +Status: Closed Bug Type: Documentation problem PHP Version: Irrelevant New Comment: This bug has been fixed in the documentation's XML sources. Since the online and downloadable versions of the documentation need some time to get updated, we would like to ask you to be a bit patient. Thank you for the report, and for helping us make our documentation better. Previous Comments: ------------------------------------------------------------------------ [2009-01-07 23:55:28] charles at chaoslizard dot org Description: ------------ The docs for isset (http://php.net/isset) are misleading and contradictory. "Determine whether a variable is set"--that part would make sense alone. Skip a sentence and it says "isset() will return FALSE if testing a variable that has been set to NULL". If this sentence is true, the first sentence is false, misleading, and incomplete: it should read something like "Determine whether a variable is set to anything except NULL". To put it another way, the problem is that it first claims to unconditionally check for a variable that "is set", but then claims to return FALSE for a variable that "has been set" to a particular value. The problem could hinge on the nebulous definition of "set". If this is the case, I'd suggest not using the phrase "has been set" in the later sentence. It looks like bug #19080 may have prompted the documentation to read like it does now. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=47032&edit=1

« previous php.doc.bugs (#2222) next »