I just read about unset variable through php manual.
The php manual says "unset() destroys the specified variables"
This def seems perfect until I came across static variable... "If a static variable is unset() inside of a function, unset() destroys the variable only in the context of the rest of a function. Following calls will restore the previous value of a variable. "
This definition doesn't seems a good one for me, at least, since "destroy the variable" implies that the variable is no longer associated with that memory location.
Does anyone else think a better definition would be "unset() makes the variable out of current scope"? I mean, rather than pointing towards lifetime, it's better to use word scope here?
unset(self::$somethingstatic); will raise an Fatal error, because the variable is static (always there, can't be unset).
the documentation refers specifically to static variables defined inside a function, consider:
because $shell is a static variable, it's always there (static) so any other time you mention $shell that is simply a reference - when you unset it, you are unsetting the reference (think unlink'ing a symlink) - the static variable is however still there (that's what static means).
thus if you call the above function t(1) will echo 24, t(2) will echo nothing, and t(3) will (rightly) echo 23 :)
help any?
Inside a function, variable names referencing static variables are just that.. references. In effect, unset destroys the reference.
Well, what
unset()
does is clears up the memory associated with a variable name.In the case of static variables, however, what you can visualize as happening is separating the static variable from the scope of the function, and every time you call the function, you automatically get a copy of that variable.
So, what this means is if you
unset
a static variable, you are only actuallyunset
ting that copy, so when the function is called again, it "receives" a fresh copy.If am not wrong, the point is to unset a static variable. For different reasons this might be useful, in addition this would free some memory. For example:
While we cannot achive this exactly as is, in some cases could be enough to do this:
This would free some memory (I guess) and would allow us to destroy an object we don't want anymore (I hope I am not out off topic).
Let's consider the function:
The function compiles to:
A variable actually exists outside each function call to
foo()
and, on each call, it's fetched and a reference to it is assigned to$bar
. In fact, it's very similar to this:When you call
unset()
, you're only destroying the reference you created, not the underlying value.I didn't confirm, but what I'd guess that happens is this:
foo()
is called, the symbol$bar
is associated with this zval, its reference count is increased to 2 and the reference flag is set.unset
is called, the zval has its reference count decreased to 1, the reference flag is probably cleared and the symbol$bar
is removed.See reference count basics.