From: "Hans Åberg" <haberg-1@telia.com>
To: Chris Vine <vine35792468@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: c99 support
Date: Fri, 29 Jun 2018 17:55:52 +0200 [thread overview]
Message-ID: <64F03231-8BEC-4611-83F3-687A40C71F02@telia.com> (raw)
In-Reply-To: <20180629163549.ee530b4c3738f36e85a3a5e3@gmail.com>
> On 29 Jun 2018, at 17:35, Chris Vine <vine35792468@gmail.com> wrote:
>
> On Fri, 29 Jun 2018 12:34:07 +0200
> Hans Åberg <haberg-1@telia.com> wrote:
>>> If, say, uint8_t is available in stdint.h for C, it
>>> will be available for C++. §21.4.1/2 of C++17 makes this even more
>>> explicit: "The [cstdint] header defines all types and macros the
>>> same as the C standard library header <stdint.h>".
>>
>> Which C version? In g++7, __STDC_VERSION__ is not defined, only __STDC__.
>
> In C++17, references to "C" are to ISO/IEC 9899:2011. References to the
> C standard library are to "the library described in Clause 7 of ISO/IEC
> 9899:2011". In C++11 and C++14, the references are to ISO/IEC
> 9899:1999.
Good.
> By default (if you don't use the -std=c++xx flag) g++-7
> compiles according to C++14.
I am using C++17. And gcc7 defaults to C11, so there is an incompatibility with the default g++ C version it seems.
next prev parent reply other threads:[~2018-06-29 15:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8736xd45zc.fsf@pobox.com>
2018-06-29 7:39 ` c99 support 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 [this message]
2018-06-23 19:11 Andy Wingo
2018-06-23 19:23 ` Eli Zaretskii
2018-06-23 20:07 ` Andy Wingo
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
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=64F03231-8BEC-4611-83F3-687A40C71F02@telia.com \
--to=haberg-1@telia.com \
--cc=guile-devel@gnu.org \
--cc=vine35792468@gmail.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).