Date: Tue, 11 Jul 2006 10:14:03 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: V.Haisman@sh.cvut.cz Cc: freebsd-hackers@freebsd.org, delphij@delphij.net, julian@elischer.org, mag@intron.ac Subject: Re: kern/99979: Get Ready for Kernel Module in C++ Message-ID: <20060711.101403.-928138940.imp@bsdimp.com> In-Reply-To: <44B2D2DF.2000401@sh.cvut.cz> References: <1152540567.99616@origin.intron.ac> <44B2AE69.4080703@elischer.org> <44B2D2DF.2000401@sh.cvut.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <44B2D2DF.2000401@sh.cvut.cz>
V=E1clav Haisman <V.Haisman@sh.cvut.cz> writes:
: Deciding that some features are bad beforehand, before you evaluate t=
hem
: is IMO bad idea. Let interested people write a bunch of C++ modules w=
ith
: the complete language before deciding on what shouldn't be used.
There's actually a fair amount of experience with people doing C++ in
FreeBSD kernels. People have been doing things with it for about 8
years now. There are significant performance issues with even C code
compiled as C++. It is possible to write fast C++ for kernel work,
but it is also very easy to write really bad C++ for kernel work.
Easier than bad C code.
There's reasons that people here are somewhat skeptical about using
C++ in the kernel.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060711.101403.-928138940.imp>