ID: 16590
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Open
+Status: Closed
Bug Type: Documentation problem
Operating System: Linux
PHP Version: 4.1.2
New Comment:
This bug has been fixed in CVS. You can grab a snapshot of the
CVS version at http://snaps.php.net/. In case this was a documentation
problem, the fix will show up soon at http://www.php.net/manual/.
In case this was a PHP.net website problem, the change will show
up on the PHP.net site and on the mirror sites.
Thank you for the report, and for helping us make PHP better.
Previous Comments:
[2002-04-13 16:27:41] [EMAIL PROTECTED]
pcre is binary safe with regards to the string being matched against,
but not the pattern. this is a limitation of the pcre library itself,
not just the php interface. you can specify the nul character using:
preg_match("/\\x00/", "foo\0bar")
reclassified as documentation problem.
[2002-04-13 15:59:36] [EMAIL PROTECTED]
The docs state that PCRE is binary safe. So this might be a bug after
all...
[2002-04-13 13:23:59] [EMAIL PROTECTED]
Actually, I'm not sure whether this problem can be solved as it is PCRE
and not a PHP specific (and it can't be solved without breaking
compatibilty with languages using 0 terminated strings such as C).
I'm thinking about making it a documentation problem. What do you guys
think?
-daniel
[2002-04-13 13:06:44] [EMAIL PROTECTED]
The PCRE has problems with strings containing 0x00. It stops reading as
if the strings were \0 terminated. This affects all preg_* functions.
Examples:
preg_match("/\x00/", "foo");
preg_match("/" . chr(0) . "/", "foo");
Raises the error "Warning: No ending delimiter '/' found"
--
Edit this bug report at http://bugs.php.net/?id=16590&edit=1
