Re: To go with Go or C/C++?

From:

Bo Persson <bop@gmb.dk>

Newsgroups:

comp.lang.c++

Date:

Thu, 02 May 2013 19:29:24 +0200

Message-ID:

<aufm3hFstjkU1@mid.individual.net>

Scott Lurndal skrev 2013-05-02 19:06:

Bo Persson <bop@gmb.dk> writes:

Gerald Breuer skrev 2013-05-01 20:44:

Learn C first because you need a magnitude of time less to learn.
Then learn C++ and forget some idioms of C-programming.

The problem is that you have to forget A LOT of C, like

Why? It all still works in C++. That's a benefit.

No, it's a big disadvantage because C++ has better tools for this. Why
not learn them first?

Try

std::string s = t;

over

char * s = malloc(strlen(t) + 1);
strcpy(s, t);

// and much later:

free(s);

and guess which is easier to learn (without missing the meaning of the
+1, or forgetting the free).

printf and scanf
C string handling
pointers and arrays
malloc and free
inventing odd names instead of overloaded functions
typedef struct
prefixed names instead of namespaces
pass-by-pointer instead of pass-by-reference
that << and >> are some odd bit shifting instead of I/O operators

And here you are joking, right? Or do you truely think that bit shifting
and C++ don't mix?

No, but I believe a new student shouldn't START there. You can learn
that later, if and when you need it.

Bo Persson