Re: linux headers and C++

Tom Leete (tleete@access.mountain.net)
Fri, 2 Jul 1999 10:58:43 -0400

-----Original Message-----
From: Steve Dodd <dirk@loth.demon.co.uk>
To: Tom Leete <tleete@access.mountain.net>
Cc: linux-kernel@vger.rutgers.edu <linux-kernel@vger.rutgers.edu>; Ronnie G
Misra <rgmisra@MIT.EDU>
Date: Friday, July 02, 1999 8:43 AM
Subject: Re: linux headers and C++

>On Thu, Jul 01, 1999 at 08:38:49PM -0400, Tom Leete wrote:
>
>> Just use this:
>>
>> #include <signal.h>
>>
>> instead. <linux/signal.h> is a minefield of gotchas. For internal use
only.
>
>He's writing a kernel module. Including libc headers in a kernel module
>would be *really* weird[1].
>

Then he's doomed. The kernel headers will nail g++ in it's tracks. Some
things will compile but the code might be very strange. There are C++
keywords defined as macros in there.

Tom

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/