Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sat, 17 Jan 2004 21:04:50 -0800 From: Yitzchak Scott-Thoennes To: cygwin AT cygwin DOT com Subject: Re: cygwin/regex is non-POSIX Message-ID: <20040118050449.GA3672@efn.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Organization: bs"d X-IsSubscribed: yes On Thu, Jan 15, 2004 at 03:14:57PM -0500, Sam Steingold wrote: > the cygwin regex is not POSIX. > backrefs are not available by default (apparently you need REG_BACKR for > that), "(a|)*" cannot be compiled because of "empty (sub)expression", > &c &c. > any plans to fix this? (e.g., by replacing it with gnu regex?) > thanks. SUSv3 says: A vertical-line appearing first or last in an ERE, or immediately following a vertical-line or a left-parenthesis, or immediately preceding a right-parenthesis, produces undefined results. Also, it says backrefs part of basic regular expressions but not exteneded ones. From your mention of | I assume you are using REG_EXTENDED. If REG_EXTENDED|REG_BACKR allows backrefs, it doesn't appear to be documented. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/