Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:73168 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 13063 invoked from network); 14 Mar 2014 22:05:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Mar 2014 22:05:14 -0000 Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.44 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.215.44 mail-la0-f44.google.com Received: from [209.85.215.44] ([209.85.215.44:58017] helo=mail-la0-f44.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 12/00-12876-81D73235 for ; Fri, 14 Mar 2014 17:05:13 -0500 Received: by mail-la0-f44.google.com with SMTP id hr13so2218881lab.31 for ; Fri, 14 Mar 2014 15:05:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=MPmFpIGu7LkmoJv6KyUq3ViuaUoSqLbWwGF3WAALnPQ=; b=AhzODRPwPho+fJEGhVas64cXzofkVLeu27BFjZgTBS+5uvHbE8AouN/pmglDXeSMG3 S3G5M75Bj+PDbRihSDu+STRDTvtz5VezNnqajHe/kC4PqnvA/No5bolwdNKNx2e7o2dS mIb5AHB+bqvevLjQLr6SN1trX+ZjuEpf+usiLFdPcaWwZ2CPpnvj1OGuB3Jup8JMSxj6 3+NpApQjMCpuTTsNqr+1n6FgTwTeN+TePZKiBDlW7/d6CNy9rSNVKHMKiT654USr4+e1 OGfgxF8mJ7V3Uj/nZi46CNLaQdWxTvJ9pksVOh69r5mm+5W2SL5yoHlaQb75PHxLXaOA uVwA== X-Received: by 10.112.147.67 with SMTP id ti3mr6714190lbb.14.1394834709494; Fri, 14 Mar 2014 15:05:09 -0700 (PDT) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.205.73 with HTTP; Fri, 14 Mar 2014 15:04:29 -0700 (PDT) In-Reply-To: References: <530F0BF8.4040307@lsces.co.uk> <530F18C6.1000301@lsces.co.uk> <530F2264.10200@lsces.co.uk> <53219673.7070708@googlemail.com> <5322B46C.60005@googlemail.com> <5322DE0E.5070101@lsces.co.uk> Date: Sat, 15 Mar 2014 07:04:29 +0900 X-Google-Sender-Auth: IxTtiiMb7OSRGMWKIsu-gS47V14 Message-ID: To: Nikita Popov Cc: Lester Caine , PHP internals Content-Type: multipart/alternative; boundary=047d7b3441c461414604f49843f1 Subject: Re: [PHP-DEV] Re: [php6] Unicode support, options? From: yohgaki@ohgaki.net (Yasuo Ohgaki) --047d7b3441c461414604f49843f1 Content-Type: text/plain; charset=UTF-8 Hi Nikita, On Fri, Mar 14, 2014 at 8:20 PM, Nikita Popov wrote: > > Nothing is wrong with it, PCRE has very good support for UTF-8 (including > character properties and extended grapheme clusters). Can we just deprecate > mb_ereg? It seems totally useless and just confuses people. If you want to > match regular expressions on non-UTF-8 just do a conversion beforehand (or > use a sane encoding right away, you know). Encoding conversion would not work always. i.e. there are number of vendor specific extensions. Therefore, native encoding regex is required for those who need to handle chars. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --047d7b3441c461414604f49843f1--