(Coding Conventions): Do not encourage the use of "-flag" variable names.

diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog
index 308cb386aa692d1bc990a1a0f346e59ac821d15d..36aa760ee4ce0f8fa26d2047cf64915121d9e199 100644 (file)
--- a/doc/lispref/ChangeLog
+++ b/doc/lispref/ChangeLog
@@ -1,3 +1,8 @@
+2008-05-30  Stefan Monnier  <monnier@iro.umontreal.ca>
+
+       * tips.texi (Coding Conventions): Do not encourage the use of "-flag"
+       variable names.
+
 2008-05-03  Eric S. Raymond  <esr@golux>
 
        * keymaps.texi: Clarify that (current-local-map) and

diff --git a/doc/lispref/tips.texi b/doc/lispref/tips.texi
index e219a1e3d49374d98e3b858ba27d64525dfcbba4..ef0fb8ac1ffaf64dd8cf9f8154f4cc91ac591397 100644 (file)
--- a/doc/lispref/tips.texi
+++ b/doc/lispref/tips.texi
@@ -137,10 +137,6 @@ is true or false, give the function a name that ends in @samp{p}.  If
 the name is one word, add just @samp{p}; if the name is multiple words,
 add @samp{-p}.  Examples are @code{framep} and @code{frame-live-p}.
 
-@item
-If a user option variable records a true-or-false condition, give it a
-name that ends in @samp{-flag}.
-
 @item
 If the purpose of a variable is to store a single function, give it a
 name that ends in @samp{-function}.  If the purpose of a variable is