Return-Path: 
 <regexp-dev-return-756-apmail-jakarta-regexp-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-regexp-dev-archive@www.apache.org
Received: (qmail 57793 invoked from network); 16 Mar 2004 08:22:10 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 16 Mar 2004 08:22:10 -0000
Received: (qmail 48935 invoked by uid 500); 16 Mar 2004 08:21:47 -0000
Delivered-To: apmail-jakarta-regexp-dev-archive@jakarta.apache.org
Received: (qmail 48840 invoked by uid 500); 16 Mar 2004 08:21:46 -0000
Mailing-List: contact regexp-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:regexp-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:regexp-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:regexp-dev-help@jakarta.apache.org>
List-Post: <mailto:regexp-dev@jakarta.apache.org>
List-Id: "Regexp Developers List" <regexp-dev.jakarta.apache.org>
Reply-To: "Regexp Developers List" <regexp-dev@jakarta.apache.org>
Delivered-To: mailing list regexp-dev@jakarta.apache.org
Received: (qmail 48825 invoked from network); 16 Mar 2004 08:21:46 -0000
Received: from unknown (HELO exchange.sun.com) (192.18.33.10)
  by daedalus.apache.org with SMTP; 16 Mar 2004 08:21:46 -0000
Received: (qmail 2629 invoked by uid 50); 16 Mar 2004 08:22:30 -0000
Date: 16 Mar 2004 08:22:30 -0000
Message-ID: <20040316082230.2628.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: regexp-dev@jakarta.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 9153]  -
    RE.match() hangs when using {n,m}
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=9153>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=9153

RE.match() hangs when using {n,m}





------- Additional Comments From o_sukhodolsky@yahoo.com  2004-03-16 08:22 -------
I think that the cause of the problem is the way we compile <something>{n,m} 
constuction.  As far as I can see, program for it is equal to
<something>{n}(<something>|)...(<something>|) (this has exponentional 
complexity)
So, during matching we have no way to optimize this.
Possible way to fix the problem would be adding new operation for this 
construction, so we process it faster.

---------------------------------------------------------------------
To unsubscribe, e-mail: regexp-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: regexp-dev-help@jakarta.apache.org