ID: 10666
User updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Old Status: Open
Status: Closed
Bug Type: PCRE related
Operating System: Linux
PHP Version: 4.0.5
New Comment:
Strangely, while the bug referenced in my update at [2001-05-04 13:55:39] was very
repeatable across several
ID: 10668
User Update by: [EMAIL PROTECTED]
Status: Analyzed
Bug Type: PCRE related
Description: preg_replace backquote failure
H'm... I'm confused. :-) To complicate things further, the e-mails display half as
many backslashes as the web page. :-) Since I'm not sure what you mean, I'll
exha
ID: 10666
User Update by: [EMAIL PROTECTED]
Status: Open
Bug Type: PCRE related
Description: preg_replace 'e' modifier
Also, as a merely informational aside, PHP's use of $1 is in this instance actually
incompatible with Perl. Perl, in a s///e expression, treats $n as a variable rather
than ex
ID: 10668
User Update by: [EMAIL PROTECTED]
Status: Analyzed
Bug Type: PCRE related
Description: preg_replace backquote failure
Oddly, I get the following error:
Warning: Unexpected character in input: '\' (ASCII=92) state=1 in
/home/groups/t/ta/tavi/htdocs/playground/test.php(4) : regexp c
ID: 10666
User Update by: [EMAIL PROTECTED]
Old-Status: Closed
Status: Open
Bug Type: PCRE related
Description: preg_replace 'e' modifier
Okay. Then I have a problem with how backslash escaping is inconsistently applied
when using \\1 and $1.
Specifically, consider the following:
functi
From: [EMAIL PROTECTED]
Operating system: Linux
PHP version: 4.0.5
PHP Bug Type: PCRE related
Bug description: preg_replace backquote failure
The following code succeeds on PHP 4.03 and PHP 4.04pl1, but fails on PHP 4.05:
$str = "abc'''def";
function f($s) { return
From: [EMAIL PROTECTED]
Operating system: Linux
PHP version: 4.0.5
PHP Bug Type: PCRE related
Bug description: preg_replace 'e' modifier
Formerly, preg_replace's "e" modifier inserted extraneous backslashes in
backreferences of "\\1" or '\\1' form.
Ostensibly, the $1 backr
