[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <nycvar.YFH.7.76.1809052120510.24932@n3.vanv.qr>
Date: Wed, 5 Sep 2018 21:22:11 +0200 (CEST)
From: Jan Engelhardt <jengelh@...i.de>
To: Greg KH <greg@...ah.com>
cc: 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,
"Michael S. Tsirkin" <mst@...hat.com>, 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 Wednesday 2018-09-05 18:55, Greg KH wrote:
>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?
With C++11, C++ has become a much nicer language to use (for userspace, anyway).
>And if userspace wants to do this, can't they do the C namespace trick
>themselves when they do the import?
The only trick is to use an extra C source file and extensively wrap things.
Powered by blists - more mailing lists