unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Drew Adams <drew.adams@oracle.com>
Cc: 26564@debbugs.gnu.org, Kaushal Modi <kaushal.modi@gmail.com>
Subject: bug#26564: Document that only functions and not variables can end with "-p"
Date: Wed, 19 Apr 2017 23:44:12 +0200	[thread overview]
Message-ID: <87h91kdqdv.fsf@drachen> (raw)
In-Reply-To: <fc6d6749-73a0-4dd8-bf28-428bdaa21d32@default> (Drew Adams's message of "Wed, 19 Apr 2017 10:26:53 -0700 (PDT)")

Drew Adams <drew.adams@oracle.com> writes:

> 3. Is there a proposal for a _different_ naming convention
> for Boolean variables?  I'd argue that we should have some
> such a naming convention.  And I'd argue that it should be
> different for options and non-option variables.

That's a good point indeed.

An alternative to "-p" would be "is-", like `foo-is-negative'.

Not using -p would also have an advantage: you could distinguish boolean
variables from variables bound to a predicate function.


Michael.





  reply	other threads:[~2017-04-19 21:44 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
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 [this message]
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=87h91kdqdv.fsf@drachen \
    --to=michael_heerdegen@web.de \
    --cc=26564@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=kaushal.modi@gmail.com \
    /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).