Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:55845 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 27425 invoked from network); 17 Oct 2011 13:35:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Oct 2011 13:35:52 -0000 Authentication-Results: pb1.pair.com smtp.mail=tom@punkave.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tom@punkave.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain punkave.com designates 209.85.212.42 as permitted sender) X-PHP-List-Original-Sender: tom@punkave.com X-Host-Fingerprint: 209.85.212.42 mail-vw0-f42.google.com Received: from [209.85.212.42] ([209.85.212.42:41728] helo=mail-vw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 20/A5-27630-63F2C9E4 for ; Mon, 17 Oct 2011 09:35:50 -0400 Received: by vwl1 with SMTP id 1so2820342vwl.29 for ; Mon, 17 Oct 2011 06:35:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.115.74 with SMTP id jm10mr19759520vdb.40.1318858546638; Mon, 17 Oct 2011 06:35:46 -0700 (PDT) Received: by 10.220.199.136 with HTTP; Mon, 17 Oct 2011 06:35:46 -0700 (PDT) In-Reply-To: References: <004201cc89ec$bc4334f0$34c99ed0$@ca> Date: Mon, 17 Oct 2011 09:35:46 -0400 Message-ID: To: Klaus Silveira Cc: PHP Internals Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [PHP-DEV] enable mbstring by default From: tom@punkave.com (Tom Boutell) Will PHP really never, ever, ever be unicode by default? It'll always be a weird special case to not be from the shores of the Atlantic? On Thu, Oct 13, 2011 at 5:41 PM, Klaus Silveira wrote: > What drawbacks could possibly be brought with mbstring being enabled by > default? > > On Thu, Oct 13, 2011 at 6:11 PM, Mike Robinson wrote: > >> 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 >> >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php >> >> > > > -- > Klaus Silveira > (011) 8564-2492 > www.klaussilveira.com > -- Tom Boutell P'unk Avenue 215 755 1330 punkave.com window.punkave.com