From: Neil Jerram <neil@ossau.uklinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: bytevector docs -> compound data types?
Date: Thu, 25 Jun 2009 23:42:34 +0100 [thread overview]
Message-ID: <873a9oue91.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <m3hby4m4i5.fsf@pobox.com> (Andy Wingo's message of "Thu\, 25 Jun 2009 22\:40\:18 +0200")
Andy Wingo <wingo@pobox.com> writes:
> Another option of course is to not classify data types by "simple" or
> "compound", but some division is necessary.
>
> Perhaps our master wordsmith Baron von Jerram has a perspective :)
Huh? Where did that `Baron' come from?
But anyway... I don't have a strong opinion here, but
- I think that bytevectors go with other kinds of vectors more closely
than they go with strings
- I think we could benefit from discarding the Simple vs Compound
division - i.e. combine everything into a single `Data Types'
section. `Pairs' could be much nearer the top of the combined list
than it is now.
Regards,
Neil
prev parent reply other threads:[~2009-06-25 22:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 17:48 bytevector docs -> compound data types? Andy Wingo
2009-06-24 22:39 ` Ludovic Courtès
2009-06-25 20:40 ` Andy Wingo
2009-06-25 22:42 ` Neil Jerram [this message]
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=873a9oue91.fsf@arudy.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=wingo@pobox.com \
/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).