From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Bart Samwel <bart@samwel.tk>
Cc: Ashish sddf <buff_boulder@yahoo.com>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Compiling C++ kernel module + Makefile
Date: Mon, 19 Jan 2004 15:37:46 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.53.0401191521400.8389@chaos> (raw)
In-Reply-To: <400C37E3.5020802@samwel.tk>
On Mon, 19 Jan 2004, Bart Samwel wrote:
> Richard B. Johnson wrote:
> > On Mon, 19 Jan 2004, Bart Samwel wrote:
> [... lots of text ...]
[Snipped...]
I stand by my assertion that anybody who develops kernel
modules in C++, including MIT students, is arrogant.
Let's see if C++ is in use in the kernel. At one time, some
of the tools that came with it were written in C++ (like ksymoops).
Script started on Mon Jan 19 15:19:33 2004
$ cd /usr/src/linux-2.4.24
$ find . -name "*.cpp"
$ exit
exit
Script done on Mon Jan 19 15:20:25 2004
Well, perhaps the kernel developers were ignorant. They didn't
write anything in C++. Maybe they were just too dumb to learn the
language?
Maybe there is another reason:
The kernel development languages, as previously stated, were
defined at the project's inception to be the GNU C 'gcc'
compiler's "C" and extensions, and the 'as' (AT&T syntax)
assembler. Anybody can search the archives for the discussions
about using C++ in the kernel.
Any person, or group of persons, who is smart enough to
actually write some kernel code in C++, has proved that
they are not ignorant. Therefore, they have demonstrated
their arrogance.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2004-01-19 20:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 21:09 Compiling C++ kernel module + Makefile Ashish sddf
2004-01-16 22:07 ` Richard B. Johnson
2004-01-17 12:59 ` Bart Samwel
2004-01-19 13:46 ` Richard B. Johnson
2004-01-19 17:40 ` Bart Samwel
2004-01-19 18:39 ` Richard B. Johnson
2004-01-19 20:02 ` Bart Samwel
2004-01-19 20:37 ` Richard B. Johnson [this message]
2004-01-19 21:24 ` Bart Samwel
2004-01-20 15:20 ` Richard B. Johnson
2004-01-20 17:34 ` Zan Lynx
2004-01-20 18:10 ` Richard B. Johnson
2004-01-20 13:38 ` Thomas Lahoda
2004-01-21 2:24 ` Michael Clark
2004-01-20 18:16 ` Chris Friesen
2004-01-21 17:01 ` Giuliano Pochini
2004-01-21 17:16 ` Bart Samwel
2004-01-20 0:59 ` Robin Rosenberg
2004-01-20 6:46 ` Linus Torvalds
2004-01-20 7:32 ` Robin Rosenberg
2004-01-20 10:46 ` Bart Samwel
2004-01-20 5:29 ` Valdis.Kletnieks
2004-01-20 9:48 ` Bart Samwel
2004-01-16 22:40 ` Sam Ravnborg
2004-01-19 13:21 Petr Vandrovec
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=Pine.LNX.4.53.0401191521400.8389@chaos \
--to=root@chaos.analogic.com \
--cc=bart@samwel.tk \
--cc=buff_boulder@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.