From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Larry McVoy <lm@bitmover.com>
Cc: Oliver Xymoron <oxymoron@waste.org>,
samson swanson <intellectcrew@yahoo.com>,
linux-kernel@vger.kernel.org
Subject: Re: a great C++ book?
Date: Tue, 1 Jan 2002 13:01:23 -0700 [thread overview]
Message-ID: <200201012001.g01K1NF15702@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <20020101104331.F4802@work.bitmover.com>
In-Reply-To: <20020101041111.29695.qmail@web14310.mail.yahoo.com> <Pine.LNX.4.43.0201011214560.7188-100000@waste.org> <20020101104331.F4802@work.bitmover.com>
Larry McVoy writes:
> On Tue, Jan 01, 2002 at 12:25:10PM -0600, Oliver Xymoron wrote:
> > On Mon, 31 Dec 2001, samson swanson wrote:
> >
> > > hello again,
> > >
> > > i ask this group because i trust in your intellect.
> > >
> > > For a beginner to C++ what is your favorite book? A
> > > book that goes in depth of teaching the language.
> > > remeber i am a beginner, new to c++.
> >
> > If you already know C well, Bjarne Stroustrup's "The C++ Programming
> > Language" is decent. If not, start with Kernighan and Ritchie's "The C
> > Programming Language". Put the two next to each other and you might gain
> > some insight into the creeping horror that modern C++ has become.
>
> It's hard to explain a love/hate relationship with C++. I think
> many systems programmers come to a point where they can "speak" C++
> and do so in design conversations all the time, talking about the
> "objects" and the "methods", etc. But they program in C.
>
> This sends a somewhat mixed message to the casual observer who might
> think that one language or the other is "better". The reality is
> that you want tp program in a fairly object oriented way but you
> also want to avoid "the creeping horror that modern C++ has
> become.".
An extract from the FAQ about C++: http://www.tux.org/lkml/#s1-4
"My personal view is that C++ has it's merits, and makes
object-oriented programming easier. However, it is a more complex
language and is less mature than C. The greatest danger with C++ is in
fact it's power. It seduces the programmer, making it much easier to
write bloatware. The kernel is a critical piece of code, and must be
lean and fast. We cannot afford bloat. I think it is fair to say that
it takes more skill to write efficient C++ code than C code. Not every
contributer to the linux kernel is an uber-guru, and thus will not
know the various tricks and traps for producing efficient C++ code."
Object-oriented programming is a good tool. One of many. But it
shouldn't be a religion, nor do you need to write in C++ to make use
of it. A good example of object-oriented programming done in C is the
Xt toolkit.
> Makes you wonder what would happen if someone tried to design a
> minimalistic C++, call it the "M programming language", have be
> close to C with the minimal useful parts of C++ included.
I'm sure lots of people have thought about this. A friend of mine and
I sat down once and did a rough design for the "K" language, which was
supposed to be "exactly like C, only better". Basically, we wanted to
cherry-pick the good bits of C++, plus add some other things. As
usual, lack of time is the enemy. Besides, what's point unless it gets
widely used, and the chance of that is small.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
next prev parent reply other threads:[~2002-01-01 20:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-01 4:11 samson swanson
2002-01-01 4:40 ` Larry McVoy
2002-01-01 5:17 ` David A. Frantz
2002-01-01 5:34 ` Todor Todorov
2002-01-01 18:25 ` Oliver Xymoron
2002-01-01 18:43 ` Larry McVoy
2002-01-02 0:34 ` J.A. Magallon
2002-01-02 1:10 ` H. Peter Anvin
2002-01-02 1:29 ` Alexander Viro
2002-01-02 4:22 ` Michael P. Soulier
2002-01-02 18:46 ` Timothy Covell
2002-01-02 15:43 ` Oliver Xymoron
2002-01-01 20:01 ` Richard Gooch [this message]
2002-01-02 0:42 ` J.A. Magallon
2002-01-02 1:41 ` Richard Gooch
2002-01-02 9:59 ` Kai Henningsen
[not found] <fa.j24p57v.1d34p2v@ifi.uio.no>
[not found] ` <fa.i865mpv.1g42885@ifi.uio.no>
2002-01-02 2:45 ` Dan Maas
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=200201012001.g01K1NF15702@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=intellectcrew@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=oxymoron@waste.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®