Daniel Convissor escribió:
Because that's what the manual says it should do.
Right, however I disagree with the fact it is a warning, it should be a
fatal error IMHO.
--
"A computer is like an Old Testament god, with a lot of rules and no
mercy. "
Cristian Rodríguez R.
Platform/OpenSUS
On Tue, Jul 01, 2008 at 05:55:49PM -0500, Ralph Schindler wrote:
> In PHP 5.3 snaps, it appears that magic methods __isset, __unset, __get,
> __set must have a public visibility or the engine will trigger a
> warning. Why is this? It works as expected in 5.x branches.
Because that's what the
Hello there,
I don't have enough time to write more detailed example, but I still want to
write my opinion.
I totally agree with Stanislav, because for me magic functions should be
used in last leaf of some class extend tree. They are some kind of feature
when you are producing the non-framework,
Hi!
In PHP 5.3 snaps, it appears that magic methods __isset, __unset, __get,
__set must have a public visibility or the engine will trigger a
warning. Why is this? It works as expected in 5.x branches.
I think it doesn't actually work as expected - because as far as I can
see, visibility i
Well, I guess I blinked and missed the internal@ thread on this topic :)
Seriously though, if there was a thread on this subject, please point me
in the right direction.
In PHP 5.3 snaps, it appears that magic methods __isset, __unset, __get,
__set must have a public visibility or the engine
