From 8f39c96dec86bb2a5c57b12cf73f6fc7480f9a4c Mon Sep 17 00:00:00 2001 From: Stefan Monnier Date: Fri, 30 May 2008 14:55:07 +0000 Subject: [PATCH] (Coding Conventions): Do not encourage the use of "-flag" variable names. --- doc/lispref/ChangeLog | 5 +++++ doc/lispref/tips.texi | 4 ---- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog index 308cb386aa6..36aa760ee4c 100644 --- a/doc/lispref/ChangeLog +++ b/doc/lispref/ChangeLog @@ -1,3 +1,8 @@ +2008-05-30 Stefan Monnier + + * tips.texi (Coding Conventions): Do not encourage the use of "-flag" + variable names. + 2008-05-03 Eric S. Raymond * keymaps.texi: Clarify that (current-local-map) and diff --git a/doc/lispref/tips.texi b/doc/lispref/tips.texi index e219a1e3d49..ef0fb8ac1ff 100644 --- a/doc/lispref/tips.texi +++ b/doc/lispref/tips.texi @@ -138,10 +138,6 @@ 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 to store a list of functions (i.e., the variable is a hook), please -- 2.11.4.GIT