From: "Diogo F. S. Ramos" <dfsr@riseup.net>
To: guile-devel@gnu.org
Subject: [PATCH 2/2] Add reference to the lack of "non-greedy" variants
Date: Wed, 26 Mar 2014 00:27:21 -0300 [thread overview]
Message-ID: <1395804441-29214-2-git-send-email-dfsr@riseup.net> (raw)
In-Reply-To: <1395804441-29214-1-git-send-email-dfsr@riseup.net>
While describing special characters, remind the reader that
"non-greedy" variants are not supported. They might not be familiar
with POSIX extended regular expression and expect it to work.
* doc/ref/api-regex.texi: Add "non-greedy" observation
---
doc/ref/api-regex.texi | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/doc/ref/api-regex.texi b/doc/ref/api-regex.texi
index f95eddb..b14c2b3 100644
--- a/doc/ref/api-regex.texi
+++ b/doc/ref/api-regex.texi
@@ -38,10 +38,11 @@ regex))}.
@node Regexp Functions
@subsection Regexp Functions
-By default, Guile supports POSIX extended regular expressions.
-That means that the characters @samp{(}, @samp{)}, @samp{+} and
-@samp{?} are special, and must be escaped if you wish to match the
-literal characters.
+By default, Guile supports POSIX extended regular expressions. That
+means that the characters @samp{(}, @samp{)}, @samp{+} and @samp{?} are
+special, and must be escaped if you wish to match the literal characters
+and there is no support for ``non-greedy'' variants of @samp{*},
+@samp{+} or @samp{?}.
This regular expression interface was modeled after that
implemented by SCSH, the Scheme Shell. It is intended to be
--
1.9.1
next prev parent reply other threads:[~2014-03-26 3:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 3:27 [PATCH 1/2] Remove link to Emacs' regexp syntax Diogo F. S. Ramos
2014-03-26 3:27 ` Diogo F. S. Ramos [this message]
2014-03-26 21:08 ` [PATCH 2/2] Add reference to the lack of "non-greedy" variants Taylan Ulrich Bayırlı/Kammer
2014-03-27 3:46 ` Diogo F. S. Ramos
2014-03-28 19:25 ` Taylan Ulrich Bayırlı/Kammer
2014-04-15 11:38 ` Diogo F. S. Ramos
2016-06-19 15:41 ` Andy Wingo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1395804441-29214-2-git-send-email-dfsr@riseup.net \
--to=dfsr@riseup.net \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).