RE: [PHP-DEV] Re: str_ireplace vs. stri_replace

If your using an undocumented parameter, and that undocumented parameter changes what's the problem? The documentation doesn't say a word about a mystery undocumented parameter... I don't think we should be too concerned with someone using something they arguably shouldn't be. John >-----Original Message----- >From: Sara Golemon [mailto:pollita@php.net] >Sent: Thursday, January 30, 2003 5:39 PM >To: php-dev@lists.php.net >Subject: Re: [PHP-DEV] Re: str_ireplace vs. stri_replace > > >> > +1 from me too, stri_replace sound like a function some users may >> > +have >> > >> > implemented them selves and we could end up breaking their code by >> > introducing it. >> >> exactly :). >> >Only one complaint. > >Previously (including in 4.3.0) there already WAS a fourth >(undocumented) parameter to str_replace. A boolean value >which would allow the user to use an alternate search and >replace method. True, this was undocumented, and was probably >only included for developer debugging (Sascha? Can you enlighten us?). > >This alternate method has been removed (by virtue of being >deprecated) and should produce wrong param count errors for >users who include that fourth parameter currently (how many >would even know of this?) so that they can fix their code. > >If we introduce a *new* fourth parametere (also boolean) which >checks for case_sensitivity, this could potentially cause >problems for users who were using this undocumented parameter. > Leaving the fourth and adding a fifth would get even more >confusing if the appearance is that the fourth parameter was >just added *and* served no purpose. > >So, we could relegate those VERY few who might've used that >fourth parameter already to the "read the changelog or suffer" >bucket, or........not. > >-Pollita > > >-- >PHP Development Mailing List <http://www.php.net/> >To unsubscribe, visit: http://www.php.net/unsub.php > >