Re: PHP 4.0 Bug #2004: recursive call limitation

From: Date: Wed, 11 Aug 1999 09:48:07 +0000
Subject: Re: PHP 4.0 Bug #2004: recursive call limitation
References: 1 2 3 4 5  Groups: php.dev 
Request: Send a blank email to php-dev+get-9741@lists.php.net to get a copy of this message
Morning, > you try the emalloc(), efree() solution I suggested and let us know if it's > good enough for what you need. It doesn't change anything ... I've done that : /*#if (HAVE_ALLOCA || (defined (__GNUC__) && __GNUC__ >= 2)) && !(defined(ZTS) && (WINNT|WIN32)) # define do_alloca(p) alloca(p) # define free_alloca(p) #else*/ # define do_alloca(p) emalloc(p) # define free_alloca(p) efree(p) /*#endif*/ Is it what you were talking about !? > But if you have very heavy recursive > mathematical computations I really suggest you either go with Sascha's > suggestion of going iterative, or write a PHP C module that will support > your math stuff. If it's pretty much general purpose it'll go into the PHP > 4.0 tree. Here, there's somebody who's writing a search engine which is using recursive to jump from link to link (I mean ... if there's a link on a page then it goes to the page and if there's a link on a page etc etc) ... we will see if there's no problem. Anyway, can we have a "stack overflow" message like there was in php3 !? And ... I dunno if it's php or not, but when I'm stopping an infinite loop with the button stop of netscape ... the page stop loading but then apache still get very busy and took 96% of my CPU. I'm not sure it's coming from php cause sometimes it's happen to me when I'm visiting other website !? gregori

« previous php.dev (#9741) next »