Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71709
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.47 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <52E81217.7060603@oracle.com>
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> <52E81217.7060603@oracle.com>
Date: Wed, 29 Jan 2014 11:07:46 +0900
Message-ID: <CAGa2bXbcLquJjKChpGhnVC8q4bLkM+4zvf+9OLBFyrOL1wzDWA@mail.gmail.com>
To: Christopher Jones <christopher.jones@oracle.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0112bf4491a7c704f1126a26
Subject: Re: [PHP-DEV] [VOTE] RFC: Multibyte Char Handling
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--089e0112bf4491a7c704f1126a26
Content-Type: text/plain; charset=UTF-8

Hi Christopher,

On Wed, Jan 29, 2014 at 5:24 AM, Christopher Jones <
christopher.jones@oracle.com> wrote:

> 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 asked comments, but people tends to read RFC actually when
vote is started...

I don't mind at all change status to under discussion, though.

Since compiling current mbstring by default is not good idea for some
users, it would be nice to have load map for this issue. Making mbstring-ng
mature is impossible in short term. We do need some experiments and
feedbacks if it's really possible.

Do you have any suggestion for this?

 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.
>

I agree. Let's discuss!


>
> 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.
>

I'll add more threads to the RFC. Thank  you.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--089e0112bf4491a7c704f1126a26--