Zsh Mailing List Archive
Messages sorted by:
Re: REMATCH_PCRE with zsh built without pcre support
- X-seq: zsh-users 22654
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Zsh Users <zsh-users@xxxxxxx>
- Subject: Re: REMATCH_PCRE with zsh built without pcre support
- Date: Mon, 3 Apr 2017 11:00:16 -0700
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:date:in-reply-to:comments:references:to:subject :mime-version; bh=dikAz6SPgPn5yKh6rLMe0iaonwV7zXsm8ItmSBcY450=; b=YYkHkFeK1AF+B0omQ1FMzbnmN5tydcq+uvmcJRCzb/rJ7dyxcChxQF3MZoExbCudFE zQMrCmWgUXWjnOk+sq+8p5QlOpki3MbXapp8frTWHaWjpft3PpYDciv/G1hfSz3KrZLW Q0aHc0MQsHU4mNIcirfyf6bnf8gnirDb+7wPfWTsmDpu2+YP8RbCinvYRjCan/vk+5K9 CZMs2IuqfDTtFSUYzg/uZ8GTBRAdTy4uVc9eNU1+cnDYmj6eNyDHk9cMdsbgzWoURORw qorxr2JewnYamwM3Oj4IqPODSm8mUec2Z6yUO1T1uaH1So9DFMscxpIl1TZeyTmCV/t/ THCQ==
- In-reply-to: <20170403112611.GA4333@fujitsu.shahaf.local2>
- List-help: <mailto:firstname.lastname@example.org>
- List-id: Zsh Users List <zsh-users.zsh.org>
- List-post: <mailto:email@example.com>
- Mailing-list: contact zsh-users-help@xxxxxxx; run by ezmlm
- References: <firstname.lastname@example.org> <170401145348.ZM30308@torch.brasslantern.com> <20170403011159.GA64116@tower.spodhuis.org> <CAH+w=7YWqmJXHbAf0p2KwDxJqOXVzu7HzCugV0NjFfVYsVGMJw@mail.gmail.com> <20170403112611.GA4333@fujitsu.shahaf.local2>
On Apr 3, 11:26am, Daniel Shahaf wrote:
} I agree that semantics of operators shouldn't depend on option
I'm not even particularly worried about semantic dependency; the gripe
here is that "setopt re_match_pcre" does not succeed (or fail) based on
the presence (or absence) of the module. Exactly how big a problem is
that? If you are relying on =~ having perl semantics, you ought to be
calling "zmodload zsh/pcre" anyway, and not just expecting setopt to do
that for you.
On the other hand if others think it's a major shortcoming that setopt
does not hard fail when the option won't actually have a useful effect,
then we should use a different paradigm than setopt here; yes it would
be possible for setopt to barf with "can't change option: rematchpcre"
but that means a module-specific special case that no other setopt has.
And now I've repeated myself at least three times so I'll stop.
} > [...] the zsh/regex module would have to become part of the default
} > static build, which might have licensing consequences.
} What would those be? zsh/regex is BSD licensed.
I don't know, and don't have time to figure it out.
Messages sorted by: