Re: Bug #13587 Updated: Recurence makes crash

On 7 Oct 2001 jeroen@php.net wrote: > Derick wrote: > > Indeed, if we can make PHP not to crash, we'll certainly do so. But in this case it > > is NOT possible as I explained before. > > You wrote before: > > > There is no clean way to catch this. PHP does not support infinite recursion, as no > > language does. > > The performance hit is too big if this kind of checking was build in, and even then > > it's not very easy to do in a smart way. > > That's a reason why PHP cannot check for this at compile time. But PHP > can of course check at runtime wether there are allocation problems. A > "Error: out of memory " would be apropriate, or a stack error. (don't > know where exactly the segfault is being caused by, by the hashtable > allocation attempt, or because that hash table allocation gets a pointer > to a location outside the execution stack or something alike, in either > case, a error would be appropriate and possible, very likely without > noticable performance hit) Read the archives before responding with this kind of stuff. It WILL give a big performance it. Oh, you wrote once: > (and I *definitely* also need some positive reactions otherwise you > probablywon't see any more patches from me (some people won't care > maybe, but that's their problem)) I suggest you do exactly that now. Derick