public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Dow" <jdow@earthlink.net>
To: "T. A." <tkhoadfdsaf@hotmail.com>, <root@chaos.analogic.com>,
	"Martin Dalecki" <dalecki@evision-ventures.com>,
	"Kurt Wall" <kwall@kurtwerks.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: C++ and the kernel
Date: Tue, 9 Apr 2002 14:51:04 -0700	[thread overview]
Message-ID: <018201c1e010$a5fc52c0$1125a8c0@wednesday> (raw)
In-Reply-To: <Pine.LNX.3.95.1020409075919.4157A-100000@chaos.analogic.com> <OE76STdsxAedIkuHZNp0000992f@hotmail.com>

From: "T. A." <tkhoadfdsaf@hotmail.com>

>     Who the heck said anything about rewriting the kernel?  I'm just looking
> into coding a C++ framework for those whom may like to use it in modules,
> mostly for hack value.

May I humbly suggest that this list is not a good place for this discussion.
Attitudes are quite ossified for many good reasons and probably a few bad
reasons. Take a reasonably cleanly functioning kernel as a tool and develop
a fully C++ kernel. Try it out. Benchmark it for size and speed. Report back
comparisons with its original base.

You are sounding like a little boy who has found a new toy. Over 40 years of
experience suggests the proper way to handle this is to let the person have
his head, and in the corporate world some IR&D funds, to develop a project
that uses the idea and report back in detail how it worked out. If it succeeds
the company or group wins. If it fails it managed to stay out of your product
stream, for as sure as the Sun generally rises roughly in the East it WILL
find its way into something as the person's way of finding out for himself if
it works.

This is an issue that has caused this list a significant amount of distraction
over the years. Maybe it would be a really good thing to develop numbers and
data to either support it or shoot it down. The cant of a Computer Science
cirrocumuli often fails when the rubber meets the road. This may and may not
be such. I trust the kernel maintainers' instincts in this regard. Old age
and experience will beat youth and enthusiasm any day in the long run.

So take a team with you, select a dictator or leader or whatever, and simply
make a rigid translation of a kernel snapshot to C++ without adding any new
functionality. Let us all watch the progress, say on SourceForge or the like.
And report back when it is all done. You may be right that it is something
that is worth doing. But, unless you can show in very hard data that there is
a real advantage to C++ in the kernel Linus will simply reject it with the
full support of the rest of his crew.

FWIW, Microsoft does not use C++ in their kernel.
{^_^}


  reply	other threads:[~2002-04-09 21:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-09 10:16 C++ and the kernel T. A.
2002-04-09  9:54 ` Martin Dalecki
2002-04-09 12:10   ` Richard B. Johnson
2002-04-09 12:26     ` Dr. David Alan Gilbert
2002-04-09 13:28       ` Richard B. Johnson
2002-04-09 14:00         ` Chris Friesen
2002-04-09 13:55           ` Sean Neakums
2002-04-09 14:00             ` Alexander Viro
2002-04-09 14:02         ` Michael Clark
2002-04-09 14:30         ` Rik van Riel
2002-04-10  1:52         ` H. Peter Anvin
2002-04-09 17:17     ` T. A.
2002-04-09 21:51       ` J. Dow [this message]
2002-04-09 23:11         ` Rui Sousa
2002-04-09 17:27   ` T. A.
2002-04-09 11:29 ` Erik Mouw
2002-04-09 16:21 ` Kurt Wall
  -- strict thread matches above, loose matches on Subject: below --
2002-04-09 16:45 Sau Dan Lee
2002-04-09 16:51 Sau Dan Lee
2002-04-09 16:58 ` Richard B. Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='018201c1e010$a5fc52c0$1125a8c0@wednesday' \
    --to=jdow@earthlink.net \
    --cc=dalecki@evision-ventures.com \
    --cc=kwall@kurtwerks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.com \
    --cc=tkhoadfdsaf@hotmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox