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

On Tue, Jun 14, 2011 at 07:43:50PM -0600, Karl Williamson wrote:
> The current behavior of \N{} when it can't find the name is to raise a  
> warning and return the REPLACEMENT character.  This seems wrong to me,  
> as it is a compilation-time construct, and every other place I'm  
> familiar with bails out under such circumstances.
>
> Changing this would not have backwards compatibility issues, since the  
> likelihood of someone deliberately using this to insert a REPLACEMENT  
> character into a string seems vanishingly small to me.



Would it be possible to autoload 'use charnames ":full"' if \N{} can't
find a name, and charnames hasn't be loaded yet?


Abigail

• Shouldn't \N{unknown name} be a syntax error? by Karl Williamson
• Re: Shouldn't \N{unknown name} be a syntax error? by Abigail
• Re: Shouldn't \N{unknown name} be a syntax error? by demerphq
• Re: Shouldn't \N{unknown name} be a syntax error? by Karl Williamson
• Re: Shouldn't \N{unknown name} be a syntax error? by Tom Christiansen
• Re: Shouldn't \N{unknown name} be a syntax error? by Karl Williamson
• Re: Shouldn't \N{unknown name} be a syntax error? by Karl Williamson
• Re: Shouldn't \N{unknown name} be a syntax error? by Jesse Vincent
• Re: Shouldn't \N{unknown name} be a syntax error? by Karl Williamson
• Re: Shouldn't \N{unknown name} be a syntax error? by Ricardo Signes
• Re: Shouldn't \N{unknown name} be a syntax error? by Karl Williamson