From: Sean Neakums <sneakums@zork.net>
To: linux-kernel@vger.kernel.org
Subject: Re: C++ and the kernel
Date: Tue, 09 Apr 2002 14:55:59 +0100 [thread overview]
Message-ID: <6uofgtvuvk.fsf@zork.zork.net> (raw)
In-Reply-To: <Pine.LNX.3.95.1020409085537.4291B-100000@chaos.analogic.com> <3CB2F3F9.8325AC04@nortelnetworks.com>
commence Chris Friesen quotation:
> "Richard B. Johnson" wrote:
>> Making code "cleaner" is a matter of perspective.
>>
>> class A {
>> public: void func(char *st) { cout << st << endl; }
>> };
>> using A::func;
>> A a;
>> a.func("Hello World!");
>>
>> Is not all that clean. In fact, I'm not sure I have it right. It's
>> easier and clearer to write puts("Hello World!");
>
> Your example is needlessly complex, and I'm sure you know this. A more
> realistic comparison would be:
>
> cout << "Hello World!\n";
And of course standard libraries are not available in the kernel, so
you'll most likely end up calling printk anyway in your C++ kernel
code.
--
///////////////// | | The spark of a pin
<sneakums@zork.net> | (require 'gnu) | dropping, falling feather-like.
\\\\\\\\\\\\\\\\\ | | There is too much noise.
next prev parent reply other threads:[~2002-04-09 13:56 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 [this message]
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
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=6uofgtvuvk.fsf@zork.zork.net \
--to=sneakums@zork.net \
--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 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®