From: Eli Zaretskii <eliz@gnu.org>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: c99 support
Date: Sun, 24 Jun 2018 05:37:52 +0300 [thread overview]
Message-ID: <83o9g0ucxr.fsf@gnu.org> (raw)
In-Reply-To: <874lht4683.fsf@pobox.com> (message from Andy Wingo on Sat, 23 Jun 2018 22:07:24 +0200)
> From: Andy Wingo <wingo@pobox.com>
> Cc: guile-users@gnu.org, guile-devel@gnu.org
> Date: Sat, 23 Jun 2018 22:07:24 +0200
>
> > 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
All of the above is available with reasonably recent versions of MinGW.
> I assume MinGW uses GCC. What version? I see that the version 6 series
> is available on mingw.org.
Current versions are 6 and 7, I have 5.3 installed on one of my
machines. All of them support what you mentioned.
next parent reply other threads:[~2018-06-24 2:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <878t7548ta.fsf@pobox.com>
[not found] ` <83po0htihm.fsf@gnu.org>
[not found] ` <874lht4683.fsf@pobox.com>
2018-06-24 2:37 ` Eli Zaretskii [this message]
2018-06-23 20:12 c99 support Andy Wingo
2018-06-24 0:00 ` Chris Vine
2018-06-24 9:13 ` Arne Babenhauserheide
2018-06-29 7:39 ` Andy Wingo
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=83o9g0ucxr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=guile-devel@gnu.org \
--cc=guile-user@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).