all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Roel Janssen <roel@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>, "Andreas Enge" <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Using #true and #false everywhere?
Date: Wed, 21 Oct 2020 13:51:23 +0200	[thread overview]
Message-ID: <c7101efde8a3c2c2a84274749753edd39f30eaa3.camel@gnu.org> (raw)
In-Reply-To: <87pn5b7vcj.fsf@gnu.org>

On Wed, 2020-10-21 at 11:59 +0200, Ludovic Courtès wrote:
> Hi,
> 
> Andreas Enge <andreas@enge.fr> skribis:
> 
> > on the bikeshedding front: I find #true and #false confusing, since
> > everything I see on the Scheme language seems to use #t and #f.
> 
> What material are you referring to?  SICP & co.?
> 

Sorry to inject in the thread, but here's more material that uses #t
and #f:

  $ guile
  GNU Guile 3.0.4
  Copyright (C) 1995-2020 Free Software Foundation, Inc.

  Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
  This program is free software, and you are welcome to redistribute it
  under certain conditions; type `,show c' for details.

  Enter `,help' for help.
  scheme@(guile-user)> (= 1 1)
  $1 = #t
  scheme@(guile-user)> (= 1 2)
  $2 = #f

I don't remember ever being confused about #t and #f, so perhaps my
opinion doesn't matter much in this, but I'd prefer #t and #f because
it's already widespread use in Scheme.  (And with widespread I mean:
Pretty much all Scheme code I read).

I do remember being confused about the double parenthesis on "let" ;).

Kind regards,
Roel Janssen




  parent reply	other threads:[~2020-10-21 11:51 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
2020-10-21 15:52           ` Ludovic Courtès
2020-10-21 11:51         ` Roel Janssen [this message]
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=c7101efde8a3c2c2a84274749753edd39f30eaa3.camel@gnu.org \
    --to=roel@gnu.org \
    --cc=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.