From: Alexander Nasonov <alnsn@yandex.ru>
To: Greg Troxel <gdt@lexort.com>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel@gnu.org
Subject: Re: c99 support
Date: Tue, 26 Jun 2018 09:04:25 +0100 [thread overview]
Message-ID: <20180626080425.GA1348@neva> (raw)
In-Reply-To: <smua7ritltt.fsf@linuxpal.mit.edu>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
Greg Troxel wrote:
>
> Andy Wingo <wingo@pobox.com> writes:
>
> > Is there anyone who compiles Guile with a compiler that does not support
> > C99? If so, please give platform and compiler.
>
> Not really the question you asked, and pretty fuzzy, but an anecdote
> about a real situation I am aware of:
>
> In 2015--2016, there was some C code that was supposed to be very
> portable and a notion that using C99 features would not be a problem
> in any environment (as in "In 2015, it's beyond lame not to support
> C99".) It turned out that it was almost entirely no problem, except
> for one build environment that was using an old compiler, I think from
> MS. That compiler could handle almost all of C99, except mixed
> declarations and code.
"Granted, however, there is also bad news for C programmers"
https://herbsutter.com/2012/05/03/reader-qa-what-about-vc-and-c99/
Alex
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2018-06-26 8:04 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
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 [this message]
[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=20180626080425.GA1348@neva \
--to=alnsn@yandex.ru \
--cc=gdt@lexort.com \
--cc=guile-devel@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).