Re: *crash* on try to find out how manynestinglevelsare allowed

From: Date: Sun, 09 Jul 2000 21:05:10 +0000
Subject: Re: *crash* on try to find out how manynestinglevelsare allowed
References: 1  Groups: php.dev 
Request: Send a blank email to php-dev+get-23962@lists.php.net to get a copy of this message
Hello Zeev, On 09-Jul-00 18:58:51, you wrote: >The problem is that this arbitrary limit is meaningless; Calling a certain >PHP function may exhaust your stack, whereas calling another one even a >thousand times recursively may not exhaust it. It depends on the function. It's pretty much like that execution time limit option. Some scripts may take much more time to execute but it's an option that you can change even at run time. It was thought that 30 seconds was a reasonable time limit for most scripts. You don't have to enable recursion limit by default, but a 100 would be a reasoanable limit for most scripts. Other scripts may change the limit or simply disable the checks, just like for the time limit option. The point here is not to figure a reasonable limit, but rather to provide some useful information to the programmer when stack exhaustion leads PHP to crash. If you can make the limit be figured from the actual remaining CPU stack space, better, but at least with nested call hard limit you can provide a portable solution that programmers may enable or not. Regards, Manuel Lemos Web Programming Components using PHP Classes. Look at: http://phpclasses.UpperDesign.com/?user=mlemos@acm.org -- E-mail: mlemos@acm.org URL: http://www.mlemos.e-na.net/ PGP key: http://www.mlemos.e-na.net/ManuelLemos.pgp --

« previous php.dev (#23962) next »