Re: [RFC] UString
| From: | Andrea Faulds | Date: | Tue, 21 Oct 2014 13:38:34 +0000 |
| Subject: | Re: [RFC] UString | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-78200@lists.php.net to get a copy of this message | ||
> On 21 Oct 2014, at 13:35, Christian Schneider <cschneid@cschneid.com> wrote:
>
> 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.
I think we should reserve some way to do Unicode strings. I’d want u”foo”, but we’re not
adding literals, so u(“foo”) it is.
Also, bear in mind that namespaces mean you can still have your own u() if it’s in your namespace
(\u).
--
Andrea Faulds
http://ajf.me/