From 89618fe37d0c6568b1b42e237057278e686005d6 Mon Sep 17 00:00:00 2001 From: Nuri Jung Date: Tue, 7 Jul 2020 13:26:53 +0000 Subject: github #58: docs: Note that the zsh/regex syntax is platform-dependent. --- ChangeLog | 5 +++++ Doc/Zsh/mod_regex.yo | 12 ++++++++++++ 2 files changed, 17 insertions(+) diff --git a/ChangeLog b/ChangeLog index 0cf55eff6..ae583fd05 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2020-07-07 Nuri Jung + + * github #58: Doc/Zsh/mod_regex.yo: docs: Note that the zsh/regex + syntax is platform-dependent. + 2020-07-06 Pete Moore * 46194: Doc/Zsh/metafaq.yo: docs: metafaq: Remove spurious diff --git a/Doc/Zsh/mod_regex.yo b/Doc/Zsh/mod_regex.yo index f20451664..40ee92785 100644 --- a/Doc/Zsh/mod_regex.yo +++ b/Doc/Zsh/mod_regex.yo @@ -26,5 +26,17 @@ tt(-regex-match) operator. If tt(BASH_REMATCH) is set, then the array tt(BASH_REMATCH) will be set instead of tt(MATCH) and tt(match). + +Note that the tt(zsh/regex) module logic relies on the host system. The +same var(expr) and var(regex) pair could produce different results on different +platforms if a var(regex) with non-standard syntax is given. + +For example, no syntax for matching a word boundary is defined in the POSIX +extended regular expression standard. GNU tt(libc) and BSD tt(libc) both provide +such syntaxes as extensions (tt(\b) and tt([[:<:]])/tt([[:>:]]) respectively), +but neither of these syntaxes is supported by both of these implementations. + +Refer to the manref(regcomp)(3) and manref(re_format)(7) manual pages on your +system for locally-supported syntax. ) enditem() -- cgit 1.4.1