Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

--enable-pcre and regex comparison (Was: make check problem)

X-seq: zsh-workers 34346
From: Lawrence Velázquez <vq@xxxxxxxxx>
To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
Subject: --enable-pcre and regex comparison (Was: make check problem)
Date: Thu, 22 Jan 2015 14:04:46 -0500
Cc: zsh-workers@xxxxxxx
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=larryv.me; h= x-sasl-enc:content-type:mime-version:subject:from:in-reply-to :date:cc:content-transfer-encoding:message-id:references:to; s= mesmtp; bh=t1EpPgbUMVL44sUH+V3ZjTuZ7uw=; b=PXosoHb4pz1pHb9koCYPQ 8ucYVLc1zvyoGUI10M8/2T3O16HkwhiWdotyAvSdiw+s5E9Cw8qfCe4ewNWC24Pg 7E0OaqsHWMKqeerIgGmpx1vZ5KggzKBTKjmmV9ihk7Gk6e2xU638WxtddrQ0B8D2 83S7YgatUuPS/RNXWpn6HE=
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=x-sasl-enc:content-type:mime-version :subject:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to; s=smtpout; bh=t1EpPgbUMVL44sUH+V3ZjTu Z7uw=; b=puEewNuyZTD8TXsq1OBjyi2RWbY/TCsK44VqmuFYY2ayMSR5M71+HI1 S9KsD9XPuNGj/Qq/KNrXuHh8ZLFy4vyOSC01T4WQ7nzd7EsoFU5IboH8e0V1mqRr 1tYeLM2NaX6fwbSsNCZLStiWP17mjUkU5kpth/wwF9nlefM5MUxw=
In-reply-to: <150122095610.ZM11712@torch.brasslantern.com>
List-help: <mailto:zsh-workers-help@zsh.org>
List-id: Zsh Workers List <zsh-workers.zsh.org>
List-post: <mailto:zsh-workers@zsh.org>
Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
References: <54B9AA99.6080403@eastlink.ca> <150116185732.ZM30791@torch.brasslantern.com> <54B9D726.2020108@eastlink.ca> <20150119102910.18102a0b@pwslap01u.europe.root.pri> <54C045A8.10102@eastlink.ca> <CF871D9C-A710-421B-BFB2-A3F2488AD7CC@kba.biglobe.ne.jp> <54C13593.9040602@eastlink.ca> <150122095610.ZM11712@torch.brasslantern.com>

On Jan 22, 2015, at 12:56 PM, Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:

> Sorry I forgot about --enable-pcre before.  You shouldn't link=static
> the zsh/pcre module without having used --enable-pcre in configure.
> 
> It's special because it's extremely non-standard and changes the meaning
> of the expressions on the right-hand-side of the =~ comparison, so if
> unknowingly enabled it might break scripts.

But doesn't that only take effect if RE_MATCH_PCRE is set?

vq

Follow-Ups:
- Re: --enable-pcre and regex comparison (Was: make check problem)
  - From: Bart Schaefer

References:
- completion
  - From: Ray Andrews
- Command substitution parsing issues (not really Re: completion)
  - From: Bart Schaefer
- Re: Command substitution parsing issues (not really Re: completion)
  - From: Ray Andrews
- Re: Command substitution parsing issues (not really Re: completion)
  - From: Peter Stephenson
- make check problem
  - From: Ray Andrews
- Re: make check problem
  - From: Jun T.
- Re: make check problem
  - From: Ray Andrews
- Re: make check problem
  - From: Bart Schaefer

Messages sorted by: Reverse Date, Date, Thread, Author