Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78199 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 34213 invoked from network); 21 Oct 2014 12:51:40 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Oct 2014 12:51:40 -0000 Authentication-Results: pb1.pair.com header.from=mike.php.net@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=mike.php.net@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.178 as permitted sender) X-PHP-List-Original-Sender: mike.php.net@gmail.com X-Host-Fingerprint: 209.85.216.178 mail-qc0-f178.google.com Received: from [209.85.216.178] ([209.85.216.178:58184] helo=mail-qc0-f178.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C7/26-02077-BD656445 for ; Tue, 21 Oct 2014 08:51:40 -0400 Received: by mail-qc0-f178.google.com with SMTP id c9so793907qcz.37 for ; Tue, 21 Oct 2014 05:51:36 -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:date:message-id:subject :from:to:cc:content-type; bh=8bawrcvpNJ3/WBt1XCsBddNAD4DUzIAYyQ92By+NaeE=; b=AExJioKkGF3yxzc92wW8IFCnhWJHYBWUK9Tnbxs/gcLbZ6Gy+LkGbX3fZPpDhGtzUK Z86s94qQrntihE94QV05jI7pnS8qb04c39PI79xo8gzj3TfONS7TLpQ0HIUN9klDpYQv Y2VXRvUQGhWRCmUcpghcr4Xaa4puXDeQheC5JANaLPMP5QO4SvVHm7Ws1kVanOXi7YKY as8fh+ergwL33MpTTFiuz4yaYlTbtM1bTrbg12aanNXaVG0cQJ7wmfWnobkooWQZ0xfd 8ITgE9ta9tUOD3/SouCT0PXyLiX5zgx/JIGkxvY+4bBlm9Rz5QGZ0QZaZ4PGHA7QLfu1 yp0w== MIME-Version: 1.0 X-Received: by 10.224.171.194 with SMTP id i2mr45608657qaz.59.1413895894823; Tue, 21 Oct 2014 05:51:34 -0700 (PDT) Sender: mike.php.net@gmail.com Received: by 10.140.142.199 with HTTP; Tue, 21 Oct 2014 05:51:34 -0700 (PDT) In-Reply-To: <45C5E14F-1623-4596-846E-B3933C68F993@cschneid.com> References: <1413875212.2624.3.camel@localhost.localdomain> <45C5E14F-1623-4596-846E-B3933C68F993@cschneid.com> Date: Tue, 21 Oct 2014 14:51:34 +0200 X-Google-Sender-Auth: aEd4MQ1cwizvrcQ2yLpT4kKkgHM Message-ID: To: Christian Schneider Cc: Joe Watkins , PHP Internals Content-Type: multipart/alternative; boundary=001a11c2b2768f7a890505ee4a41 Subject: Re: [PHP-DEV] [RFC] UString From: mike@php.net (Michael Wallner) --001a11c2b2768f7a890505ee4a41 Content-Type: text/plain; charset=UTF-8 On 21 October 2014 14:35, Christian Schneider wrote: > Am 21.10.2014 um 09:06 schrieb Joe Watkins : > > https://wiki.php.net/rfc/ustring > > > > This is the result of work done by a few of us, we won't be > opening any > > vote in a fortnight. We have a long time before 7, there is no rush > > whatever. > > > I have one concern I want to bring up: The RFC proposes a helper function > u() to generate UStrings. > > As this is a very handy function name for all sort of utility functions > (as a matter of face we use it to create and sanitize URL strings to be > embedded into HTML) I would assume that more than one project has a name > clash there. > > Maybe something like _u() could be used instead? Or do you have better > alternatives for this? > > PS: UString is also in the global name space but should be less of a > problem I'd imagine. > With the "use function" support, that could be located in a namespace. But something else: wasn't there a big concern in another thread regarding codepoint/grapheme support, like with $ustring->length()? -- Regards, Mike --001a11c2b2768f7a890505ee4a41--