Stut wrote:
Jim Lucas wrote:
Stut wrote:
tedd wrote:
At 4:08 PM +0100 4/16/07, Stut wrote:
Jim Lucas wrote:
Richard Kurth wrote:
What 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 set
I use this combination a lot:
if ( isset($_GET['something']) && !empty($_GET['something']) ) {
// do something here with $_GET['something']
}
The isset is a pointless waste of cycles.
-Stut
I've been accuse of that too, but what's your solution?
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.
No you won't. The empty function does not raise a notice if its argument
does not exist.
From http://php.net/empty...
"empty() is the opposite of (boolean) var, except that no warning is
generated when the variable is not set."
-Stut
Interesting, have not looked at the empty() man page in a long time.
It use to through E_NOTICE warnings, as far back as I can remember back in 1999, and 2000
I wonder if they changed it, or the person that told me to do it that way was mistaken.
my mistake.
But, as you can tell, others were under the same impression as I.
--
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.
- Rush
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
