Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71697
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain oracle.com designates 156.151.31.81 as permitted sender)
Message-ID: <52E81217.7060603@oracle.com>
Date: Tue, 28 Jan 2014 12:24:55 -0800
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAGa2bXb7iVGbqpQh8TkDDyr-FmCWTFg1rcXj23ScErhNmikbNw@mail.gmail.com> <CA+kxMuTBjp=OhN0sHDrciJWKzre1mDKt_BSTja4UJ7_-JGnkGg@mail.gmail.com> <CAGa2bXb3UYFnUpFJBtNh=j9nP96ge7pXF-_AhG+tWwOPRSHS6A@mail.gmail.com> <CA+kxMuQvHpzM2GbUxRC9u5EPV3ZZz9F1qtDPcVRx3ZyAB22RUw@mail.gmail.com> <CA+kxMuQ25NhV9_Pyy+sBxakPDkX40FVzwAxGcmc0R7-MjDS-7w@mail.gmail.com> <CAGa2bXZqw_BWA3M-SKBfDymiVnBVJY_uB1VeBPpx45UYv1U6GQ@mail.gmail.com> <CAGa2bXa-dXGAQAXsE8KR0pR5wsS2hkQGKSOJr6_Ty1NgwJGYtg@mail.gmail.com>
In-Reply-To: <CAGa2bXa-dXGAQAXsE8KR0pR5wsS2hkQGKSOJr6_Ty1NgwJGYtg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [VOTE] RFC: Multibyte Char Handling
From: christopher.jones@oracle.com (Christopher Jones)



On 01/26/2014 06:53 PM, Yasuo Ohgaki wrote:
> Hi Dan,
>
> On Mon, Jan 27, 2014 at 9:09 AM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:
>
>> I just didn't want to touch 5 year old RFC.
>> As I wrote in parent RFC, the implementation is subject to be changed.
>>
>
> I've updated altmbstring RFC as this RFC name implies. Original author
> was intended to provide alternative to mbstring.
>
> In contrast, my RFC is intended to replace mbstring by mbstring-ng.
> There are technical difficulties to copy all of mbstring feature to
> mbstring-ng,
> we may evaluate them and decide migration procedure when mbstring-ng is
> ready.
>
> Choices would be
>   - provide mbstring-ng as alternative of mbstring
>       - keep mbstring-ng in php-src, move mbstring to PECL
>       - keep both mbstring-ng and mbstring in php-src
>   - replace mbstring by mbstring-ng and move mbstring to PECL as
> mbstring-legacy.
>
> I'm not sure which one is the best. We may try to find out by providing
> mbstring-ng
> as EXPERIMENTAL module.
>
> Regards,
>
> --
> Yasuo Ohgaki
> yohgaki@ohgaki.net
>

Since this RFC (https://wiki.php.net/rfc/multibyte_char_handling)
depends on another unfinalized one
(https://wiki.php.net/rfc/altmbstring), surely it is too premature to
be voting on https://wiki.php.net/rfc/multibyte_char_handling now?

The situation is just confusing and counter productive.

I quote from the RFC:

     Compile mbstringp-ng as default compiled module, when mbstring-ng
     is ready. See following FRC [sic] for mbstring-ng details.

     Alternative implementation of mbstring using ICU [the previous
     sentence is a link to https://wiki.php.net/rfc/altmbstring]

     Until mbstring-ng is ready, mbstring-ng is provided as
     EXPERIMENTAL module.

     mbstring-ng implementation is subject to be changed.

Chris

P.S. Am I the only one getting confused by a plethora of RFCs and
ideas and last minute changes?  If an RFC is changed materially, then
the vote should be stopped and restarted after an appropriate time for
discussion.

P.P.S. Some confusion could be avoided if the second part of #18
(about including the URL in emails) was followed from:
https://blogs.oracle.com/opal/entry/the_mysterious_php_rfc_process
This is a common issue with RFC discussions on internals.

-- 
christopher.jones@oracle.com  http://twitter.com/ghrd
Free PHP & Oracle book:
http://www.oracle.com/technetwork/topics/php/underground-php-oracle-manual-098250.html