Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:55794
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain rile.ca designates 199.19.173.234 as permitted sender)
Reply-To: <mike@rile.ca>
To: "'Ferenc Kovacs'" <tyra3l@gmail.com>,
        "'PHP Internals'" <internals@lists.php.net>
References: <CAH-PCH6M1CbvSsJJDK2u+xF2seLwH9Ow6HjkBKHUDqqOVcL_bg@mail.gmail.com>
In-Reply-To: <CAH-PCH6M1CbvSsJJDK2u+xF2seLwH9Ow6HjkBKHUDqqOVcL_bg@mail.gmail.com>
Date: Thu, 13 Oct 2011 17:11:52 -0400
Message-ID: <004201cc89ec$bc4334f0$34c99ed0$@ca>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 7bit
Thread-Index: AcyILQGuNgGW0NxSTdya2SooluzGQQBvtMag
Content-Language: en-ca
Subject: RE: [PHP-DEV] enable mbstring by default
From: mike@rile.ca ("Mike Robinson")

On October-11-11 11:46 AM Ferenc Kovacs wrote:

> As the "full" unicode support went down with php6, wouldn't it be a
> logical step to enable the mbstring extension by default(maybe even
> turning it into a builtin ext like phar)?
> I think that mbstring is a pretty mature and stable extension, and
> there isn't much dependencies so I can't think of reason why we
> couldn't do it.
> Of course the mbstring.func_overload would still disabled by default
> (maybe exporting the mb functions to the 'utf8' namespace? :P), so it
> would be a backward compatible change.
> What do you think?
> 
> ps: maybe it is too late for 5.4, but having it in trunk is still
> better than nothing.

The mbstring extension was enabled by default once upon a time, if memory
serves, and as I recall the results were extremely painful. While both PHP
and mbstring have matured significantly since then, I'm old school that way.
Fool me once...

Best,

Mike Robinson