From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 11 16:14:57 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 23F9616A4DA for ; Tue, 11 Jul 2006 16:14:57 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD45843D55 for ; Tue, 11 Jul 2006 16:14:55 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k6BGDtai043185; Tue, 11 Jul 2006 10:13:55 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Tue, 11 Jul 2006 10:14:03 -0600 (MDT) Message-Id: <20060711.101403.-928138940.imp@bsdimp.com> To: V.Haisman@sh.cvut.cz From: "M. Warner Losh" In-Reply-To: <44B2D2DF.2000401@sh.cvut.cz> References: <1152540567.99616@origin.intron.ac> <44B2AE69.4080703@elischer.org> <44B2D2DF.2000401@sh.cvut.cz> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Tue, 11 Jul 2006 10:13:56 -0600 (MDT) 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++ X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 16:14:57 -0000 In message: <44B2D2DF.2000401@sh.cvut.cz> V=E1clav Haisman 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