From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Implement SRFI-111 Boxes
Date: Mon, 24 Mar 2014 23:23:33 +0100 [thread overview]
Message-ID: <87k3bjtevu.fsf@pobox.com> (raw)
In-Reply-To: <874n4tlka7.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 24 Jan 2014 11:57:20 +0100")
A late reply, but at least the year is right :)
On Fri 24 Jan 2014 11:57, ludo@gnu.org (Ludovic Courtès) writes:
> taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:
>
>> Has it been considered to coalesce the box type with Guile's "variable"
>> type? I can see two concrete differences:
>>
>> * External representation (*not* specified by SRFI-111)
>>
>> * Variables can be "unbound" (empty), boxes can't
>>
>> So we could get away with making the box API consist of aliases to a
>> subset of the variable API and still conform to SRFI-111.
>
> Even though both types are box-like, they represent conceptually
> different things, so I think it’s better to keep them disjoint.
Why do you think so? To me, Guile's variables are boxes, and the
ability to make a variable unbound is a Guile extension.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2014-03-24 22:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 5:56 [PATCH] Implement SRFI-111 Boxes Mark H Weaver
2014-01-24 9:39 ` Taylan Ulrich Bayırlı/Kammer
2014-01-24 10:57 ` Ludovic Courtès
2014-03-24 22:23 ` Andy Wingo [this message]
2014-03-25 17:01 ` Ludovic Courtès
2014-03-25 19:37 ` Andy Wingo
2014-03-25 20:21 ` Ludovic Courtès
2014-03-25 20:31 ` Andy Wingo
2014-03-25 21:18 ` Ludovic Courtès
2014-01-24 10:55 ` Ludovic Courtès
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=87k3bjtevu.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-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.
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).