I can very much understand the drive behind this whish. The patch consists of two parts. The first part is generating an error message in case no constructor is available. He uses E_NOTICE while i would prefer E_STRICT
Both E_NOTICE or E_STRICT are fine with me. Whatever people feel is more appropriate.
there. Then the second part is a bit strange. It looks like if we could ignore other functions/methods with the patch.that doesn't look right.
No, it avoids the segfault caused by the previous patch because in that case EX(function_state).function never gets set.
I don't change anything for other function calls as function is always set (otherwise it would have caused a segfault w/o my patch anyway).
- Chris
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
