ID: 40610
User updated by: Webbed dot Pete at gmail dot com
Reported By: Webbed dot Pete at gmail dot com
Status: Open
Bug Type: Documentation problem
Operating System: Windows, Linux
PHP Version: 5.2.1
Assigned To: colder
New Comment:
If we require a single function, to *fully* emulate 'isset with
default' (with only two parameters), [EMAIL PROTECTED] is correct.
A compromise is currently required involving separate functions or at
least separate parameters that isolate potential array keys or object
property names.
The above emulations are effective userland emulations.
Further emulations are also helpful, such as emulation of '(isset AND
true) with default', which was noted in an earlier comment. This too
can be emulated through a set of functions.
It gets messy to do these workarounds, but the resulting application
code is much cleaner.
Instead of coding
$x = (isset($var) && $var) ? $var : $default;
$y = (isset($pref['key']) && $pref['key']) ? $pref['key'] : $default;
one can code
$x = varsettrue($var, $default);
$y = arrsettrue($pref,'key',$default);
by creating function varsettrue() as noted above, and now
function arrsettrue($arr,$key,$default='') {
if ( isset($arr) && is_array($arr) && array_key_exists($key,$arr) &&
isset($arr[$key]) && $arr[$key] ) return $arr[$key];
return $default;
}
The 'mess' is encapsulated in a set of userland functions. This frees
coders to write well-protected code that never generates notices.
Perhaps someday there can be built-in functions that accomplish all
this, but for now at least we know there are effective (if slow/messy)
workarounds. I now believe a single userland function may be possible;
will think on that.
Previous Comments:
------------------------------------------------------------------------
[2007-02-24 09:16:27] [EMAIL PROTECTED]
function foo(&$a) {}
foo($a); // will "create" $a
$b = new stdclass;
foo($b->c); // will "create" the public property "c"
$d = array();
foo($d['index']); // Will "create" the array index
In each case, it will be assigned to null. Calling isset will return
false because isset() returns false on variables assigned to NULL.
However, there are other functions like array_key_exist() or
property_exist() that are able to detect the NULL value.
Conclusion: there is simply no solution to effectively emulate the
isset() construct with default value using an user land function.
------------------------------------------------------------------------
[2007-02-24 03:20:18] Webbed dot Pete at gmail dot com
Typo on function arrset(). Instead of
... return $val;
it should be
... return $arr[$key];
------------------------------------------------------------------------
[2007-02-24 00:38:43] Webbed dot Pete at gmail dot com
<<<When you pass a non-existent variable by reference of course it HAS
to be created, or what do you think should be referenced?>>>
Funny thing is, passing a reference to a non-existent normal variable
works fine. Only array elements require something to be created.
If we accept this as a requirement, I believe we arrive at the
following set of conclusions:
What we're declarng here is that
a) isset() is not identical to "is created".
b) A php app has no way to discover if a variable is created.
c) Array elements must be treated distinctly from other variables
whenever the number of created keys is important.
d) For array elements, key references must be carried separately from
value references.
Thus, to accomplish the equivalent of "isset() with default," without
causing side effects, can still be accomplished with some pain.
It requires separate functions for variables, constants and array
elements. I believe the following patterns would be correct:
function varset(&$val,$default='') {
if (isset($val)) return $val;
return $default;
}
function defset($str,$default='') {
if (defined($str)) return constant($str);
return $default;
}
function arrset(&$arr,$key,$default='') {
if ( isset($arr) && is_array($arr) && array_key_exists($key,$arr) &&
isset($arr[$key]) ) return $val;
return $default;
}
Corrections welcome.
Thanks!
------------------------------------------------------------------------
[2007-02-23 23:38:31] [EMAIL PROTECTED]
Reclassified a docu problem.
When you pass a non-existent variable by reference of course it HAS to
be created, or what do you think should be referenced?
------------------------------------------------------------------------
[2007-02-23 22:47:54] Webbed dot Pete at gmail dot com
I have double and triple checked the documentation...
http://us3.php.net/manual/en/language.references.whatdo.php
...tells us that
<<<PHP references allow you to make two variables to refer to the same
content. Meaning, when you do:
<?php
$a =& $b;
?>
it means that $a and $b point to the same content. Note: $a and $b are
completely equal here, that's not $a is pointing to $b or vice versa,
that's $a and $b pointing to the same place.>>>
This works as far as it goes. What's left unsaid is that if $b is a
missing array key, the unset key will be created and the $b array will
grow.
Neither 'array' nor 'references' documentation specify this behavior.
They don't say whether or not array elements are created willy-nilly
when an array reference exists.
I find nothing in the reference manual that either specifies nor
suggests this behavior is intentional. I do find several user comments
about this bug. It's just never been reported as a bug before.
The impact is that we cannot trust the keys of an array.
If this is declared as missing documentation, we will have to live with
the bug.
I'd prefer to see it eventually fixed; php will be better for it.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/40610
--
Edit this bug report at http://bugs.php.net/?id=40610&edit=1
