Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84123
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.49 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <54F377D2.7030601@lsces.co.uk>
References: <1413875212.2624.3.camel@localhost.localdomain>
 <CA+9eiLtVUsbRQA9S0eagVfOc3aovhuak=QQmnBKp_BmgN4n28w@mail.gmail.com>
 <CAGKNXQEYquY_YQvTRv7uAhaycyCNG1FRwX_GYZ1dnHfhC-biZg@mail.gmail.com>
 <54469840.3070708@sugarcrm.com> <1414051917.2624.35.camel@localhost.localdomain>
 <CA+9eiLsC1dD9vp=uWqdYTXj7hC=mBnOMSs5B6KFngOQPd1m4OA@mail.gmail.com>
 <1414060726.2624.60.camel@localhost.localdomain> <1414072403.3228.3.camel@kuechenschabe>
 <87D717D5-273B-4A32-A3E5-83EBDFD314CB@ajf.me> <1414077690.3228.12.camel@kuechenschabe>
 <54495CF6.30608@sugarcrm.com> <1414130585.2624.64.camel@localhost.localdomain>
 <CAGAGxbaKK4P2D5epQTzEzNx3jcBP7XCPexGA4gyA3hdx3p+UKg@mail.gmail.com>
 <CAL=_i_nDz0XoVA5d4gqinYg9GinJUMW55+HLQ4y9O3Nj_URoxw@mail.gmail.com> <54F377D2.7030601@lsces.co.uk>
Date: Mon, 2 Mar 2015 06:26:05 +0900
Message-ID: <CAGa2bXafqG0Y==4jZtRpOUtBsx7OTX9VA5nAPC-L0Z8pOHtRVQ@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113551e42f26c6051040c2cc
Subject: Re: [PHP-DEV] [RFC] UString
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a113551e42f26c6051040c2cc
Content-Type: text/plain; charset=UTF-8

Hi Lester,

On Mon, Mar 2, 2015 at 5:34 AM, Lester Caine <lester@lsces.co.uk> wrote:

> On 28/02/15 06:48, Joe Watkins wrote:
> >     This is just a quick note to announce my intention to ready this RFC
> > for voting next week.
>
> Since there is nothing in this which needs any changes to the core then
> surly it simply needs to exist in pecl until such time as a proper
> replacement for unicode in core strings has been addressed? Since it
> will still require intl to provide those areas it does not support, and
> I question if we really need to provide yet another encoding converter.
>
> A unicode string handler that just handles UTF8 strings may be yet
> another stepping stone, but it still falls short of beings able to
> handle all of the internationalization problems and is simply an
> alternate to mbstring so one either runs both, or sit down and convert
> all the third party libraries to eliminate mbstring.
>
> Like http extension, it's not essential that it's loaded by default, and
> leaving it in pecl allows development outside that of the core?


Although it seems current code does not have code like GMP. I'm sure
we'll have this before release. i.e.

$new = $some_ustring . 'abc'; // $new is UString object

To implement feature like this, it cannot be PECL.

My only concern for this RFC performance. It's loosely integrated into PHP
core, it may affect efficiency. I suppose other people are working on simple
and tighter integration into core. Any comments on this?

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a113551e42f26c6051040c2cc--