Re: isset
| From: | Jim Lucas | Date: | Mon, 16 Apr 2007 16:18:48 +0000 |
| Subject: | Re: isset | ||
| References: | 1 2 3 4 5 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-253018@lists.php.net to get a copy of this message | ||
Stut wrote:
tedd wrote:-- Enjoy, Jim Lucas Different eyes see different things. Different hearts beat on different strings. But there are times for you and me when all such things agree. - RushAt 4:08 PM +0100 4/16/07, Stut wrote:In the above example, if (isset($_GET['something']) && !empty($_GET['something'])) { is the same as... if (!empty($_GET['something'])) { So, in that particular line of code the isset is a pointless waste of cycles. -Stut these two lines are not the same infact, with the first, you will not get a E_NOTICE warning, but with the second you will.Jim Lucas wrote:I've been accuse of that too, but what's your solution?Richard Kurth wrote:The isset is a pointless waste of cycles. -StutWhat do you do when isset does not work? If I send data in a $_REQUEST['var'] like if (isset($_REQUEST['var'])) { } Put var has no data it still says it is set. Because $_REQUEST['var'] = "" and isset thinks "" is setI use this combination a lot: if ( isset($_GET['something']) && !empty($_GET['something']) ) {// do something here with $_GET['something']}