From: Xi Ruoyao <xry111@xry111.site>
To: Andy <borucki.andrzej@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: How to explain this syntax?
Date: Wed, 19 Apr 2023 20:41:48 +0800 [thread overview]
Message-ID: <ee9785867dc0af3fde4a3e46e78faadf0aee73aa.camel@xry111.site> (raw)
In-Reply-To: <CAE2KeAJjcWOUL7Z1XgFOWWZdYPZ0rhxOiecTwLGonnrmCbEf3w@mail.gmail.com>
On Wed, 2023-04-19 at 14:35 +0200, Andy via Gcc-help wrote:
> I don't learn C, but I am writing c90 Antlr grammar which should be as
> compatible with GCC as possible.
> I see many GNU extension, one is most significant is nested functions,
> but all code is compilable with GCC with std=c90, not need std=gnu90,
> although some code is compilable only with std=gnu90
-pedantic-errors will reject most GNU extensions if you don't want them.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
prev parent reply other threads:[~2023-04-19 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 10:25 Andy
2023-04-16 10:53 ` Andrew Haley
2023-04-19 11:40 ` Andy
2023-04-19 11:53 ` Xi Ruoyao
2023-04-19 12:35 ` Andy
2023-04-19 12:41 ` Xi Ruoyao [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ee9785867dc0af3fde4a3e46e78faadf0aee73aa.camel@xry111.site \
--to=xry111@xry111.site \
--cc=borucki.andrzej@gmail.com \
--cc=gcc-help@gcc.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).