Re: Re: __set() / __get() : limitation and/or unintentional behavoiur?

From:	Wez Furlong	Date:	Sat, 01 Apr 2006 18:39:41 +0000
Subject:	Re: Re: __set() / __get() : limitation and/or unintentional behavoiur?
References:	1 2 3 4 5	Groups:	php.internals
Request:	Send a blank email to [email protected] to get a copy of this message

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 never occur, at worst I get
> a nice FATAL ERROR telling what an idiot I have been... 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 the engine itself is the 'bad guy' ...  unfortunately I don't have the C
> skills
> to test that theory.


   

Thread (7 messages)

• Jochem MaasSat, 01 Apr 2006 00:49:10 +0000
  • Unknown W. BracketsSat, 01 Apr 2006 07:05:56 +0000Re: __set() / __get() : limitation and/or unintentional behavoiur?
    • Jochem MaasSat, 01 Apr 2006 08:13:05 +0000Re: Re: __set() / __get() : limitation and/or unintentional behavoiur?
      • Matthew C. KavanaghSat, 01 Apr 2006 08:41:53 +0000
        • Jochem MaasSat, 01 Apr 2006 17:04:09 +0000
          • Wez FurlongSat, 01 Apr 2006 18:39:41 +0000
          • Jasper Bryant-GreeneSat, 01 Apr 2006 23:02:01 +0000