From: Mark H Weaver <mhw@netris.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: TODO list for Guile R7RS support
Date: Sat, 11 Feb 2012 15:41:34 -0500 [thread overview]
Message-ID: <87d39l5cht.fsf@netris.org> (raw)
In-Reply-To: <87k43uhegn.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 10 Feb 2012 16:53:44 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver <mhw@netris.org> skribis:
>
>> * bytevectors in core R7RS
>
> What does it mean? That bindings are available by default?
Yes.
>> * R7RS feature identifiers: r7rs, exact-closed, ratios, exact-complex,
>> ieee-float, full-unicode, windows, posix, unix, darwin, linux, bsd,
>> freebsd, solaris, i386, x86-64, ppc, sparc, jvm, clr, llvm, ilp32,
>> lp64, ilp64, big-endian, little-endian, guile, guile-2, guile-2.0
>
> I wonder how these are specified. Does a *-kfreebsd-gnu build have
> ‘freebsd’? And ‘bsd’? Do *-gnu* have ‘linux’ defined, even when Linux
> isn’t used? Does Cygwin have ‘unix’?
>
> And above all: are people going to write #ifdef __linux__ish code when
> what they mean is #ifdef __GLIBC__ or even something different?
Yes, this is a very good point, and one that should be raised with the
R7RS working group. The C library is usually far more relevant to user
code than the kernel. This strikes me as another instance of the
widespread confusion that "linux" is an operating system, when in fact
it is only a kernel. It would be a shame for this confusion to be
codified into the R7RS.
Thanks,
Mark
next prev parent reply other threads:[~2012-02-11 20:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 5:09 TODO list for Guile R7RS support Mark H Weaver
2012-02-10 15:53 ` Ludovic Courtès
2012-02-11 20:41 ` Mark H Weaver [this message]
2012-02-11 21:11 ` Ludovic Courtès
2012-02-12 3:54 ` Alex Shinn
2012-02-12 23:46 ` Ludovic Courtès
2012-02-12 23:57 ` Alex Shinn
2012-02-13 4:03 ` William ML Leslie
2012-02-13 11:50 ` Ludovic Courtès
2012-02-14 2:35 ` Alex Shinn
2012-02-16 21:05 ` Ludovic Courtès
2012-02-22 21:46 ` Andy Wingo
2012-02-22 22:06 ` Andy Wingo
2012-02-23 1:39 ` Alex Shinn
2012-02-26 22:08 ` Ludovic Courtès
2012-02-26 22:48 ` Alex Shinn
2012-02-27 16:00 ` 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=87d39l5cht.fsf@netris.org \
--to=mhw@netris.org \
--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).