On 09/12/2014 00:51, Andrea Faulds wrote:
Please read through the RFC and cast your vote if you wish to do so:
https://wiki.php.net/rfc/unicode_escape
Voting starts today (2014-12-08) and ends in 10 days’ time (2014-12-18).
Hi,
A more complete and "long term" approach might come from a bette
On 13/12/14 08:57, Markus Fischer wrote:
>> https://wiki.php.net/rfc/unicode_escape
>> >
>> > Voting starts today (2014-12-08) and ends in 10 days’ time (2014-12-18).
> The RFC is really a good writeup, very much appreciated.
>
> I've voted no because I'm not entirely convinced the current approa
On 09.12.14 00:51, Andrea Faulds wrote:
> Good evening,
>
> I’m opening voting on the Unicode Codepoint Escape Syntax RFC. There’s been
> some discussion in the last two weeks since I introduced the RFC, but there’s
> nothing left which I feel needs changing. For the character name syntax
> sug
On Wed, Dec 10, 2014 at 11:56 AM, Andrea Faulds wrote:
> I’ve updated the patches for php-src and the specification to implement this,
> along with their tests, and I’ve also updated the RFC.
>
> Now this won’t error:
> "\"\u202e\""
>
> But this still will:
> "\u{foobar"
>
> I think this
> On 10 Dec 2014, at 19:16, Sara Golemon wrote:
>
>> A possible compromise might be to let ‘\u’ through but not ‘\u{‘.
>>
> Still don't like it from the inconsistency with existing escape
> sequence handlers pov, but it'd cover the biggest set of BC issues, so
> I'd be happy with it.
I’ve upda
On Wed, Dec 10, 2014 at 10:59 AM, Andrea Faulds wrote:
>> On 10 Dec 2014, at 18:55, Sara Golemon wrote:
>> I was just updating my HHVM patch to match your PHP implementation and
>> an issue came up. The following code, which is valid in PHP5:
>>
>> > echo json_decode("\"ma\u00F1ana\"");
>>
>> Wi
On Wed, Dec 10, 2014 at 06:59:39PM +, Andrea Faulds wrote:
> A possible compromise might be to let ‘\u’ through but not ‘\u{‘.
+1
I can see that some people might have \u (for what reason I do not know), but it
would be more unlikely for \u{ to be found in 'legacy' code.
--
Alain Williams
> On 10 Dec 2014, at 18:55, Sara Golemon wrote:
>
> On Mon, Dec 8, 2014 at 3:51 PM, Andrea Faulds wrote:
>> Please read through the RFC and cast your vote if you wish to do so:
>>
>> https://wiki.php.net/rfc/unicode_escape
>>
>> Voting starts today (2014-12-08) and ends in 10 days’ time (2014
On Mon, Dec 8, 2014 at 3:51 PM, Andrea Faulds wrote:
> Please read through the RFC and cast your vote if you wish to do so:
>
> https://wiki.php.net/rfc/unicode_escape
>
> Voting starts today (2014-12-08) and ends in 10 days’ time (2014-12-18).
>
I was just updating my HHVM patch to match your PHP
Hi Derick,
> On 9 Dec 2014, at 16:54, Derick Rethans wrote:
>
>> On Tue, 9 Dec 2014, Andrea Faulds wrote:
>>
>> I think \x{} is misleading anyway - \xXX is always
>> single-byte/character, yet Unicode code points can’t be represented in
>> PHP strings as single bytes when encoded in UTF-
On Tue, 9 Dec 2014, Andrea Faulds wrote:
> I think \x{} is misleading anyway - \xXX is always
> single-byte/character, yet Unicode code points can’t be represented in
> PHP strings as single bytes when encoded in UTF-8 (unless they’re
> below U+0100, of course).
You mean below U+0080 surel
Lester Caine wrote on 09/12/2014 16:00:
On 09/12/14 15:30, Rowan Collins wrote:
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 wrote:
On 09/12/14 13:07, Andrea Faulds wrote:
On 9 Dec 2014, at 08:15, Lester Caine wrote
On 09/12/14 15:30, Rowan Collins wrote:
> 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 wrote:
> On 09/12/14 13:07, Andrea Faulds wrote:
>
>> On 9 Dec 2014, at 08:15, Lester Caine wrote:
>>
>>
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 wrote:
On 09/12/14 13:07, Andrea Faulds wrote:
On 9 Dec 2014, at 08:15, Lester Caine wrote:
If ICU is to be adopted as the base for unicode support, then surely
everything
On 09/12/14 14:07, Andrea Faulds wrote:
>
>> On 9 Dec 2014, at 13:35, Lester Caine wrote:
>>
>>> On 09/12/14 13:07, Andrea Faulds wrote:
>>>
On 9 Dec 2014, at 08:15, Lester Caine wrote:
If ICU is to be adopted as the base for unicode support, then surely
everything else shoul
> On 9 Dec 2014, at 13:35, Lester Caine wrote:
>
>> On 09/12/14 13:07, Andrea Faulds wrote:
>>
>>> On 9 Dec 2014, at 08:15, Lester Caine wrote:
>>>
>>> If ICU is to be adopted as the base for unicode support, then surely
>>> everything else should follow those rules?
>>> \u and \U
On 09/12/14 13:07, Andrea Faulds wrote:
>
>> On 9 Dec 2014, at 08:15, Lester Caine wrote:
>>
>> If ICU is to be adopted as the base for unicode support, then surely
>> everything else should follow those rules?
>> \u and \U are defined along with \x{hh} so does it make
>> sense to
> On 9 Dec 2014, at 08:15, Lester Caine wrote:
>
> If ICU is to be adopted as the base for unicode support, then surely
> everything else should follow those rules?
> \u and \U are defined along with \x{hh} so does it make
> sense to add something which is not part of ICU?
Er, w
On 09/12/14 02:44, Andrea Faulds wrote:
>> Maybe there should be more elaboration on why PHP itself should go with
>> > the \u{} ECMAScript representaton, thus introducing a syntax disparity
>> > with our most major string handling extension.
> Well, PCRE does what it does probably because of i
Tue, 9 Dec 2014 02:44:33 + Andrea Faulds :
>
> Well, PCRE does what it does probably because of its name:
> *Perl-Compatible* Regular Expressions. Perl has the \x syntax. But
> PCRE’s syntax comes from what suits Perl, not PHP, so I don’t see why
> we should necessarily match its behaviour. If
Hi!
> On 9 Dec 2014, at 02:14, ma...@include-once.org wrote:
>
> 2014-12-09 0:51 GMT+01:00 Andrea Faulds :
>>
>> https://wiki.php.net/rfc/unicode_escape
>
>
> Still leaves unmentioned that there was already an established Unicode
> escape syntax. PCRE provides \x{1F520} for codepoints in conju
2014-12-09 0:51 GMT+01:00 Andrea Faulds :
>
> https://wiki.php.net/rfc/unicode_escape
Still leaves unmentioned that there was already an established Unicode
escape syntax. PCRE provides \x{1F520} for codepoints in conjunction to
plain \xFF for byte escapes.
Maybe there should be more elaboration
On Tue, Dec 09, 2014 at 12:38:54AM +, Andrea Faulds wrote:
> Hi Alain,
>
> > On 9 Dec 2014, at 00:11, Alain Williams wrote:
> >
> > I vote 'yes’.
>
> At the risk of stating the obvious: I don’t see your vote on the page’s
> voting widget. Please vote there.
I looked ... I now see that I n
thanks for the rfc! Maybe you can add to the documentation that older PHP
versions can use json_decode with the limit to 4 hex digits:
php -r "echo json_decode('\"man\u0303ana\"');"
php -r "echo json_decode('\"ma\u00F1ana\"');"
Regards
Thomas
Andrea Faulds wrote on 09.12.2014 00:51:
> Good ev
Hi Alain,
> On 9 Dec 2014, at 00:11, Alain Williams wrote:
>
> I vote 'yes’.
At the risk of stating the obvious: I don’t see your vote on the page’s voting
widget. Please vote there.
Thanks!
--
Andrea Faulds
http://ajf.me/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubs
On Mon, Dec 08, 2014 at 11:51:37PM +, Andrea Faulds wrote:
> Good evening,
>
> I’m opening voting on the Unicode Codepoint Escape Syntax RFC. There’s been
> some discussion in the last two weeks since I introduced the RFC, but there’s
> nothing left which I feel needs changing. For the chara
26 matches
Mail list logo
