Bug #5919 Updated: stri_replace() to compliment str_replace()

ID: 5919 Updated by: gearond@cvc.net Reported By: juhl@eisenstein.dk Status: Open Bug Type: Feature/Change Request Operating System: Slackware Linux 7.0 PHP Version: 4.3.0 New Comment: Russians call the '@', little dog, 'sabachkee'. Anyway, I like the idea of stri_replace because the only alternative is a slower, and more complex usage of [eregi|pregi]_replace. And if one is replacing a lot of symbols, (like I am), and not just strings, then extensive knowledge of regex is required , (which I don't have yet), to replace all the symbols. I'm trying to escape all the key words and key symbols in Oracle's applications. Works great with str_replace, **IF** I want to change the whole string to upper or lower case, or use a function of my own. Otherwise, it sucks. I am implementing one of my own for now though, (actually copying the non recursive one under 'str_replace()'. To see an example of it, see: http://www.qweeka.com/db_tools.php after memorial day. Previous Comments: ------------------------------------------------------------------------ [2002-05-02 18:19:14] philip@php.net I marked similar feature requests as duplicates (bugs #10352 and #14215) and am changing the status of this to open. This feature request comes up fairly often, it's still open :) ------------------------------------------------------------------------ [2002-01-13 17:45:53] philip@cornado.com Please submit this patch :) ------------------------------------------------------------------------ [2001-05-07 10:57:33] derick@php.net Closing because of no feedback ------------------------------------------------------------------------ [2000-11-21 04:04:24] sniper@php.net Where's the patch? =) ------------------------------------------------------------------------ [2000-09-23 18:40:41] juhl@php.net > A patch that implements this feature will probably accepted In that case I'll start writing a patch :-) ------------------------------------------------------------------------ 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/5919 -- Edit this bug report at http://bugs.php.net/?id=5919&edit=1