Re: Reference from str_ireplace to str_replace
| From: | Maciej Sobaczewski | Date: | Fri, 15 Aug 2014 14:12:44 +0000 |
| Subject: | Re: Reference from str_ireplace to str_replace | ||
| References: | 1 2 3 4 | Groups: | php.doc |
| Request: | Send a blank email to phpdoc+get-969385107@lists.php.net to get a copy of this message | ||
W dniu 2014-08-15 16:09, Chris Wright pisze:
On 15 August 2014 14:05, Maciej Sobaczewski <sobak@php.net> wrote:Are there any objections against doing it? Something what I overloooked, i.e. content that it's not duplicated in 100%? Cheers, Maciej.Accidentally sent this off-list :/ With few days of a delay but here it is. 2014-08-13 09:54, Christian Stoller wrote:I think that creating a page like the alias pages would be OK ("This is a case-insensitive version of str_replace()" with just a link). I do not think it should make any mention of preg_replace() directly. str_replace() should have this linked in the "see also" section and I suspect that mentioning it on a stub page for str_ireplace() would have the opposite effect of that which is desired. I thought about preg_replace() with i modifier as it differs from normal call. It is all about case intensivity.From: Maciej Sobaczewski [mailto:sobak@php.net] Sent: Tuesday, August 12, 2014 2:58 PMHello Christian, I probably made it unclear. I do not want to merge those pages. I'm proposing to leave str_ireplace() but remove duplicated content. So, basically, leave function signature on str_ireplace() and leave description saying that user can use it instead of preg_replace() with i modifier and that further documentation is available on str_replace() page. As far as I can see rest of information is the same on both pages so I think that it makes no sense to keep it duplicated and maintain two places instead of one.Hello, Firstly, sorry for unclear subject. I don't know how to write it shortly and clear, due to my limited English skills. I'm wondering if this wouldn't be better solution to link from str_ireplace() to str_replace() and delete duplicated content. Basically, the approach as in require and include pair. What do you think? Regards, Maciej.I think this would make the doku less readable, because you will have to list the different function definitions. Christian