Lester Caine wrote on 09/12/2014 15:07:
On 09/12/14 14:07, Andrea Faulds wrote:
On 9 Dec 2014, at 13:35, Lester Caine <les...@lsces.co.uk> wrote:
On 09/12/14 13:07, Andrea Faulds wrote:
On 9 Dec 2014, at 08:15, Lester Caine <les...@lsces.co.uk> wrote:
If ICU is to be adopted as the base for unicode support, then surely
everything else should follow those rules?
\uhhhh and \Uhhhhhhhh are defined along with \x{hhhhhh} so does it make
sense to add something which is not part of ICU?
Er, where does ICU define \uXXXX and \UXXXXXX? I don't unferstand.
http://userguide.icu-project.org/strings/regexp
We aren't using ICU regular expressions, and ICU is merely an implementation
detail anyway.
Has THAT been agreed on? Surely if using ICU fully in PHP7 in place of
the patchwork of current fixes for unicode then we don't want to be
breaking thing again by odd differences from the core code for unicode?
I though the agreement was that there was no resource to create an
alternative from scratch?
I think what Andrea's getting at is that the fact that ICU is in use
under the hood shouldn't be particularly visible to users. If PHP gets
"Unicode support" (whatever that turns out to mean), what the user
should see is *PHP's Unicode facilities*; only core devs and package
maintainers will need to know that those are implemented using ICU. As
such, there's no automatic need for PHP to do everything the same way as
ICU.
--
Rowan Collins
[IMSoP]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
