From: Al Viro <viro@ZenIV.linux.org.uk>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, dhowells@redhat.com
Subject: Re: [RFC] UAPI: Check headers by compiling all together as C++
Date: Thu, 13 Sep 2018 23:15:47 +0100 [thread overview]
Message-ID: <20180913221546.GV19965@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20180913220124.GA12570@avx2>
On Fri, Sep 14, 2018 at 01:01:24AM +0300, Alexey Dobriyan wrote:
> > Don't tempt me...
>
> <= g++-8 doesn't support C99 style initializers.
> g++-8 mostly does: for example
>
> .foo = {
> [BAR] = 1,
> },
>
> doesn't work, but regular .foo = 42 does.
> Additionally, g++ makes noise about order of initializators.
> C++20 is supposed to make things better.
It's too early for AFD postings. And you *are* tempting
me to throw into the tree as many anti-C++ devices as can be
done tastefully, just to stop somebody attempting that insanity
in the earnest.
next prev parent reply other threads:[~2018-09-13 22:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 18:59 [RFC] UAPI: Check headers by compiling all together as C++ Alexey Dobriyan
2018-09-05 19:26 ` Greg KH
2018-09-05 19:31 ` Alexey Dobriyan
2018-09-05 22:22 ` Al Viro
2018-09-13 22:01 ` Alexey Dobriyan
2018-09-13 22:15 ` Al Viro [this message]
2018-09-13 23:27 ` David Howells
2018-09-13 23:42 ` Al Viro
2018-09-05 19:53 ` David Howells
-- strict thread matches above, loose matches on Subject: below --
2018-09-06 9:18 David Howells
2018-09-05 15:54 David Howells
2018-09-05 16:55 ` Greg KH
2018-09-05 17:33 ` Yann Droneaud
2018-09-05 17:42 ` Michael S. Tsirkin
2018-09-06 7:12 ` Yann Droneaud
2018-09-05 19:22 ` Jan Engelhardt
2018-09-05 17:50 ` David Howells
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=20180913221546.GV19965@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=adobriyan@gmail.com \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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 NNTP newsgroup(s).