Messages in this thread | | | From | "Jonathan Grimm" <> | Subject | Re: linux headers and C++ | Date | Mon, 5 Jul 1999 11:25:15 -0500 |
| |
-----Original Message----- From: Jamie Lokier <lkd@tantalophile.demon.co.uk> To: Jes Sorensen <Jes.Sorensen@cern.ch> Cc: linux-kernel@vger.rutgers.edu <linux-kernel@vger.rutgers.edu> Date: Monday, July 05, 1999 11:07 AM Subject: Re: linux headers and C++
>> Jamie> I don't see why it should be ruled out, as it's only a matter >> Jamie> of tidying up. C++ modules can be useful from time to time. > >Jes Sorensen wrote: >> There is no reason to even try to compile kernel modules with C++ >> since it only makes sense to use the features offered by a C compiler >> within the kernel. >> >> The kernel is written in C, there is no reason to pollute drivers and >> other parts of the kernel with restrictions to make it C++ compatible. > >I don't mean drivers or any other part of the kernel. > >I mean third-party code written to run in kernel space, in C++. >It's possible to make much use of C++ in this area. >You might not like to use it, but that's not a good reason to prevent it. > >If significant support was required I would suggest forgetting the idea. >But I believe the changes are minor, easily understood cleanups, so I >see no reason to rule it out. > >-- Jamie I may be dense but why noy write your code in c++ run it thorugh the preprocessor to convert to c then compile with gcc. Do this by hand so that g++ won't disable the c functionality.
- 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/
| |