From: Andy Wingo <wingo@pobox.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: guile-users@gnu.org, guile-devel@gnu.org
Subject: Re: c99 support
Date: Sat, 23 Jun 2018 22:07:24 +0200 [thread overview]
Message-ID: <874lht4683.fsf@pobox.com> (raw)
In-Reply-To: <83po0htihm.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 23 Jun 2018 22:23:17 +0300")
On Sat 23 Jun 2018 21:23, Eli Zaretskii <eliz@gnu.org> writes:
>> From: Andy Wingo <wingo@pobox.com>
>> Date: Sat, 23 Jun 2018 21:11:29 +0200
>> Cc: guile-devel@gnu.org
>>
>> Is there anyone who compiles Guile with a compiler that does not support
>> C99? If so, please give platform and compiler.
>
> You mean C99 compiler or C99 C run-time library? Or both?
>
> MS-Windows (MinGW) doesn't have a C99 compliant C library, although
> quite a few of what's needed is present.
Hard to say :) I think my questions are limited to, in decreasing order
of importance:
* Is there any system that we target that doesn't have C99 stdint.h
and stddef.h ?
* Is there any system that we target that doesn't support C99 inline
functions?
* C99 mixed decls and statements?
* C99 one-line comments (// foo) ?
* C99 compound literals? ((struct x) { 1, 2 }) ?
* stdbool.h
I want to use C99 inside Guile, and I want to eventually replace
scm_t_uint8 with uint8_t.
I assume MinGW uses GCC. What version? I see that the version 6 series
is available on mingw.org.
Andy
next prev parent reply other threads:[~2018-06-23 20:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-23 19:11 c99 support Andy Wingo
2018-06-23 19:23 ` Eli Zaretskii
2018-06-23 20:07 ` Andy Wingo [this message]
2018-06-24 2:37 ` Eli Zaretskii
2018-06-24 11:54 ` Jan Nieuwenhuizen
2018-06-26 0:47 ` Greg Troxel
2018-06-26 8:04 ` Alexander Nasonov
[not found] <8736xd45zc.fsf@pobox.com>
2018-06-29 7:39 ` Andy Wingo
2018-06-29 8:39 ` Hans Åberg
2018-06-29 10:10 ` Chris Vine
2018-06-29 10:34 ` Hans Åberg
2018-06-29 15:35 ` Chris Vine
2018-06-29 15:55 ` Hans Åberg
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=874lht4683.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=eliz@gnu.org \
--cc=guile-devel@gnu.org \
--cc=guile-users@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).