[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] master f113ae5: ; Minor copyedits in a recent ELisp manual
From: |
Eli Zaretskii |
Subject: |
[Emacs-diffs] master f113ae5: ; Minor copyedits in a recent ELisp manual change. |
Date: |
Sun, 13 Oct 2019 04:01:23 -0400 (EDT) |
branch: master
commit f113ae59222dbb0961a34c1e0913cf0f3104a567
Author: Eli Zaretskii <address@hidden>
Commit: Eli Zaretskii <address@hidden>
; Minor copyedits in a recent ELisp manual change.
* doc/lispref/tips.texi (Coding Conventions): Make the
guideline against '-p' in variable names less mandatory and
more constructive.
---
doc/lispref/tips.texi | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/doc/lispref/tips.texi b/doc/lispref/tips.texi
index 9f64209..eb03816 100644
--- a/doc/lispref/tips.texi
+++ b/doc/lispref/tips.texi
@@ -158,9 +158,10 @@ If the purpose of a function is to tell you whether a
certain
condition is true or false, give the function a name that ends in
@samp{p} (which stands for ``predicate''). 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}. This predicate
-suffix should not be used in variable names (i.e., you should name a
-variable @code{foo-feature} instead of @code{foo-feature-p}).
+Examples are @code{framep} and @code{frame-live-p}. We recommend to
+avoid using this @code{-p} suffix in boolean variable names, unless
+the variable is bound to a predicate function; instead, use a
+@code{-flag} suffix or names like @code{is-foo}.
@item
If the purpose of a variable is to store a single function, give it a
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Emacs-diffs] master f113ae5: ; Minor copyedits in a recent ELisp manual change.,
Eli Zaretskii <=