From: "T. A." <tkhoadfdsaf@hotmail.com>
To: <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 13:17:30 -0400 [thread overview]
Message-ID: <OE76STdsxAedIkuHZNp0000992f@hotmail.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1020409075919.4157A-100000@chaos.analogic.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.
And yes I do know C++ and it can very well be used for low level stuff
such as the kernel. Now that doesn't mean I'm going to go wild and start
writing extensive templates, exceptions, standard template libraries, or any
of the other unneeded crap (mostly from the last C++ revision) either.
And as far as the comment of being a troll goes I could definitely find
better uses of my time. Only reason for a post here is because I'm looking
for some guidance on a couple of minor issues I've encountered. The C
brigades can go back and rest in the barracks now.
----- Original Message -----
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: "Martin Dalecki" <dalecki@evision-ventures.com>
Cc: "T. A." <tkhoadfdsaf@hotmail.com>; "Linux Kernel Mailing List"
<linux-kernel@vger.kernel.org>
Sent: Tuesday, April 09, 2002 8:10 AM
Subject: Re: C++ and the kernel
>
> I would like to rewrite the kernel in FORTRAN because this was
> one of the first languages I learned.
>> snip <<
> If you really knew C++, you wouldn't even joke about putting it
> in the kernel.
>
> Cheers,
> Dick Johnson
>
> Penguin : Linux version 2.4.18 on an i686 machine (797.90 BogoMips).
>
> Windows-2000/Professional isn't.
>
>
----- Original Message -----
From: "Kurt Wall" <kwall@kurtwerks.com>
To: "T. A." <tkhoadfdsaf@hotmail.com>
Sent: Tuesday, April 09, 2002 12:16 PM
Subject: Re: C++ and the kernel
> Scribbling feverishly on April 09, T. A. managed to emit:
> > Hi all,
> >
> > I am in the initial stages of writing some C++ wrapper classes for
the
> > kernel. So far its been an interesting process, mainly due to the use
of
>
> Stop right here, read http://www.tux.org/lkml/#s15-3, and figure out
> what you've done wrong. ;-)
>
> > Would patches be welcomed for one or more of these issues?
>
> I dare say not. One wonders if this message was a carefully crafted
> troll.
>
> Kurt
> --
> You will reach the highest possible point in your business or profession.
>
next prev parent reply other threads:[~2002-04-09 17:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 10:16 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. [this message]
2002-04-09 21:51 ` J. Dow
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
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=OE76STdsxAedIkuHZNp0000992f@hotmail.com \
--to=tkhoadfdsaf@hotmail.com \
--cc=dalecki@evision-ventures.com \
--cc=kwall@kurtwerks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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
all inboxes | Powered by JetHome®