From: "<Iliyan Malchev>" <ibm@asu.edu>
To: Glynn Clements <glynn.clements@virgin.net>
Cc: Mat Harris <mat.harris@genestate.com>,
linux-c-programming@vger.kernel.org
Subject: Re: migration from perl
Date: Thu, 15 Aug 2002 15:32:08 -0700 (MST) [thread overview]
Message-ID: <Pine.GSO.4.21.0208151528350.21083-100000@general1.asu.edu> (raw)
In-Reply-To: <15707.56675.958362.834807@cerise.nosuchdomain.co.uk>
On Thu, 15 Aug 2002, Glynn Clements wrote:
> > Should I learn C or C++?
>
> I recommend learning C first. C++ is based upon C, so most of the
> effort spent on learning C will still be relevant if you decide to use
> C++.
I must disagree with this statement. Bjarne Stroustrup in his book "The
Design and Evolution of C++" has a section dedicated to questions of that
nature, and his answer to "Should I learn C first, and then C++?" is that you
should not learn C if you want to learn C++ eventually. Start with C++ from
scratch. Yes, while C++ is superset of C, you should not think of it this
way. C++ lets you program around a different paradigm, and you should start
with that.
Regards
Ilian Maltchev
"Computers in the future may weigh no more than 1.5 tons."
--Popular Mechanics, forecasting the relentless march of
science, 1949
-------------------------------------------------
Ilian Maltchev
-------------------------------------------------
email: ibm@asu.edu
ilian_maltchev@inter-tel.com
-------------------------------------------------
next prev parent reply other threads:[~2002-08-15 22:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-15 14:35 migration from perl Mat Harris
2002-08-15 15:29 ` Axel Siebenwirth
2002-08-15 16:10 ` Mat Harris
2002-08-15 16:54 ` Glynn Clements
[not found] ` <20020815170931.A32743@genestate.com>
2002-08-15 16:27 ` Axel Siebenwirth
2002-08-15 16:57 ` Glynn Clements
2002-08-15 22:32 ` <Iliyan Malchev> [this message]
2002-08-15 22:42 ` +Rudymartin
2002-08-15 23:33 ` Glynn Clements
2002-08-16 15:34 ` Earl R. Lapus
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.GSO.4.21.0208151528350.21083-100000@general1.asu.edu \
--to=ibm@asu.edu \
--cc=glynn.clements@virgin.net \
--cc=linux-c-programming@vger.kernel.org \
--cc=mat.harris@genestate.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;
as well as URLs for NNTP newsgroup(s).