Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:79217 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 72834 invoked from network); 27 Nov 2014 08:22:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Nov 2014 08:22:57 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.172 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.192.172 mail-pd0-f172.google.com Received: from [209.85.192.172] ([209.85.192.172:36395] helo=mail-pd0-f172.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9C/34-40216-06FD6745 for ; Thu, 27 Nov 2014 03:22:57 -0500 Received: by mail-pd0-f172.google.com with SMTP id y13so4542353pdi.3 for ; Thu, 27 Nov 2014 00:22:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=hLszDVm6SI5bKnAtlcjhyb7+qiQkqOVQ4atPVcy2+Sw=; b=tTgL/KbsKKYCmJmkvJ0O/TbyUkOjAnhm00nKsWc1zwQ4Db8P+ReXQeUcVxj46/LFOv vXsed6HPbUvQ8v31p7veMUMDaGkgB6oGm+a3FXngXZYjMjeySXFymMHACZs49jS0+t/Z mFd86Ad6GcCmhy7bSGDcFV3ACgurvK33u2g0MWJgtQrv+icFFuRWtMXu9TSsC8Ssq5Kl tWNaPUAjBfEdRuft48kMrK3EOXNm5rWBQbzz/ZUJSY5TxLulTq3itfaYiR88yFaC6hX1 u0iJD8g85jg3jLPkvPg4/bUo8zHbR89EY8H1IqGgxWCqTYy6y7YMDHXojdVpjCikd2qG 83vg== X-Received: by 10.68.220.39 with SMTP id pt7mr44027215pbc.37.1417076574526; Thu, 27 Nov 2014 00:22:54 -0800 (PST) Received: from Stas-Air.local (108-66-6-48.lightspeed.sntcca.sbcglobal.net. [108.66.6.48]) by mx.google.com with ESMTPSA id my1sm6377856pbc.20.2014.11.27.00.22.53 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 27 Nov 2014 00:22:53 -0800 (PST) Message-ID: <5476DF5C.6040807@gmail.com> Date: Thu, 27 Nov 2014 00:22:52 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Sara Golemon , PHP internals References: <54767CAC.9060608@gmail.com> In-Reply-To: <54767CAC.9060608@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] IntlChar class and intl_char_*() functions From: smalyshev@gmail.com (Stanislav Malyshev) Hi! >> While playing around with Andrea's unicode literals syntax proposal, I >> was reminded of just how little of ICU is exposed. I've put up a >> short proposal for adding IntlChar exporting these APIs as static >> methods (with a matching non-oop interface). >> >> https://wiki.php.net/rfc/intl.char Looking into this and also reading the \u{} proposal, I also thought - do we have a programmatic way of doing what \u would do? I.e. if we assume $x holds an Unicode codepoint value (i.e., an integer) do we have a good built-in way to generate the corresponding utf8 sequence? If not, then I think this class may be a good place to put such a function in. -- Stas Malyshev smalyshev@gmail.com