Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124880
Message-ID: <9aa10400-c967-47c7-8f23-592ac96554bd@sandfox.me>
Date: Mon, 12 Aug 2024 06:30:14 +0300
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV][Discussion] Should All String Functions Become
 Multi-Byte Safe?
To: internals@lists.php.net
References: <8a60a5d76bf3bbdda821160c6141b45914a33b98.camel@ageofdream.com>
 <410a8188-06bf-439f-bdab-c47e73d1db70@app.fastmail.com>
 <c00a7b2b80e83877ef94ebdf6fb9d5c9a8f977ce.camel@ageofdream.com>
Content-Language: en-US
In-Reply-To: <c00a7b2b80e83877ef94ebdf6fb9d5c9a8f977ce.camel@ageofdream.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
From: sandfox@sandfox.me (Anton Smirnov)

On 12/08/2024 00:36, Nick Lockheart wrote:
> So what I would propose is:
> 
> (1) All string functions should state in the official man page if they
> are safe for UTF-8 or not.

Reasonable but see below

> (2) Functions intended for working with text should be made UTF-8 safe.

Define precisely UTF-8 safe. Also, what about BC breaks here?

> (3) Functions intended for processing binary should be added if
> necessary, and should be named something like "binary" or "byte".

That would require renaming and deprecating most of the standard string 
library, I guess no one would agree to that.

But generally they are already named differently, str* are binary, mb_* 
and grapheme_* are text-oriented