Hi Stas,
On Thu, Jan 16, 2014 at 4:22 PM, Stas Malyshev <[email protected]>wrote:
> > We need few more basic functions like trim().
> > This is different issue, but I may work on it.
>
> It feels like we will end up with creating clones of pretty every string
> function there is. Not sure it is the best approach...
We could learn from Python 2.x and 3.x.
There are Python users, who are serious about multilingual support,
complain about 3.x. They insist 2.x behavior and even want to
discontinue 3.x.
I don't think mbstring is optimum multibyte string library neither.
We may keep current structure until we have decent multibyte
string library that could live long enough.
By the time we have it, we may use compatibility switch for
basic string functions to change multibyte awareness.
If we are going to choose this way, it may be better to have
byte_len() and other byte_*() function now for easier transition.
I'm not sure which is the best having mb_*(), byte_*() or specifying
binary encoding for standard string functions, though.
It's out of this RFC scope.
Regards,
--
Yasuo Ohgaki
[email protected]