|
The purpose of this sort of thing is to "hook up" two very different things. The human's problem space is very different from today's computer's solution space. One is highly perceptual and the other is highly procedural. Object-oriented design (which has been around thousands of years, despite what the software high-priests maintain) is one attempt to map one to the other with whatever layer of abstraction is necessary. "Languages" like the one mentioned are another.
Software OOP became "hot" in the early nineties. The cost of the resources to do it well was so high that there wasn't a suitable return on investment. Consequently, it languished. Unfortunately, such delays left its development and methodology pretty much in the hands of academics and other non-real-world types. The resulting mess is a conglomeration of fiats and dictums and procedures that don't often hold up to rational scrutiny.
The blurb in my signature is all that's left of an abortive attempt at a tutorial on OOP, using C++. It's very difficult (for me) to write such a tutorial that goes beyond the mere syntactical requirements of using classes and so forth. It's a different way of thinking that I find easier to do than to convey.
|