Re: About restricting the recursive implicit calls
Am 25.2.2013 um 19:08 schrieb Stas Malyshev <[email protected]>:
> Hi!
>
>>
>> p.s.: There is no reason why not to fix this in this way, I think,
>
> There actually is. First, any option modifying engine behavior creates a
> compatibility problem, since now the code that needs to work with it has
> to check and be tested for yet another variable. Second, why does it
> concentrate on magics? You can get stack overflow with any functions.
>
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
> (408)454-6900 ext. 227
It doesn't break if the limit is not set too low. It is like I now is, only without the
segmentation faults.
No, normal functions don't crash as - not 100% sure if I'm right - the Zend Engine
erealloc's (under control of the MM (and the memory limit)) the previous function
context and then returns; after the execution of the function the stack is restored:
a stack is only emulated and cannot cause crashes (the real c stack doesn't grow).
I concentrate only on implicit function calls as they are the only problem.
Bob
Thread (18 messages)