Return-Path: <jon@latchkey.com>
Mailing-List: contact regexp-dev-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list regexp-dev@jakarta.apache.org
Received: (qmail 29078 invoked from network); 21 Jul 2000 00:23:13 -0000
Received: from mail.clearink.com (HELO clearink.com) (205.227.191.11)
  by locus.apache.org with SMTP; 21 Jul 2000 00:23:13 -0000
Received: from [131.161.251.227] ([131.161.251.227])
	by clearink.com (8.10.2/8.10.2) with ESMTP id e6L0N2v08093
	for <regexp-dev@jakarta.apache.org>; Thu, 20 Jul 2000 17:23:02 -0700
User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022
Date: Thu, 20 Jul 2000 17:23:13 -0700
Subject: Re: confusing behaviour of regexp code
From: Jon Stevens <jon@latchkey.com>
To: <regexp-dev@jakarta.apache.org>
Message-ID: <B59CE601.88B9%jon@latchkey.com>
In-Reply-To: 
 <7D508F33AD7AD311B634009027CC6331DFAADB@apollo.office.netdecisions.co.uk>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

on 6/29/2000 10:58 AM, "Nathan Coast" <nathan.coast@netdecisions.co.uk>
wrote:

> firstly is this the correct place to be sending these sort of questions?

yes.

> why should the ordering of the character values within [  ] be significant?
> 
> e.g. this string "-12+)( 3   "
> 
> is failed by
> 
> ^[\\(\\)0-9\\-\\+ ]+$
> 
> and passed by
> 
> ^[0-9\\-\\+ \\(\\)]+$

Ug. I'm no regex expert, but it sounds like it could be a bug.

-jon