Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58922
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAMUwpuTcZZS2c=ffDhCiw=aRkmGK_GLo4EAc5YouYTJWpEEuHw@mail.gmail.com>
References: <4F5D9C77.3030000@lerdorf.com>
	<4F5DA152.10109@sugarcrm.com>
	<4F5DA894.8060606@lerdorf.com>
	<4F5DAB49.3030808@sugarcrm.com>
	<4F5DAFCE.8020600@lerdorf.com>
	<CAGa2bXbNOqoDdQsmyWrXR+Qw8E6o2uxWbrnKXBwJewwjtpMJ_g@mail.gmail.com>
	<4F5E15D6.6080302@lerdorf.com>
	<CAGa2bXYSEk2UTKMnMGvA4R_mJrk1kO6BigSoC5U+aByW9eapEw@mail.gmail.com>
	<CAMUwpuTcZZS2c=ffDhCiw=aRkmGK_GLo4EAc5YouYTJWpEEuHw@mail.gmail.com>
Date: Wed, 14 Mar 2012 15:24:58 +0100
Message-ID: <CAH-PCH6jkH9zGd9U8BrkoeORyHc9xQMo1COWoqN9Jm+kLiLFpw@mail.gmail.com>
To: jpauli <jpauli@php.net>
Cc: Yasuo Ohgaki <yohgaki@ohgaki.net>, Rasmus Lerdorf <rasmus@lerdorf.com>, 
	Stas Malyshev <smalyshev@sugarcrm.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d0417019175813f04bb34bd0d
Subject: Re: [PHP-DEV] default charset confusion
From: tyra3l@gmail.com (Ferenc Kovacs)

--f46d0417019175813f04bb34bd0d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

>
>
> I would then propose to make mbstring compile time mandatory.
>
> I'm against yet another global ini setting, I find the actual ini setting=
s
> confusing enough to add one more that would moreover reflect mbstring one=
's
> (and add more and more confusion).
> Why not turn ext/mbstring mandatory at compile time, for all future PHP
> versions, like preg or spl are ?
>
> We do need multibyte handling either. ZendEngine takes advantage of
> mbstring for internal encoding as well, so I probably missed something as
> why it is still possible to --disable-mbstring (or not add
> --enable-mbstring) when compiling ? Has it a huge performance impact ?
>
> Thank you :)
>
> Julien.P
>

see
http://www.mail-archive.com/internals@lists.php.net/msg48452.html
http://lxr.php.net/opengrok/xref/PHP_5_4/UPGRADING#91
and
http://www.mail-archive.com/internals@lists.php.net/msg53863.html

basically the mbstring code in the ZE is only used if you
enable zend.multibyte, which is disabled by default, so it isn't mandatory
to have ext/mbstring for the default build/setup.
as you can see from the last link, I would support having ext/mbstring
builtin and always enabled, but I would like to hear from more people about
the pros and cons.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--f46d0417019175813f04bb34bd0d--