From 7123e3dc020324cc51e4d76f3b763a10473111ec Mon Sep 17 00:00:00 2001
From: Sara Golemon <pollita@php.net>
Date: Fri, 20 Jun 2003 16:01:59 +0000
Subject: [PATCH] Add warning about potential BC break

git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@132629 c90b9560-bf6c-de11-be94-00142212c4b1
---
 reference/strings/functions/str-replace.xml | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/reference/strings/functions/str-replace.xml b/reference/strings/functions/str-replace.xml
index 330d3cfb86..4f611f84d6 100644
--- a/reference/strings/functions/str-replace.xml
+++ b/reference/strings/functions/str-replace.xml
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.6 $ -->
+<!-- $Revision: 1.7 $ -->
 <!-- splitted from ./en/functions/strings.xml, last change in rev 1.2 -->
   <refentry id="function.str-replace">
    <refnamediv>
@@ -29,6 +29,18 @@
      In PHP 4.0.5 and later, every parameter to
      <function>str_replace</function> can be an array.
     </para>
+    <warning>
+     <simpara>
+      In PHP versions prior to 4.3.3 a bug existed when using arrays as
+      both <parameter>search</parameter> and <parameter>replace</parameter>
+      parameters which caused empty <parameter>search</parameter> indexes
+      to be skipped without advancing the internal pointer on the
+      <parameter>replace</parameter> array. This has been corrected in
+      <literal>PHP 4.3.3</literal>, any scripts which relied on this bug
+      should remove empty search values prior to calling this function in
+      order to mimick the original behavior.
+     </simpara>
+    </warning>
     <para>
      If <parameter>subject</parameter> is an array, then the search
      and replace is performed with every entry of