Jochem Maas wrote:
[snip]
my tests with
APC 3.0.10
show that despite the best efforts of mr. Lerdorf et al it is still
segfaults
intermittently when using [lots of?] objects (of varying complexity)
that use
__get()/__set()/__call()/etc - the last 24 hours lead me to suspect that
not APC
but th
I suggest that you quit your bitching and start filing some solid bug
reports instead.
http://bugs.php.net
--Wez.
On 4/1/06, Jochem Maas <[EMAIL PROTECTED]> wrote:
> Its still trivial to make php segfault when using __get()/__set() - I really
> don't care what I do with php, a segfault should nev
Matthew C. Kavanagh wrote:
Write your __set to not allow arrays to be set, and make arrays within
your object private or objects with __set in their own right.
You could in fact create a "CustomArray" or something and allow
CustomArrays to be __set'd in your object, then control their contents
Write your __set to not allow arrays to be set, and make arrays within
your object private or objects with __set in their own right.
You could in fact create a "CustomArray" or something and allow
CustomArrays to be __set'd in your object, then control their contents
with CustomArray->__set().
Unknown W. Brackets wrote:
The __set() method is called when a property of a class is set, __get()
when a property is retrieved.
An array is simple a way of listing things; the array itself is a piece
of data. When you set a key in that array, you are not setting the
I know these things.
The __set() method is called when a property of a class is set, __get()
when a property is retrieved.
An array is simple a way of listing things; the array itself is a piece
of data. When you set a key in that array, you are not setting the
array. It may help to think of it like this:
$t =
