Re: [VOTE] RFC: Multibyte Char Handling
Hi Christopher,
On Wed, Jan 29, 2014 at 5:24 AM, Christopher Jones <
[email protected]> 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
[email protected]
Thread (20 messages)