Re: cvs: php4 /ext/standard Makefile.in basic_functions.c basic_functions.h url_scanner_ex.c url_scanner_ex.h url_scanner_ex.re
| From: | Zeev Suraski | Date: | Tue, 19 Sep 2000 17:55:03 +0000 |
| Subject: | Re: cvs: php4 /ext/standard Makefile.in basic_functions.c basic_functions.h url_scanner_ex.c url_scanner_ex.h url_scanner_ex.re | ||
| References: | 1 | Groups: | php.cvs |
| Request: | Send a blank email to php-cvs+get-1793@lists.php.net to get a copy of this message | ||
It currently breaks compilation under Windows; VC doesn't seem to particularly like that nextiter label. Is there any reason for using this 'goto nextiter', instead of using a plain 'continue'?
Zeev
At 20:42 19-09-00, Sascha Schumann wrote:
On Tue, 19 Sep 2000, Andi Gutmans wrote: At 17:32 19/09/00 +0000, Sascha Schumann wrote:-- Zeev Suraski <zeev@zend.com> http://www.zend.com/Is it possible to use emalloc()/efree() in your code or is this code which might be executed before the memory manager is initialized?sas Tue Sep 19 10:32:28 2000 EDTAdded files:/php4/ext/standard url_scanner_ex.c url_scanner_ex.h url_scanner_ex.reModified files:/php4/ext/standard basic_functions.c basic_functions.h Makefile.inLog: Add new URL scanner. This version is up to 20% faster. It will be enabled by default once I'm sure that it works in every case. To enable it, apply s/url_adapt_ext/url_adapt_ext_ex/ to session.cIt is still experimental code, and not meant to be judged by our usual code guidelines (i.e. a cleanup will follow). Or do you mean that we gain the 20% speedup by not using the memory manager? :-)- Sascha-- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, e-mail: php-cvs-unsubscribe@lists.php.net For additional commands, e-mail: php-cvs-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net