From xemacs-m  Thu Jan 30 11:34:44 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
          by xemacs.org (8.8.4/8.8.4) with ESMTP
	  id LAA13125 for <xemacs-beta@xemacs.org>; Thu, 30 Jan 1997 11:34:43 -0600 (CST)
Received: by crystal.WonderWorks.COM 
	id QQcati23793; Thu, 30 Jan 1997 12:34:38 -0500 (EST)
Date: Thu, 30 Jan 1997 12:34:38 -0500 (EST)
Message-Id: <QQcati23793.199701301734@crystal.WonderWorks.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Kyle Jones <kyle_jones@wonderworks.com>
To: xemacs-beta@xemacs.org
Subject: regex dump on DUNIX
In-Reply-To: <9701301207.AA12266@fornet.gvc.dec.com>
References: <9701301207.AA12266@fornet.gvc.dec.com>

Steve Carney writes:
 >   looking-at("^\\([^    \n:]+[  ]*:\\) *\\(.*\\(\n[     ].*\\)*\n\\)")

Putting expr* next to expr+ where both exprs can match the same
text makes the v19 regex code go blooey on long matches.  It has
been this way for years.  The answer is, near as I can tell,
"don't do that."  I purged VM of such expressions as part of the
ordeal of porting to v19 Emacs.

