From: Timothy Covell <timothy.covell@ashavan.org>
To: "Michael P. Soulier" <michael.soulier@rogers.com>,
linux-kernel@vger.kernel.org
Subject: Re: a great C++ book?
Date: Wed, 2 Jan 2002 12:46:34 -0600 [thread overview]
Message-ID: <200201021850.g02IoHSr021331@svr3.applink.net> (raw)
In-Reply-To: <a0tmmt$ear$1@cesium.transmeta.com> <Pine.GSO.4.21.0201012015430.16467-100000@weyl.math.psu.edu> <20020102042204.GD4313@tigger>
In-Reply-To: <20020102042204.GD4313@tigger>
On Tuesday 01 January 2002 22:22, Michael P. Soulier wrote:
> On 01/01/02 Alexander Viro did speaketh:
> > And then there is "six month ago I cud not spel injuneer and now I r won"
> > crowd - and quite a few of them seem to be afraid of C. FWIC it is a
> > damn good reason to stay with C...
> >
> :) That's because they picked-up "Visual Basic for Dummies" and now
>
> they claim to be programmers. *sigh*
>
> Mike
I got my degree in Physics, so I learned to program in Fortran. In
that day, however, there were folks who were clamoring for more C
programming in science. I took one look at it and gagged on the pointers
and mallocs. In my opinion, no scientist should trust C code for important
numerical work unless he has too; that's why Fortran was created in the first
place.
Anyhow, one of the local self-appointed Unix gurus was aghast at
my distaste for C's primitiveness. Alas, I feal justified today because
Perl, Java, C#, and Cyclone are proving that C is for systems programming and
not for everyday use.
That much said, I still am only fluent in Fortran, shell, Perl (and a little
Tcl/TK), so I don't really consider myself a programmer, just a sysadmin with
a clue.
--
timothy.covell@ashavan.org.
next prev parent reply other threads:[~2002-01-02 18:50 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 [this message]
2002-01-02 15:43 ` Oliver Xymoron
2002-01-01 20:01 ` Richard Gooch
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=200201021850.g02IoHSr021331@svr3.applink.net \
--to=timothy.covell@ashavan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.soulier@rogers.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®