On Tue, Sep 4, 2012 at 9:43 AM, Ferenc Kovacs <tyr...@gmail.com> wrote:
> never heard of that one before.
>
> for example, running
> <?php
> for($i=0;$i<100;$i++){
> $foo="foo_".$i;
> ${$foo}->bar = 123;
> }
> echo "done";
>
> gives me 100 E_STRICT, but still executes just fine and prints "done" at
> the end.
> the only explanation that I can think of is that you have a custom error
> handler somewhere in your code, which somehow does something unexpected
> (exits the script execution or does something like an infinite recursion
> which segfaults/OOMs your application.
> if you still think that it isn't the case, then please open an issue on
> bugs.php.net with a reproduce script, as this would be clearly a bug.
I think Ferenc is correct in that this sounds like there's a custom
error handler somewhere. If the custom error handler collects error
info and then throws an exception (as has been detailed in various
blog posts as one manner of unifying the errors), this would cause the
trouble you're seeing.
Adam
--
Nephtali: A simple, flexible, fast, and security-focused PHP framework
http://nephtaliproject.com
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
