Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Subject: RE: kbuild & C++
Date: Wed, 7 Sep 2005 11:13:24 +0200
Message-ID: <809C13DD6142E74ABE20C65B11A2439809C4BE@www.telos.de>
Thread-Topic: kbuild & C++
Thread-Index: AcWzNfrIfCiZ2FNESH+4jAM4+CvINwAVXBdQ
From: "Budde, Marco" <budde@telos.de>
To: "Esben Nielsen" <simlo@phys.au.dk>, "Jesper Juhl" <jesper.juhl@gmail.com>
Cc: <linux-kernel@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1144
Lines: 35

Hi,

>> That would be because the kernel is written in *C* (and some asm),
*not* C++.

I cannot see the connection. At the end everything gets converted
to assembler/opcode. In the user space I can mix C and C++ code
without any problems, why should this not be possible in the
kernel mode?

>> There /is/ no C++ support.

This will be a problem in future. Nearly nobody will start a new
larger project (driver, user space software, embedded firmware)
using non OO languages today. So porting eg. Windows drivers to
Linux is nearly impossible without C++ support.

E.g. in my case the Windows source code has got more than 10 MB.
Nobody will convert such an amount of code from C++ to C.
This would take years.

> I think it can only be a plus to Linux to add C++ support for at least
> out-of-mainline drivers. Adding drivers written in C++ into the
mainline
> is another thing.

Right.

cu, Marco

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