[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180905133711-mutt-send-email-mst@kernel.org>
Date: Wed, 5 Sep 2018 13:42:58 -0400
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Yann Droneaud <ydroneaud@...eya.com>
Cc: Greg KH <greg@...ah.com>, David Howells <dhowells@...hat.com>,
linux-api@...r.kernel.org, linux-kbuild@...r.kernel.org,
Michal Marek <michal.lkml@...kovi.net>,
dri-devel@...ts.freedesktop.org,
virtualization@...ts.linux-foundation.org,
keyrings@...r.kernel.org, David Airlie <airlied@...ux.ie>,
linux-nilfs@...r.kernel.org, linux-nvdimm@...ts.01.org,
codalist@...a.cs.cmu.edu, coda@...cmu.edu, coreteam@...filter.org,
Rob Clark <robdclark@...il.com>, linux-arm-msm@...r.kernel.org,
Kent Overstreet <kent.overstreet@...il.com>,
Dan Williams <dan.j.williams@...el.com>,
Takashi Iwai <tiwai@...e.com>, linux-bcache@...r.kernel.org,
Coly Li <colyli@...e.de>, Jaroslav Kysela <perex@...ex.cz>,
Jan Harkes <jaharkes@...cmu.edu>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Ryusuke Konishi <konishi.ryusuke@....ntt.co.jp>,
Jason Wang <jasowang@...hat.com>,
Mat Martineau <mathew.j.martineau@...ux.intel.com>,
netfilter-devel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
moderated for non-subscribers <alsa-devel@...a-project.org>,
freedreno@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC] UAPI: Check headers by compiling all together as C++
On Wed, Sep 05, 2018 at 07:33:38PM +0200, Yann Droneaud wrote:
> Hi,
>
> Le mercredi 05 septembre 2018 à 18:55 +0200, Greg KH a écrit :
> > On Wed, Sep 05, 2018 at 04:54:27PM +0100, David Howells wrote:
> > >
> > > Here's a set of patches that inserts a step into the build process to make
> > > sure that the UAPI headers can all be built together with C++ (if the
> > > compiler being used supports C++). All but the final patch perform fixups,
> > > including:
> >
> > Wait, why do we care? What has recently changed to start to directly
> > import kernel uapi files into C++ code?
> >
> > And if userspace wants to do this, can't they do the C namespace trick
> > themselves when they do the import? That must be how they are doing it
> > today, right?
> >
>
> They can't.
>
>
> Adding extern "C" { } doesn't magically make "class" a non keyword.
> Even if it was the case, writing C++ code using whatever->class would
> probably broke because class is a keyword in C++.
I think it's a bug in the language TBH.
> --
> Yann Droneaud
> OPTEYA
>
Powered by blists - more mailing lists