From: "Thompson, David" <dthompson2@worcester.edu>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: ?-suffix for booleans... good-idea? or bad-idea?
Date: Tue, 25 Apr 2017 20:23:23 -0400 [thread overview]
Message-ID: <CAJ=RwfYy=3L2LCcUV4jaeg9OKj0AE3esW2cjXb619dsubLHOWA@mail.gmail.com> (raw)
In-Reply-To: <878tmpoi3x.fsf@dustycloud.org>
Hey,
On Mon, Apr 24, 2017 at 1:01 PM, Christopher Allan Webber
<cwebber@dustycloud.org> wrote:
>
> What do people think? I'm struggling with deciding what's the right
> thing for my own code, but leaning towards "we shouldn't use the ?
> suffix for just boolean values".
My convention is that anything that evaluates to either #t or #f has a
'?' at the end. Thus both predicates and flag variables are named
like this. Using 'is-' or something like that is just how languages
that don't allow punctuation in symbols workaround the limitation.
Ruby is particularly annoying because while a method name can have a
question mark at the end, a variable name cannot.
tl;dr - Good idea!
- Dave
next prev parent reply other threads:[~2017-04-26 0:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 17:01 ?-suffix for booleans... good-idea? or bad-idea? Christopher Allan Webber
2017-04-25 3:43 ` Alex Vong
2017-04-25 15:50 ` Jan Wedekind
2017-04-25 16:21 ` Paul
2017-04-26 15:25 ` Alex Kost
2017-04-25 18:08 ` Neil Jerram
2017-04-25 16:53 ` Panicz Maciej Godek
2017-04-26 0:23 ` Thompson, David [this message]
2017-04-27 10:39 ` Jan Nieuwenhuizen
2017-04-27 10:53 ` Panicz Maciej Godek
2017-04-27 12:07 ` Marko Rauhamaa
2017-05-05 17:26 ` Vladimir Zhbanov
2017-05-05 19:44 ` szgyg
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ=RwfYy=3L2LCcUV4jaeg9OKj0AE3esW2cjXb619dsubLHOWA@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=cwebber@dustycloud.org \
--cc=guile-user@gnu.org \
/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.
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).