From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Using #true and #false everywhere?
Date: Wed, 21 Oct 2020 13:21:34 +0200 [thread overview]
Message-ID: <20201021112134.GA4681@jurong> (raw)
In-Reply-To: <87pn5b7vcj.fsf@gnu.org>
On Wed, Oct 21, 2020 at 11:59:40AM +0200, Ludovic Courtès wrote:
> What material are you referring to? SICP & co.?
I simply used my favourite search engine with something such as
scheme language boolean
In my case the first link is to the racket manual:
https://docs.racket-lang.org/reference/booleans.html
Or this:
https://courses.cs.washington.edu/courses/cse341/02sp/scheme/basics.html
Or the Wikipedia entry:
https://en.wikipedia.org/wiki/Scheme_%28programming_language%29
Any kind of search quickly reveals that booleans in Scheme are coded
using #t and #f; whereas to find #true and #false, my impression is that
one already needs to know that these are possibilities. I find their use
more confusing than helpful.
Now if we drop the #t from phases as discussed in the present thread,
that would be even better. I have never been convinced by phases that
always return #t and never #f; what is the point of a return value
if it is not really checked?
Andreas
next prev parent reply other threads:[~2020-10-21 11:22 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 10:38 Using #true and #false everywhere? Ludovic Courtès
2020-10-16 13:19 ` Maxim Cournoyer
2020-10-16 13:36 ` Tobias Geerinckx-Rice
2020-10-18 1:36 ` Maxim Cournoyer
2020-10-18 2:22 ` Bengt Richter
2020-10-19 20:45 ` zimoun
2020-10-21 9:56 ` Ludovic Courtès
2020-10-20 9:57 ` Andreas Enge
2020-10-21 9:59 ` Ludovic Courtès
2020-10-21 11:21 ` Andreas Enge [this message]
2020-10-21 15:52 ` Ludovic Courtès
2020-10-21 11:51 ` Roel Janssen
2020-10-16 16:24 ` Vagrant Cascadian
2020-10-16 23:45 ` Danny Milosavljevic
2020-10-20 10:32 ` Andreas Enge
2020-10-20 11:10 ` Ricardo Wurmus
2020-10-20 12:02 ` zimoun
2020-10-20 12:59 ` Tobias Geerinckx-Rice
2020-10-20 13:11 ` zimoun
2020-10-20 13:32 ` Tobias Geerinckx-Rice
2020-10-20 14:26 ` zimoun
2020-10-20 15:48 ` Taylan Kammer
2020-10-21 1:25 ` Mark H Weaver
2020-10-21 6:18 ` Ricardo Wurmus
2020-10-21 10:04 ` Ludovic Courtès
2020-10-20 12:45 ` zimoun
2020-10-20 12:55 ` Andreas Enge
2020-10-21 10:20 ` Ludovic Courtès
2020-10-24 18:29 ` Robin Templeton
-- strict thread matches above, loose matches on Subject: below --
2020-10-16 22:06 Miguel Ángel Arruga Vivas
2020-10-17 0:25 ` jbranso
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201021112134.GA4681@jurong \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=ludo@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.