Mailing-List: contact oro-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oro-user@jakarta.apache.org
Message-Id: <200107251754.f6PHsZR07830@yoda.savarese.org>
To: oro-user@jakarta.apache.org
Subject: Re: Is there a bug with :alpha:? 
In-reply-to: Your message of "Wed, 25 Jul 2001 13:43:47 EDT."
             <20010725174456.5068146894@lenard.microcelli5.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 25 Jul 2001 13:54:35 -0400
From: "Daniel F. Savarese" <dfs@savarese.org>


In message <20010725174456.5068146894@lenard.microcelli5.com>, Laurent Duperval
 writes:
>I don't know. In the Applet, I tried
>
>[[:alnum:]]
>
>With "J" in the entry box and it returns 1 match. If I do the same with
>[[:alpha:]] it doesn't work (0 matches). How do locales affect this (if at
>all)?

Ok, so that's what I get for testing on my local check out.  I fixed this
problem in the latest development release, but forgot about it.  From
the CHANGES file:

o Added code to Perl5Matcher to handle bytecode generated for [[:alpha:]].
  [[:alpha:]] would compile but not be interpreted.

This tells me it's time for a 2.0.4 release.

daniel