develooper Front page | perl.perl5.porters | Postings from October 2012

Re: Shouldn't \N{unknown name} be a syntax error?

Thread Previous
Karl Williamson
October 24, 2012 10:06
Re: Shouldn't \N{unknown name} be a syntax error?
Message ID:
On 09/10/2012 09:35 AM, Ricardo Signes wrote:
> * Karl Williamson <> [2012-09-09T19:00:59]
>> And now, Unicode has revised their advice on regular expressions and
>> they now say the same thing:
>> "The \N syntax should instead cause a syntax error for an undefined name"
> I think doing the above is sane at least to try.  Would it be enough to make
> the existing warning fatal and smoke the CPAN to see what the first few
> canaries, if any are?

The smoke showed only a semi-canary.  That was Encode-JP-Mobile-0.29. 
It deliberately has a test in a .t that looked to verify that this 
situation caused a warning and didn't just do something silently.

I submitted a patch for it, which is now included in the latest CPAN 

So, I have pushed to blead the change proposed above.

Thread Previous Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About