Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:55779 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 70921 invoked from network); 11 Oct 2011 15:46:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Oct 2011 15:46:10 -0000 Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.170 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.160.170 mail-gy0-f170.google.com Received: from [209.85.160.170] ([209.85.160.170:59668] helo=mail-gy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AF/6E-26502-1C4649E4 for ; Tue, 11 Oct 2011 11:46:10 -0400 Received: by gyb11 with SMTP id 11so7685534gyb.29 for ; Tue, 11 Oct 2011 08:46:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=d8AsaNV8IyCm8c/5kChTT7MmaFLDH8tL1bo2tkMLqCU=; b=VNNtAfK8CBLzeNf7d0ll52oKcv0U/GiW5DdC3aHOteB/osgxaRyjYAwd2rLrvCwIL3 sFoSxLGGcVHwSnK/8isukUsq68ynUuAr70Ysw9NkHCubf6sxXWTKpda8zPvCmiHc3HWG ToO23EcwB6GD7jJwJqkARqe40R5XIqZX+3NTM= MIME-Version: 1.0 Received: by 10.150.131.1 with SMTP id e1mr10609332ybd.37.1318347966754; Tue, 11 Oct 2011 08:46:06 -0700 (PDT) Received: by 10.147.125.13 with HTTP; Tue, 11 Oct 2011 08:46:06 -0700 (PDT) Date: Tue, 11 Oct 2011 17:46:06 +0200 Message-ID: To: PHP Internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: enable mbstring by default From: tyra3l@gmail.com (Ferenc Kovacs) Hi. 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. --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu