Getting used to C++ takes a little while for everyone, but for grizzled C programmers, the process can be
especially unnerving. Because C is effectively a subset of C++, all the old C tricks continue to work, but many
of them are no longer appropriate. To C++ programmers, for example, a pointer to a pointer looks a little funny.
Why, we wonder, wasn't a reference to a pointer used instead?
C is a fairly simple language. All it really offers is macros, pointers, structs, arrays, and functions. No matter
what the problem is, the solution will always boil down to macros, pointers, structs, arrays, and functions. Not
so in C++. The macros, pointers, structs, arrays and functions are still there, of course, but so are private and
protected members, function overloading, default parameters, constructors and destructors, user-defined
operators, inline functions, references, friends, templates, exceptions, namespaces, and more. The design space
is much richer in C++ than it is in C: there are just a lot more options to consider.
When faced with such a variety of choices, many C programmers hunker down and hold tight to what they're
used to. For the most part, that's no great sin, but some C habits run contrary to the spirit of C++. Those are the
ones that have simply got to go.
Comments
Post a Comment
https://gengwg.blogspot.com/