# HG changeset patch
# User Richard M. Stallman <rms@gnu.org>
# Date 1045337260 0
# Node ID 4556482b5d224a0f33b4385f00f0ebf097e587a0
# Parent  6a37bab3279193dd50de38fcc4664d2754f35940
Clarify that match data is unpredictable after failing searches.

diff -r 6a37bab32791 -r 4556482b5d22 lispref/searching.texi
--- a/lispref/searching.texi	Sat Feb 15 19:26:25 2003 +0000
+++ b/lispref/searching.texi	Sat Feb 15 19:27:40 2003 +0000
@@ -1255,7 +1255,7 @@
 @subsection Simple Match Data Access
 
   This section explains how to use the match data to find out what was
-matched by the last search or match operation.
+matched by the last search or match operation, if it succeeded.
 
   You can ask about the entire matching text, or about a particular
 parenthetical subexpression of a regular expression.  The @var{count}
@@ -1273,7 +1273,8 @@
 
   A search which fails may or may not alter the match data.  In the
 past, a failing search did not do this, but we may change it in the
-future.
+future.  So don't try to rely on the value of the match data after
+a failing search.
 
 @defun match-string count &optional in-string
 This function returns, as a string, the text matched in the last search