Re: range operator vs. unicode

2006-06-08 Thread Dan Kogai
On Jun 08, 2006, at 17:34 , Yitzchak Scott-Thoennes wrote: Which part should be fixed? The limitation of the magic, namely The key part is that magical auto-increment is defined earlier as only working for strings matching /^[a-zA-Z]*[0-9]*\z/. Which is described in Auto-increment and

[PATCH] Re: range operator vs. unicode

2006-06-08 Thread Yitzchak Scott-Thoennes
On Thu, Jun 08, 2006 at 05:56:13PM +0900, Dan Kogai wrote: On Jun 08, 2006, at 17:34 , Yitzchak Scott-Thoennes wrote: Which part should be fixed? The limitation of the magic, namely The key part is that magical auto-increment is defined earlier as only working for strings matching

Re: range operator vs. unicode

2006-06-08 Thread Yitzchak Scott-Thoennes
On Thu, Jun 08, 2006 at 05:03:15PM +0900, Dan Kogai wrote: I found that ('a'..'z') works only for alphanumerals. Try the code below; use strict; use warnings; #use utf8; use charnames ':full'; binmode STDOUT, ':utf8'; # works print $_\n for (\N{LATIN CAPITAL LETTER A} .. \N{LATIN

Re: range operator vs. unicode

2006-06-08 Thread Dr.Ruud
Dan Kogai schreef: I found that ('a'..'z') works only for alphanumerals. Just like it is documented. But your definition of 'alphanumeral' is stale: news:[EMAIL PROTECTED] -- Affijn, Ruud Gewoon is een tijger.

Re: range operator vs. unicode

2006-06-08 Thread SADAHIRO Tomoyuki
On Thu, 8 Jun 2006 11:03:42 +0200, Rafael Garcia-Suarez [EMAIL PROTECTED] wrote Sure, we can extend the magic to ensure that the increment of a variable that holds \N{omega} is \N{alpha}\N{alpha}. But I feel that dragons might be dormant here... If is the ranges of greak letters to be