Re: list of 7, 8 concepts for learning c++

From:

Juha Nieminen <nospam@thanks.invalid>

Newsgroups:

comp.lang.c++

Date:

06 Mar 2011 07:50:43 GMT

Message-ID:

<4d733cd3$0$2867$7b1e8fa0@news.nbl.fi>

K4 Monk <k4monk@gmail.com> wrote:

1. Polymorphism: function level and through derived class. Also
through templates
2. Streams: everything I/O involves streaming
3. Implementation level representation of an object.
4. Implementation level representation of member objects
5. Three types of inheritance and why should they be used: private,
protected, and public
6. Implementation level representation of derived class objects
7. Multiple inheritence, and where it is necessary
8. The clusterfuck made up of the above 7

  And what is the alternative you suggest? Not having polymorphism? Not
having templates? Not having type-safe streams?

  As for implementation-level representation of classes, it's necessary
for efficiency and to determine access rights. (There exist technologies
to achieve the same thing with more abstract code, but usually they put
quite heavy demands on the runtime environment, usually requiring things
like JIT compilation.)

  As for multiple inheritance, all OO languages I know of have multiple
inheritance. It's just that in most other languages it's a crippled
version that is significantly less useful than in C++. (They don't *call*
it "multiple inheritance", and they vehemently deny that it is, but that's
what it is, plain and simple. Just because it's a crippled version doesn't
mean it's not multiple inheritance.)