ID: 46959 Updated by: [email protected] Reported By: ravitanra at gmail dot com Status: Closed Bug Type: PCRE related Operating System: Linux PHP Version: 5.2.8 New Comment:
ereg, fileinfo, filter, spl, zip and get_browser() are all using PCRE internally. Making it required is useful because it solves dependency issues when you have static and shared modules. It also helps web developers since they can rely on PCRE. Though I'm not sure what your problem is with it? Sure its a little extra memory but that's the only real runtime cost. Previous Comments: ------------------------------------------------------------------------ [2008-12-29 17:18:03] ravitanra at gmail dot com Thanks for the fix. Hopefully it will be available in 5.2.9 Btw, why not keep the options to disable in 5.3.0+ releases unless it has any serious negatives. ------------------------------------------------------------------------ [2008-12-29 15:27:28] [email protected] This bug has been fixed in CVS. Snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. Thank you for the report, and for helping us make PHP better. ------------------------------------------------------------------------ [2008-12-29 10:17:31] [email protected] It looks like it was forced enable by accident. Ilia merged some 5.3 changes into 5.2 and accidentally got the force enabled option too. http://cvs.php.net/viewvc.cgi/php-src/ext/pcre/config0.m4?r1=1.38.2.3.2.10&r2=1.38.2.3.2.11&pathrev=PHP_5_2 Confirming this now. With 5.3.0+ we have SPL, Reflection and PCRE all forced as enabled. ------------------------------------------------------------------------ [2008-12-29 05:31:26] ravitanra at gmail dot com What are such extensions are? a list will be useful. Are there any side effects of removing pcre? I removed pcre by removing from the makefile & disabling HAVE_BUNDLED_PCRE macro. It compiled and running fine but would be intereing to know side effects Unless there are strong reasons, IMO, there should be an option to remove it and by default those extensions can be bundled. ------------------------------------------------------------------------ [2008-12-29 01:52:29] [email protected] Should we not remove the option then? ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/46959 -- Edit this bug report at http://bugs.php.net/?id=46959&edit=1
