Live data from Hacker News

Instance Model Programming in C

slkpg.byethost7.com

21–22 of 22 posts

Re: Instance Model Programming in C

#21
post #20
post #13

Earlier quoted context omitted.

Another good read are The Annotated C++ Reference Manual [1] and The Design and Evolution of C++ [1]. They help understand all design compromises that were done to keep compatibility with C, which is was part of what brought C++ into the mainstream, but also the main cause of many of its warts. [1] http://www.amazon.com/The-Annotated-C-Reference-Manual/dp/02... [2] http://www.amazon.com/The-Design-Evolution-Bjarne-St…

> Another good read are The Annotated C++ Reference Manual[1] and The Design and Evolution of C++[1]. Annotated C++ Reference Manual as well as D&E is severely dated. Quite a while back there was some talk of stroustrup co-authoring a revision of the reference-manual with andrew-koenig, but it never came to fruition...

That is true, but the point here is to learn how C++ got designed in first place, you can't update that.

Re: Instance Model Programming in C

#22
post #15

Drifting from the topic, but I never understood this urgent need for so much inheritance when doing OO, especially when using languages that don't natively have it, like C and JavaScript. I really like OO programming (i.e. I'm particularly not one of the functional-fundamentalist OO-haters here on HN), but as I've grown more experienced, I've started to use inheritance less and less, and composition more and more. Th…

That is far from an uncommon idea. The phrase to search for to learn more about this is "Composition over Inheritance". That leads you to e.g. http://en.wikipedia.org/wiki/Composition_over_inheritance or, combined with "site: c2.com" to http://c2.com/cgi/wiki?CompositionInsteadOfInheritance or http://c2.com/cgi/wiki?UseCompositionAndInterfacesWithoutCla... . In some sense, deep inheritance hierarchies were a thing of…

80's!?!

OO only started to get into the enterprise in the 90's.

Post reply on HN