RubyGems - rroonga - Versions diffs - 7.0.2-x86-mingw32 → 7.1.1-x86-mingw32 - Mend

rroonga 7.0.2-x86-mingw32 → 7.1.1-x86-mingw32

Files changed (1237) hide show

data/vendor/local/share/doc/groonga/ja/html/tutorial/query_expansion.html CHANGED Viewed

@@ -1,24 +1,22 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml" lang="ja">
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-    <title>4.11. クエリ拡張 &#8212; Groonga v7.0.1-160-gda23e59ドキュメント</title>
+    <title>4.11. クエリ拡張 &#8212; Groonga v7.1.0-73-g6d02cfaドキュメント</title>
     <link rel="stylesheet" href="../_static/groonga.css" type="text/css" />
     <link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
     <script type="text/javascript">
       var DOCUMENTATION_OPTIONS = {
         URL_ROOT:    '../',
-        VERSION:     '7.0.1-160-gda23e59',
+        VERSION:     '7.1.0-73-g6d02cfa',
         COLLAPSE_INDEX: false,
         FILE_SUFFIX: '.html',
-        HAS_SOURCE:  true
+        HAS_SOURCE:  false,
+        SOURCELINK_SUFFIX: '.txt'
       };
     </script>
     <script type="text/javascript" src="../_static/jquery.js"></script>
@@ -28,12 +26,10 @@
     <link rel="shortcut icon" href="../_static/favicon.ico"/>
     <link rel="index" title="索引" href="../genindex.html" />
     <link rel="search" title="検索" href="../search.html" />
-    <link rel="top" title="Groonga v7.0.1-160-gda23e59ドキュメント" href="../index.html" />
-    <link rel="up" title="4. チュートリアル" href="../tutorial.html" />
     <link rel="next" title="5. サーバー" href="../server.html" />
     <link rel="prev" title="4.10. マイクロブログ検索システムの作成" href="micro_blog.html" />
   </head>
-  <body role="document">
+  <body>
 <div class="header">
   <h1 class="title">
     <a id="top-link" href="../index.html">
@@ -63,7 +59,7 @@
         <li class="right" >
           <a href="micro_blog.html" title="4.10. マイクロブログ検索システムの作成"
              accesskey="P">前へ</a> |</li>
-        <li class="nav-item nav-item-0"><a href="../index.html">Groonga v7.0.1-160-gda23e59ドキュメント</a> &#187;</li>
+        <li class="nav-item nav-item-0"><a href="../index.html">Groonga v7.1.0-73-g6d02cfaドキュメント</a> &#187;</li>
           <li class="nav-item nav-item-1"><a href="../tutorial.html" accesskey="U">4. チュートリアル</a> &#187;</li>
       </ul>
     </div>
@@ -292,13 +288,6 @@ select Doc --match_columns body --query &quot;theatre&quot; --query_expander Syn
   <h4>次のトピックへ</h4>
   <p class="topless"><a href="../server.html"
                         title="次の章へ">5. サーバー</a></p>
-  <div role="note" aria-label="source link">
-    <h3>このページ</h3>
-    <ul class="this-page-menu">
-      <li><a href="../_sources/tutorial/query_expansion.txt"
-            rel="nofollow">ソースコードを表示</a></li>
-    </ul>
-   </div>
 <div id="searchbox" style="display: none" role="search">
   <h3>クイック検索</h3>
     <form class="search" action="../search.html" method="get">
@@ -325,12 +314,12 @@ select Doc --match_columns body --query &quot;theatre&quot; --query_expander Syn
         <li class="right" >
           <a href="micro_blog.html" title="4.10. マイクロブログ検索システムの作成"
              >前へ</a> |</li>
-        <li class="nav-item nav-item-0"><a href="../index.html">Groonga v7.0.1-160-gda23e59ドキュメント</a> &#187;</li>
+        <li class="nav-item nav-item-0"><a href="../index.html">Groonga v7.1.0-73-g6d02cfaドキュメント</a> &#187;</li>
           <li class="nav-item nav-item-1"><a href="../tutorial.html" >4. チュートリアル</a> &#187;</li>
       </ul>
     </div>
     <div class="footer" role="contentinfo">
-        &#169; Copyright 2009-2017, Brazil, Inc.
+        &#169; Copyright 2009-2018, Brazil, Inc.
     </div>
   </body>
 </html>

data/vendor/local/share/doc/groonga/ja/html/tutorial/search.html CHANGED Viewed

@@ -1,24 +1,22 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml" lang="ja">
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-    <title>4.4. さまざまな検索条件 &#8212; Groonga v7.0.1-160-gda23e59ドキュメント</title>
+    <title>4.4. さまざまな検索条件 &#8212; Groonga v7.1.0-73-g6d02cfaドキュメント</title>
     <link rel="stylesheet" href="../_static/groonga.css" type="text/css" />
     <link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
     <script type="text/javascript">
       var DOCUMENTATION_OPTIONS = {
         URL_ROOT:    '../',
-        VERSION:     '7.0.1-160-gda23e59',
+        VERSION:     '7.1.0-73-g6d02cfa',
         COLLAPSE_INDEX: false,
         FILE_SUFFIX: '.html',
-        HAS_SOURCE:  true
+        HAS_SOURCE:  false,
+        SOURCELINK_SUFFIX: '.txt'
       };
     </script>
     <script type="text/javascript" src="../_static/jquery.js"></script>
@@ -28,12 +26,10 @@
     <link rel="shortcut icon" href="../_static/favicon.ico"/>
     <link rel="index" title="索引" href="../genindex.html" />
     <link rel="search" title="検索" href="../search.html" />
-    <link rel="top" title="Groonga v7.0.1-160-gda23e59ドキュメント" href="../index.html" />
-    <link rel="up" title="4. チュートリアル" href="../tutorial.html" />
     <link rel="next" title="4.5. ドリルダウン" href="drilldown.html" />
     <link rel="prev" title="4.3. いろいろなデータの保存" href="data.html" />
   </head>
-  <body role="document">
+  <body>
 <div class="header">
   <h1 class="title">
     <a id="top-link" href="../index.html">
@@ -63,7 +59,7 @@
         <li class="right" >
           <a href="data.html" title="4.3. いろいろなデータの保存"
              accesskey="P">前へ</a> |</li>
-        <li class="nav-item nav-item-0"><a href="../index.html">Groonga v7.0.1-160-gda23e59ドキュメント</a> &#187;</li>
+        <li class="nav-item nav-item-0"><a href="../index.html">Groonga v7.1.0-73-g6d02cfaドキュメント</a> &#187;</li>
           <li class="nav-item nav-item-1"><a href="../tutorial.html" accesskey="U">4. チュートリアル</a> &#187;</li>
       </ul>
     </div>
@@ -209,7 +205,7 @@ select --table Site --filter &quot;_id &lt;= 2 || _id &gt;= 7&quot; --output_col
 <p><code class="docutils literal"><span class="pre">select</span></code> コマンドの <code class="docutils literal"><span class="pre">scorer</span></code> パラメータは、 全文検索を行った結果の各レコードに対して処理を行うためのパラメータです。</p>
 <p><code class="docutils literal"><span class="pre">filter</span></code> パラメータと同様に、 JavaScriptの式に似た文法で様々な条件を指定することができます。</p>
 <p>実行例:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Site --filter &quot;true&quot; --scorer &quot;_score = rand()&quot; --output_columns _id,_key,_score --sortby _score
+<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Site --filter &quot;true&quot; --scorer &quot;_score = rand()&quot; --output_columns _id,_key,_score --sort_keys _score
 # [
 #   [
 #     0,
@@ -283,7 +279,7 @@ select --table Site --filter &quot;_id &lt;= 2 || _id &gt;= 7&quot; --output_col
 #     ]
 #   ]
 # ]
-select --table Site --filter &quot;true&quot; --scorer &quot;_score = rand()&quot; --output_columns _id,_key,_score --sortby _score
+select --table Site --filter &quot;true&quot; --scorer &quot;_score = rand()&quot; --output_columns _id,_key,_score --sort_keys _score
 # [
 #   [
 #     0,
@@ -365,7 +361,7 @@ select --table Site --filter &quot;true&quot; --scorer &quot;_score = rand()&quo
 </pre></div>
 </div>
 <p>このケースでは、rand()という乱数を返す関数を用いて、全文検索のスコアを乱数で上書きしています。</p>
-<p><code class="docutils literal"><span class="pre">sortby</span></code> パラメータの条件は次のとおりです:</p>
+<p><code class="docutils literal"><span class="pre">sort_keys</span></code> パラメータの条件は次のとおりです:</p>
 <div class="highlight-none"><div class="highlight"><pre><span></span>_score
 </pre></div>
 </div>
@@ -378,14 +374,10 @@ select --table Site --filter &quot;true&quot; --scorer &quot;_score = rand()&quo
 <p>Groongaでは位置情報を保存するためのカラムの型として、TokyoGeoPoint/WGS84GeoPointの２つの型があります。前者は日本測地系、後者は世界測地系(WGS84相当)の経緯度を保存します。</p>
 <p>以下のようにして経緯度を指定します:</p>
 <ul class="simple">
-<li><p class="first">&quot;経度のミリ秒表記x緯度のミリ秒表記&quot; （例: &quot;128452975x503157902&quot;）</p>
-</li>
-<li><p class="first">&quot;経度のミリ秒表記,緯度のミリ秒表記&quot; （例: &quot;128452975,503157902&quot;）</p>
-</li>
-<li><p class="first">&quot;経度の度数表記x緯度の度数表記&quot; （例: &quot;35.6813819x139.7660839&quot;）</p>
-</li>
-<li><p class="first">&quot;経度の度数表記,緯度の度数表記&quot; （例: &quot;35.6813819,139.7660839&quot;）</p>
-</li>
+<li>&quot;経度のミリ秒表記x緯度のミリ秒表記&quot; （例: &quot;128452975x503157902&quot;）</li>
+<li>&quot;経度のミリ秒表記,緯度のミリ秒表記&quot; （例: &quot;128452975,503157902&quot;）</li>
+<li>&quot;経度の度数表記x緯度の度数表記&quot; （例: &quot;35.6813819x139.7660839&quot;）</li>
+<li>&quot;経度の度数表記,緯度の度数表記&quot; （例: &quot;35.6813819,139.7660839&quot;）</li>
 </ul>
 <p>ここでは、ためしに東京駅と新宿駅とついて、世界測地系での位置情報を保存してみましょう。東京駅は緯度が35度40分52.975秒、経度が139度45分57.902秒です。新宿駅は緯度が35度41分27.316秒、経度が139度42分0.929秒です。よって、ミリ秒表記の場合はそれぞれ&quot;128452975x503157902&quot;/&quot;128487316x502920929&quot;となります。度数表記の場合はそれぞれ&quot;35.6813819x139.7660839&quot;/&quot;35.6909211x139.7002581&quot;となります。</p>
 <p>ミリ秒表記で位置情報を登録してみましょう。</p>
@@ -478,9 +470,9 @@ select --table Site --query &quot;_id:1 OR _id:2&quot; --output_columns _key,loc
 </pre></div>
 </div>
 <p>結果から、東京駅と秋葉原駅は2054m、秋葉原駅と新宿駅は6720m離れているようです。</p>
-<p><code class="docutils literal"><span class="pre">geo_distance</span></code> 関数は、<code class="docutils literal"><span class="pre">_score</span></code> に値を設定することで、<code class="docutils literal"><span class="pre">sortby</span></code> パラメータによるソートでも用いることができます。</p>
+<p><code class="docutils literal"><span class="pre">geo_distance</span></code> 関数は、<code class="docutils literal"><span class="pre">_score</span></code> に値を設定することで、<code class="docutils literal"><span class="pre">sort_keys</span></code> パラメータによるソートでも用いることができます。</p>
 <p>実行例:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Site --query &quot;_id:1 OR _id:2&quot; --output_columns _key,location,_score --scorer &#39;_score = geo_distance(location, &quot;128515259x503187188&quot;)&#39; --sortby -_score
+<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Site --query &quot;_id:1 OR _id:2&quot; --output_columns _key,location,_score --scorer &#39;_score = geo_distance(location, &quot;128515259x503187188&quot;)&#39; --sort_keys -_score
 # [
 #   [
 #     0,
@@ -582,13 +574,6 @@ select --table Site --query &quot;_id:1 OR _id:2&quot; --output_columns _key,loc
   <h4>次のトピックへ</h4>
   <p class="topless"><a href="drilldown.html"
                         title="次の章へ">4.5. ドリルダウン</a></p>
-  <div role="note" aria-label="source link">
-    <h3>このページ</h3>
-    <ul class="this-page-menu">
-      <li><a href="../_sources/tutorial/search.txt"
-            rel="nofollow">ソースコードを表示</a></li>
-    </ul>
-   </div>
 <div id="searchbox" style="display: none" role="search">
   <h3>クイック検索</h3>
     <form class="search" action="../search.html" method="get">
@@ -615,12 +600,12 @@ select --table Site --query &quot;_id:1 OR _id:2&quot; --output_columns _key,loc
         <li class="right" >
           <a href="data.html" title="4.3. いろいろなデータの保存"
              >前へ</a> |</li>
-        <li class="nav-item nav-item-0"><a href="../index.html">Groonga v7.0.1-160-gda23e59ドキュメント</a> &#187;</li>
+        <li class="nav-item nav-item-0"><a href="../index.html">Groonga v7.1.0-73-g6d02cfaドキュメント</a> &#187;</li>
           <li class="nav-item nav-item-1"><a href="../tutorial.html" >4. チュートリアル</a> &#187;</li>
       </ul>
     </div>
     <div class="footer" role="contentinfo">
-        &#169; Copyright 2009-2017, Brazil, Inc.
+        &#169; Copyright 2009-2018, Brazil, Inc.
     </div>
   </body>
 </html>

data/vendor/local/share/doc/pcre/AUTHORS CHANGED Viewed

@@ -8,7 +8,7 @@ Email domain:     cam.ac.uk
 University of Cambridge Computing Service,
 Cambridge, England.
-Copyright (c) 1997-2016 University of Cambridge
+Copyright (c) 1997-2017 University of Cambridge
 All rights reserved
@@ -19,7 +19,7 @@ Written by:       Zoltan Herczeg
 Email local part: hzmester
 Emain domain:     freemail.hu
-Copyright(c) 2010-2016 Zoltan Herczeg
+Copyright(c) 2010-2017 Zoltan Herczeg
 All rights reserved.
@@ -30,7 +30,7 @@ Written by:       Zoltan Herczeg
 Email local part: hzmester
 Emain domain:     freemail.hu
-Copyright(c) 2009-2016 Zoltan Herczeg
+Copyright(c) 2009-2017 Zoltan Herczeg
 All rights reserved.

data/vendor/local/share/doc/pcre/ChangeLog CHANGED Viewed

@@ -4,6 +4,100 @@ ChangeLog for PCRE
 Note that the PCRE 8.xx series (PCRE1) is now in a bugfix-only state. All
 development is happening in the PCRE2 10.xx series.
+Version 8.41 05-July-2017
+-------------------------
+1.  Fixed typo in CMakeLists.txt (wrong number of arguments for
+PCRE_STATIC_RUNTIME (affects MSVC only).
+2.  Issue 1 for 8.40 below was not correctly fixed. If pcregrep in multiline
+mode with --only-matching matched several lines, it restarted scanning at the
+next line instead of moving on to the end of the matched string, which can be
+several lines after the start.
+3.  Fix a missing else in the JIT compiler reported by 'idaifish'.
+4.  A (?# style comment is now ignored between a basic quantifier and a
+following '+' or '?' (example: /X+(?#comment)?Y/.
+5.  Avoid use of a potentially overflowing buffer in pcregrep (patch by Petr
+Pisar).
+6.  Fuzzers have reported issues in pcretest. These are NOT serious (it is,
+after all, just a test program). However, to stop the reports, some easy ones
+are fixed:
+    (a) Check for values < 256 when calling isprint() in pcretest.
+    (b) Give an error for too big a number after \O.
+7.  In the 32-bit library in non-UTF mode, an attempt to find a Unicode
+property for a character with a code point greater than 0x10ffff (the Unicode
+maximum) caused a crash.
+8. The alternative matching function, pcre_dfa_exec() misbehaved if it
+encountered a character class with a possessive repeat, for example [a-f]{3}+.
+9. When pcretest called pcre_copy_substring() in 32-bit mode, it set the buffer
+length incorrectly, which could result in buffer overflow.
+10. Remove redundant line of code (accidentally left in ages ago).
+11. Applied C++ patch from Irfan Adilovic to guard 'using std::' directives
+with namespace pcrecpp (Bugzilla #2084).
+12. Remove a duplication typo in pcre_tables.c.
+13. Fix returned offsets from regexec() when REG_STARTEND is used with a
+starting offset greater than zero.
+Version 8.40 11-January-2017
+----------------------------
+1.  Using -o with -M in pcregrep could cause unnecessary repeated output when
+    the match extended over a line boundary.
+2.  Applied Chris Wilson's second patch (Bugzilla #1681) to CMakeLists.txt for
+    MSVC static compilation, putting the first patch under a new option.
+3.  Fix register overwite in JIT when SSE2 acceleration is enabled.
+4.  Ignore "show all captures" (/=) for DFA matching.
+5.  Fix JIT unaligned accesses on x86. Patch by Marc Mutz.
+6.  In any wide-character mode (8-bit UTF or any 16-bit or 32-bit mode),
+    without PCRE_UCP set, a negative character type such as \D in a positive
+    class should cause all characters greater than 255 to match, whatever else
+    is in the class. There was a bug that caused this not to happen if a
+    Unicode property item was added to such a class, for example [\D\P{Nd}] or
+    [\W\pL].
+7.  When pcretest was outputing information from a callout, the caret indicator
+    for the current position in the subject line was incorrect if it was after
+    an escape sequence for a character whose code point was greater than
+    \x{ff}.
+8.  A pattern such as (?<RA>abc)(?(R)xyz) was incorrectly compiled such that
+    the conditional was interpreted as a reference to capturing group 1 instead
+    of a test for recursion. Any group whose name began with R was
+    misinterpreted in this way. (The reference interpretation should only
+    happen if the group's name is precisely "R".)
+9.  A number of bugs have been mended relating to match start-up optimizations
+    when the first thing in a pattern is a positive lookahead. These all
+    applied only when PCRE_NO_START_OPTIMIZE was *not* set:
+    (a) A pattern such as (?=.*X)X$ was incorrectly optimized as if it needed
+        both an initial 'X' and a following 'X'.
+    (b) Some patterns starting with an assertion that started with .* were
+        incorrectly optimized as having to match at the start of the subject or
+        after a newline. There are cases where this is not true, for example,
+        (?=.*[A-Z])(?=.{8,16})(?!.*[\s]) matches after the start in lines that
+        start with spaces. Starting .* in an assertion is no longer taken as an
+        indication of matching at the start (or after a newline).
 Version 8.39 14-June-2016
 -------------------------

data/vendor/local/share/doc/pcre/LICENCE CHANGED Viewed

@@ -25,7 +25,7 @@ Email domain:     cam.ac.uk
 University of Cambridge Computing Service,
 Cambridge, England.
-Copyright (c) 1997-2016 University of Cambridge
+Copyright (c) 1997-2017 University of Cambridge
 All rights reserved.
@@ -36,7 +36,7 @@ Written by:       Zoltan Herczeg
 Email local part: hzmester
 Emain domain:     freemail.hu
-Copyright(c) 2010-2016 Zoltan Herczeg
+Copyright(c) 2010-2017 Zoltan Herczeg
 All rights reserved.
@@ -47,7 +47,7 @@ Written by:       Zoltan Herczeg
 Email local part: hzmester
 Emain domain:     freemail.hu
-Copyright(c) 2009-2016 Zoltan Herczeg
+Copyright(c) 2009-2017 Zoltan Herczeg
 All rights reserved.

data/vendor/local/share/doc/pcre/NEWS CHANGED Viewed

@@ -1,6 +1,18 @@
 News about PCRE releases
 ------------------------
+Release 8.41 13-June-2017
+-------------------------
+This is a bug-fix release.
+Release 8.40 11-January-2017
+----------------------------
+This is a bug-fix release.
 Release 8.39 14-June-2016
 -------------------------

data/vendor/local/share/doc/pcre/html/pcrecompat.html CHANGED Viewed

@@ -128,7 +128,7 @@ the pattern /^(a(b)?)+$/ in Perl leaves $2 unset, but in PCRE it is set to "b".
 14. PCRE's handling of duplicate subpattern numbers and duplicate subpattern
 names is not as general as Perl's. This is a consequence of the fact the PCRE
 works internally just with numbers, using an external table to translate
-between numbers and names. In particular, a pattern such as (?|(?&#60;a&#62;A)|(?&#60;b)B),
+between numbers and names. In particular, a pattern such as (?|(?&#60;a&#62;A)|(?&#60;b&#62;B),
 where the two capturing parentheses have the same number but different names,
 is not supported, and causes an error at compile time. If it were allowed, it
 would not be possible to distinguish which parentheses matched, because both

data/vendor/local/share/doc/pcre/html/pcrejit.html CHANGED Viewed

@@ -79,9 +79,12 @@ API that is JIT-specific.
 </P>
 <P>
 If your program may sometimes be linked with versions of PCRE that are older
-than 8.20, but you want to use JIT when it is available, you can test
-the values of PCRE_MAJOR and PCRE_MINOR, or the existence of a JIT macro such
-as PCRE_CONFIG_JIT, for compile-time control of your code.
+than 8.20, but you want to use JIT when it is available, you can test the
+values of PCRE_MAJOR and PCRE_MINOR, or the existence of a JIT macro such as
+PCRE_CONFIG_JIT, for compile-time control of your code. Also beware that the
+<b>pcre_jit_exec()</b> function was not available at all before 8.32,
+and may not be available at all if PCRE isn't compiled with
+--enable-jit. See the "JIT FAST PATH API" section below for details.
 </P>
 <br><a name="SEC4" href="#TOC1">SIMPLE USE OF JIT</a><br>
 <P>
@@ -119,6 +122,20 @@ when you call <b>pcre_study()</b>:
   PCRE_STUDY_JIT_PARTIAL_HARD_COMPILE
   PCRE_STUDY_JIT_PARTIAL_SOFT_COMPILE
 </pre>
+If using <b>pcre_jit_exec()</b> and supporting a pre-8.32 version of
+PCRE, you can insert:
+<pre>
+   #if PCRE_MAJOR &#62;= 8 && PCRE_MINOR &#62;= 32
+   pcre_jit_exec(...);
+   #else
+   pcre_exec(...)
+   #endif
+</pre>
+but as described in the "JIT FAST PATH API" section below this assumes
+version 8.32 and later are compiled with --enable-jit, which may
+break.
+<br>
+<br>
 The JIT compiler generates different optimized code for each of the three
 modes (normal, soft partial, hard partial). When <b>pcre_exec()</b> is called,
 the appropriate code is run if it is available. Otherwise, the pattern is
@@ -428,6 +445,36 @@ fast path, and if invalid data is passed, the result is undefined.
 Bypassing the sanity checks and the <b>pcre_exec()</b> wrapping can give
 speedups of more than 10%.
 </P>
+<P>
+Note that the <b>pcre_jit_exec()</b> function is not available in versions of
+PCRE before 8.32 (released in November 2012). If you need to support versions
+that old you must either use the slower <b>pcre_exec()</b>, or switch between
+the two codepaths by checking the values of PCRE_MAJOR and PCRE_MINOR.
+</P>
+<P>
+Due to an unfortunate implementation oversight, even in versions 8.32
+and later there will be no <b>pcre_jit_exec()</b> stub function defined
+when PCRE is compiled with --disable-jit, which is the default, and
+there's no way to detect whether PCRE was compiled with --enable-jit
+via a macro.
+</P>
+<P>
+If you need to support versions older than 8.32, or versions that may
+not build with --enable-jit, you must either use the slower
+<b>pcre_exec()</b>, or switch between the two codepaths by checking the
+values of PCRE_MAJOR and PCRE_MINOR.
+</P>
+<P>
+Switching between the two by checking the version assumes that all the
+versions being targeted are built with --enable-jit. To also support
+builds that may use --disable-jit either <b>pcre_exec()</b> must be
+used, or a compile-time check for JIT via <b>pcre_config()</b> (which
+assumes the runtime environment will be the same), or as the Git
+project decided to do, simply assume that <b>pcre_jit_exec()</b> is
+present in 8.32 or later unless a compile-time flag is provided, see
+the "grep: un-break building with PCRE &#62;= 8.32 without --enable-jit"
+commit in git.git for an example of that.
+</P>
 <br><a name="SEC12" href="#TOC1">SEE ALSO</a><br>
 <P>
 <b>pcreapi</b>(3)
@@ -443,9 +490,9 @@ Cambridge CB2 3QH, England.
 </P>
 <br><a name="SEC14" href="#TOC1">REVISION</a><br>
 <P>
-Last updated: 17 March 2013
+Last updated: 05 July 2017
 <br>
-Copyright &copy; 1997-2013 University of Cambridge.
+Copyright &copy; 1997-2017 University of Cambridge.
 <br>
 <p>
 Return to the <a href="index.html">PCRE index page</a>.