aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEli Zaretskii2006-05-19 19:47:14 +0000
committerEli Zaretskii2006-05-19 19:47:14 +0000
commit5345f90dfa6444f1dd5428492d0133db97baec75 (patch)
treed31d38fcafa46c8d8d99d0ac6b8e81dbb7c48cb1
parent892eb2370135a8c5985ffe06d3f22fb334381965 (diff)
downloademacs-5345f90dfa6444f1dd5428492d0133db97baec75.tar.gz
emacs-5345f90dfa6444f1dd5428492d0133db97baec75.zip
(Simple Match Data): Warn about match data being set anew by every search.
-rw-r--r--lispref/searching.texi6
1 files changed, 6 insertions, 0 deletions
diff --git a/lispref/searching.texi b/lispref/searching.texi
index 505122fdd16..e93cee42a3b 100644
--- a/lispref/searching.texi
+++ b/lispref/searching.texi
@@ -1264,6 +1264,12 @@ subexpression is numbered 1, the second 2, and so on. Only regular
1264expressions can have subexpressions---after a simple string search, the 1264expressions can have subexpressions---after a simple string search, the
1265only information available is about the entire match. 1265only information available is about the entire match.
1266 1266
1267 Every successful search sets the match data. Therefore, you should
1268query the match data immediately after searching, before calling any
1269other function that might perform another search. Alternatively, you
1270may save and restore the match data (@pxref{Saving Match Data}) around
1271the call to functions that could perform another search.
1272
1267 A search which fails may or may not alter the match data. In the 1273 A search which fails may or may not alter the match data. In the
1268past, a failing search did not do this, but we may change it in the 1274past, a failing search did not do this, but we may change it in the
1269future. So don't try to rely on the value of the match data after 1275future. So don't try to rely on the value of the match data after