From: "J.A. Magallon" <jamagallon@able.es>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: Larry McVoy <lm@bitmover.com>,
Oliver Xymoron <oxymoron@waste.org>,
samson swanson <intellectcrew@yahoo.com>,
linux-kernel@vger.kernel.org
Subject: Re: a great C++ book?
Date: Wed, 2 Jan 2002 01:42:33 +0100 [thread overview]
Message-ID: <20020102014233.C5968@werewolf.able.es> (raw)
In-Reply-To: <20020101041111.29695.qmail@web14310.mail.yahoo.com> <Pine.LNX.4.43.0201011214560.7188-100000@waste.org> <20020101104331.F4802@work.bitmover.com> <200201012001.g01K1NF15702@vindaloo.ras.ucalgary.ca>
In-Reply-To: <200201012001.g01K1NF15702@vindaloo.ras.ucalgary.ca>; from rgooch@ras.ucalgary.ca on Tue, Jan 01, 2002 at 21:01:23 +0100
On 20020101 Richard Gooch wrote:
>
>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
Use the right tool for the purpose. You bet for rewriting half the
C++ runtime in C instead of not-using the bloated part of C++.
Pretty. If you're going to program in a OO way, use an oo language.
And I get tired of people saying C++ is bloat. My pupils at 5th course
of Computer Science still think C++ is bloat. They have no idea on
compilers. And they bless Ada.
A 5th level virtual function still has only a one-level
indirection overhead when called. Low level code is just as efficient
as C. If a C++ program is bloated it is the programmers matter, not
the language.
>of it. A good example of object-oriented programming done in C is the
>Xt toolkit.
>
kidding ????
Perhaps GTK+, but Xt...
By
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.2 (Cooker) for i586
Linux werewolf 2.4.18-pre1-beo #3 SMP Thu Dec 27 10:15:27 CET 2001 i686
next prev parent reply other threads:[~2002-01-02 0:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-01 4:11 a great C++ book? 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-01 20:01 ` Richard Gooch
2002-01-02 0:42 ` J.A. Magallon [this message]
2002-01-02 1:41 ` Richard Gooch
2002-01-02 0:34 ` J.A. Magallon
2002-01-02 9:59 ` Kai Henningsen
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
[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=20020102014233.C5968@werewolf.able.es \
--to=jamagallon@able.es \
--cc=intellectcrew@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=oxymoron@waste.org \
--cc=rgooch@ras.ucalgary.ca \
/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