From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 9 08:58:24 2003 Return-Path: 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 05C1B16A4BF for ; Tue, 9 Sep 2003 08:58:24 -0700 (PDT) Received: from serl.cs.colorado.edu (serl-fs.cs.colorado.edu [128.138.242.215]) by mx1.FreeBSD.org (Postfix) with ESMTP id 559AD43FD7 for ; Tue, 9 Sep 2003 08:58:21 -0700 (PDT) (envelope-from John.Giacomoni@colorado.edu) Received: from colorado.edu (serl.cs.colorado.edu [128.138.242.65]) by serl.cs.colorado.edu (8.12.9/8.12.6) with ESMTP id h89FwKiQ001362 for ; Tue, 9 Sep 2003 09:58:20 -0600 (MDT) Date: Tue, 9 Sep 2003 09:58:19 -0600 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) From: John Giacomoni To: freebsd-hackers@freebsd.org Content-Transfer-Encoding: 7bit In-Reply-To: <20030909062955.GA3139@cirb503493.alcatel.com.au> Message-Id: <6EB7BD63-E2DE-11D7-B54C-0003930719D8@colorado.edu> X-Mailer: Apple Mail (2.552) Subject: Re: C++ code in a kernel module? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2003 15:58:24 -0000 On Tuesday, Sep 9, 2003, at 00:29 America/Denver, Peter Jeremy wrote: > On Mon, Sep 08, 2003 at 11:12:59PM -0400, Alexander Kabaev wrote: >> On Mon, 8 Sep 2003 23:02:33 -0400 >> "Matthew Emmerton" wrote: >> >>> I've been silently following this thread, and unless I missed >>> something, has anyone asked John why he wants/needs to use C++ in the >>> kernel? >>> >> Tools, not policy :) > > True but if John explains more of what he is trying to do, maybe > someone can suggest either a way to avoid C++ or some insights as to > how he can get his C++ modules to work. > > Peter simple, I have preexisting C++ code which we are currently using in userland and wish to push down into the kernel. It would be ideal to keep the source bases the same without a rewrite to C. Admitting of course the possibility of having to modify to be compatible with both use modes. At present I am attempting to see what we can and cannot do in the kernel with C++ John G