From owner-freebsd-hackers  Fri Mar 28 15:58:38 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA14311
          for hackers-outgoing; Fri, 28 Mar 1997 15:58:38 -0800 (PST)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA14305
          for <hackers@FreeBSD.ORG>; Fri, 28 Mar 1997 15:58:35 -0800 (PST)
Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id PAA03417; Fri, 28 Mar 1997 15:58:21 -0800 (PST)
To: "Gregory D. Moncreaff" <moncrg@dominus.ma.ultranet.com>
cc: "hackers@freebsd.org" <hackers@FreeBSD.ORG>
Subject: Re: C++ Code in Kernel 
In-reply-to: Your message of "Fri, 28 Mar 1997 18:10:51 EST."
             <01BC3BA3.6FFD23A0@dominus.ultranet.com> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3409.859593499.1@time.cdrom.com>
Date: Fri, 28 Mar 1997 15:58:20 -0800
Message-ID: <3410.859593500@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> maybe its just that I'm taking a c++ class now, but I'm
> cusious as to the pro's and con's on writing kernel source
> in c++.  I haven't seen nor heard on this happening on FreeBSD
> [but then my travels haven't been that wide]

My understanding is that You Don't Wanna Do It.

Linus tried it for awhile with Linux before he started to find places where
the compiler was doing weird things to him, like putting virtual destructor
table info on the stack as a side-effect of some operation while he, in
an interrupt handler, was sort of wanting it NOT to do things like that.

There are a lot of nice mechanisms which one could implement just as
easily in straight C to far improve the structure of the kernel, I think.
No need for a blunt instrument that big. :)

					Jordan