php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Request #51103 a warning should be displayed if there is a pcre error
Submitted: 2010-02-21 00:53 UTC Modified: 2017-08-29 14:08 UTC
Votes:4
Avg. Score:4.8 ± 0.4
Reproduced:4 of 4 (100.0%)
Same Version:2 (50.0%)
Same OS:3 (75.0%)
From: henrik dot gebauer at web dot de Assigned:
Status: Suspended Package: PCRE related
PHP Version: 5.2.12 OS: Irrelevant
Private report: No CVE-ID: None
View Developer Edit
 [2010-02-21 00:53 UTC] henrik dot gebauer at web dot de 
Description:
------------
PHP should display a warning if there is a PCRE error, that is if preg_last_error() != PREG_NO_ERROR.
This would make it easier to find bugs.

Patches

Pull Requests

Pull requests:

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2010-03-09 20:51 UTC] jani@php.net
-Package: Feature/Change Request +Package: PCRE related
 [2010-12-22 20:15 UTC] yehuda+php at ymkatz dot net 
Yes, I spent twenty minutes troubleshooting a script that ran fine on one machine 
but returned no results on another machine.
Eventually, I found that pcre.recursion_limit was set to 1, but with a warning 
that there was an error, I would have found it right way.
 [2016-07-20 23:36 UTC] cmb@php.net 
Related To: Bug #53685
 [2016-07-21 11:34 UTC] cmb@php.net 
Related To: Bug #49339
 [2017-08-29 13:54 UTC] cmb@php.net 
Related To: Bug #75133
 [2017-08-29 14:08 UTC] cmb@php.net
-Status: Open +Status: Suspended
 [2017-08-29 14:08 UTC] cmb@php.net 
Thank you for your interest in PHP and for submitting a feature
request. Please be aware that due to the magnitude of change this
request requires, it would be necessary to discuss it on PHP
Internals list (internals@lists.php.net) as an RFC. Please read
the guide about creating RFCs here:
<https://wiki.php.net/rfc/howto>. If you haven't had experience
with writing RFCs before, it is advised to seek guidance on the
Internals list (<http://php.net/mailing-lists.php>) and/or solicit
help from one of the experienced developers. 

Please do not consider this comment as a negative view on the
merits of your proposal – every proposal which requires changes of
certain magnitude, even the very successful and widely supported
ones, must be done through the RFC process. This helps make the
process predictable, transparent and accessible to all developers.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Sat Dec 21 15:01:29 2024 UTC