Messages in this thread | | | From | Yann Droneaud <> | Date | Wed, 05 Sep 2018 19:33:38 +0200 | Subject | Re: [RFC] UAPI: Check headers by compiling all together as C++ |
| |
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++.
-- Yann Droneaud OPTEYA
| |