X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Eric Blake Subject: Re: Bash regex tests wh'appen? Date: Thu, 11 Jan 2007 16:41:25 +0000 (UTC) Lines: 18 Message-ID: References: <013b01c7359a$96ecb740$a501a8c0 AT CAM DOT ARTIMI DOT COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Dave Korn artimi.com> writes: > I upgraded quite a lot of bash versions in one go, and one of my > shell-scripts broke. I've reproduced it to a simple test case which shows > that either regex tests have turned into non-reg-ex text matches, or that I've > really misunderstood something here. I checked the last few release > announcements and didn't see anything about the behaviour of =~ changing. Bash 3.2 changed regex syntax. http://lists.gnu.org/archive/html/bug-bash/2006-10/msg00061.html http://sourceware.org/ml/cygwin/2006-12/msg00736.html /usr/share/doc/bash-3.2.9/NEWS item f -- Eric Blake -- 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/