From: Frank Terbeck <ft@bewatermyfriend.org>
To: John Cowan <cowan@ccil.org>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: SRFI-151 (Bitwise Operations) Implementation
Date: Thu, 09 Jan 2020 19:26:56 +0100 [thread overview]
Message-ID: <87h81432q7.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <CAD2gp_Q9vMYqohrfAu_SK+_AS=9zBBcw3psFPX0j0_NFpaQo2Q@mail.gmail.com> (John Cowan's message of "Thu, 9 Jan 2020 12:50:37 -0500")
John Cowan wrote:
[...]
> The reason bitwise-nand and friends have only two arguments (and this comes
> from Olin's original) is that they aren't associative: it's ambiguous
> whether (bitwise-nand a b c) means (bitwise-nand (bitwise-nand a b) c) or
> (bitwise-nand a (bitwise-nand b c)), and these are *not* equivalent.
> Rather than choosing one of these arbitrarily, users have to say what they
> mean.
Well, how about that. :)
That is a great argument. I'll make those two binary then, as the spec
suggests. Thanks!
Regards, Frank
--
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
-- RFC 1925
next prev parent reply other threads:[~2020-01-09 18:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 4:28 SRFI-151 (Bitwise Operations) Implementation Frank Terbeck
2020-01-09 6:50 ` Zelphir Kaltstahl
2020-01-09 7:15 ` Linus Björnstam
2020-01-09 9:10 ` Frank Terbeck
2020-01-09 12:13 ` Linus Björnstam
2020-01-09 12:52 ` Frank Terbeck
2020-01-09 17:50 ` John Cowan
2020-01-09 18:26 ` Frank Terbeck [this message]
2020-01-09 20:45 ` Linus Björnstam
2020-01-10 5:15 ` Frank Terbeck
2020-01-10 6:59 ` Linus Björnstam
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=87h81432q7.fsf@ft.bewatermyfriend.org \
--to=ft@bewatermyfriend.org \
--cc=cowan@ccil.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).