> >You may find that creating your own wrappers for these files that do
> >
> >extern "C" {
> >#define new new_
> >#define private private_
> >#include <linux/foo.h>
> >#undef new
> >#undef private
> >}
> >
> >safer, since you won't break anything
>
> It breaks module symbol versions, see earlier mail to l-k.
I don't believe that is the case.
You compute the modversions against the C header files. You include the C++
header files in a C++ module and you include the module version file directly.
Your symbols match providing you don't have an object called private or new
that is globally exported. We don't seem to have any of those
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
