Bug #9156 Updated: stripslashes doesn't work as expected

From: Date: Mon, 16 Apr 2001 09:25:09 +0000
Subject: Bug #9156 Updated: stripslashes doesn't work as expected
Groups: php.dev 
Request: Send a blank email to php-dev+get-51642@lists.php.net to get a copy of this message
ID: 9156 Updated by: jmoore Reported By: nirf@sphera.com Old-Status: Feedback Status: Closed Bug Type: *Function Specific PHP Version: 4.0.4pl1 Assigned To: Comments: Please try this with 4.0.5 when it is released and repoen report if the problem still persists. I cannot reproduce this behaviour either. - James Previous Comments: --------------------------------------------------------------------------- [2001-03-15 08:52:32] stas@php.net For me, doing addslashes and then stripslashes on the string, it comes out exactly as it was. Please provide example of the code where it doesn't work. --------------------------------------------------------------------------- [2001-02-08 03:50:05] nirf@sphera.com when using preg_replace all seems like addslashes had been processed on the string found in \1 so if the programmer had already did addslashes on the string before preg_replace he gets \1 after double addslashes which results in strings " change to \" this might confuse users, and it might be added to the manual that all strings transfered to \1 are escape (addslashes) by default. --------------------------------------------------------------------------- [2001-02-07 12:40:07] nirf@sphera.com when doing addslashes() to a string and then doing stripslashes() doesn't remove all occurance of single or double qoutes. this is the string : <TD><?=$Data_Source_Values["aliases"]->node[$i]['destination']?></TD> <TD a'><?=$Data_Source_Values['aliases']->node[$i]['type']?></TD> <TD><?=$Data_Source_Values['alias']->node[$i]['alias"sds]?></TD> --------------------------------------------------------------------------- ATTENTION! Do NOT reply to this email! To reply, use the web interface found at http://bugs.php.net/?id=9156&edit=2

« previous php.dev (#51642) next »