Re: *crash* on try to find out how many nestinglevelsare allowed

ML>> I don't think the checks should be made against the current ML>> process CPU stack pointer address but rather have a ML>> configuration option that tells how many nested calls a function ML>> is allowed to make to itself directly on indirectly. When the ML>> number of calls is exceeded the script simply exits with a ML>> runtime error saying something like "the limit of recursive ML>> calls to function xyz() was exceeded". This is possible, but Zeev & Andi don't like this idea. The argument is that this limit is completely arbitrary, i.e. 2 calls to one function may eat more stack than 100 calls to other. I.e., you won't be protected anyway, for every large enough limit there will be a function that will crash under this limit. -- Stanislav Malyshev stas@zend.com +972-3-6139665