develooper Front page | perl.perl5.porters | Postings from August 2010

Re: RFC: space vs. time vs. functionality in \N{name} loosematching

Thread Previous
From:
H.Merijn Brand
Date:
August 1, 2010 01:33
Subject:
Re: RFC: space vs. time vs. functionality in \N{name} loosematching
Message ID:
20100801103225.001090f8@pc09.procura.nl
On Thu, 29 Jul 2010 13:21:25 -0600, karl williamson
<public@khwilliamson.com> wrote:

> David Golden wrote:
> > On Thu, Jul 29, 2010 at 12:08 PM, karl williamson
> > <public@khwilliamson.com> wrote:
> >> Concisely, it is essentially the equivalent of a Unix 'diff -i -w', but with
> >> most hyphens considered to be white space as well.  Currently, when you say
> >> \N{LATIN CAPITAL LETTER A}, you currently must get the spacing exactly right
> >> and use all caps with no dashes for it to be understood. Loose matching
> >> would have, to use an extreme example, \N{La t in Capital letter-a} mean the
> >> same thing.
> > 
> > I think I favor your option #3, which seems to be "strict names by
> > default, unless you ask perl to dwim".
>
> Sorry for being unclear.  Yes it means the current behavior unless you 
> ask specifically for the new, loose behavior.

+1

-- 
H.Merijn Brand  http://tux.nl      Perl Monger  http://amsterdam.pm.org/
using 5.00307 through 5.12 and porting perl5.13.x on HP-UX 10.20, 11.00,
11.11, 11.23, and 11.31, OpenSuSE 10.3, 11.0, and 11.1, AIX 5.2 and 5.3.
http://mirrors.develooper.com/hpux/           http://www.test-smoke.org/
http://qa.perl.org      http://www.goldmark.org/jeff/stupid-disclaimers/

Thread Previous


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About