From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>,
Kaushal Modi <kaushal.modi@gmail.com>
Cc: 26564@debbugs.gnu.org
Subject: bug#26564: Document that only functions and not variables can end with "-p"
Date: Wed, 19 Apr 2017 15:04:59 -0700 (PDT) [thread overview]
Message-ID: <dc474beb-b2e2-4d22-b695-038187c1874d@default> (raw)
In-Reply-To: <87d1c8dq5f.fsf@drachen>
> > -Examples are @code{framep} and @code{frame-live-p}.
> > +Examples are @code{framep} and @code{frame-live-p}. This predicate
> > +suffix should not be used in variable names (i.e., you might name a
> > +variable @code{foo-feature} instead of @code{foo-feature-p}).
>
> I think we should not discourage naming variables bound to a predicate
> "-p". I guess you only mean "boolean variables" here?
I _would_ discourage that.
And I'd promote the practice of naming variables expected to
be bound to a Boolean _value_ with suffix `-p'.
Just as a predicate _returns_ a Boolean value, so does a
Boolean-valued variable.
A variable whose value is a _predicate_ I'd name something
like `foo-predicate' or `foo-pred' or even `foo-function'
(the last one following the current convention).
next prev parent reply other threads:[~2017-04-19 22:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 15:47 bug#26564: Document that only functions and not variables can end with "-p" Kaushal Modi
2017-04-19 16:08 ` Eli Zaretskii
2017-04-19 16:22 ` Kaushal Modi
2017-04-19 21:49 ` Michael Heerdegen
2017-04-19 22:04 ` Drew Adams [this message]
2017-04-19 22:18 ` Michael Heerdegen
2019-10-12 20:27 ` Lars Ingebrigtsen
2019-10-12 20:47 ` Kaushal Modi
2019-10-12 23:18 ` Drew Adams
2019-10-14 1:50 ` Richard Stallman
2019-10-14 2:22 ` Drew Adams
2019-10-14 7:24 ` Eli Zaretskii
2019-10-14 7:21 ` Eli Zaretskii
2017-04-19 17:26 ` Drew Adams
2017-04-19 21:44 ` Michael Heerdegen
2017-04-19 22:01 ` Drew Adams
2017-04-19 22:23 ` Michael Heerdegen
2017-04-19 22:28 ` Drew Adams
2017-04-20 1:42 ` Drew Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dc474beb-b2e2-4d22-b695-038187c1874d@default \
--to=drew.adams@oracle.com \
--cc=26564@debbugs.gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=michael_heerdegen@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).