From a5c5b6939af037a610f8b672f1c99f274489652c Mon Sep 17 00:00:00 2001
From: Sudarshan S Chawathe <chaw@eip10.org>
Date: Mon, 5 Dec 2016 16:06:11 -0500
Subject: [PATCH] In documentation of sre->string, 'POSIX' changed to 'PCRE'
 because I believe PCRE syntax is what is used in its result.  Also, in code
 for sre->string, there was a redundant (pair? (cddr x)) test which I updated
 to (pair? (cdr x)) which seems to make more sense there.

---
 irregex-utils.scm | 2 +-
 irregex.doc       | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/irregex-utils.scm b/irregex-utils.scm
index 8332791..a2195a9 100644
--- a/irregex-utils.scm
+++ b/irregex-utils.scm
@@ -89,7 +89,7 @@
         (case (car x)
           ((: seq)
            (cond
-            ((and (pair? (cddr x)) (pair? (cddr x)) (not (eq? x obj)))
+            ((and (pair? (cdr x)) (pair? (cddr x)) (not (eq? x obj)))
              (display "(?:" out) (for-each lp (cdr x)) (display ")" out))
             (else (for-each lp (cdr x)))))
           ((submatch)
diff --git a/irregex.doc b/irregex.doc
index 11f284a..6093172 100644
--- a/irregex.doc
+++ b/irregex.doc
@@ -781,7 +781,7 @@ doesn't help when irregex is able to build a DFA.
 
 \subsubsection*{(sre->string <sre>)}
 
-Convert an SRE to a POSIX-style regular expression string, if
+Convert an SRE to a PCRE-style regular expression string, if
 possible.
 
 \section{Roadmap}