i have just now started studyin Thinking in C++ Vol. 1 by Bruce Eckel
so i went through the chapter no.1 on Objects... but i m having my doubts in it.... thats why i m here to seek help
in chap. 1, i found the following text
i want to emphasize specially on the part in blue... what i have got from it is tht when a programmer gets a problem he has to analyse the problem from two reference points. one from the machine point of view and the other from the problem's point of view.. bt i want to ask two things..All programming languages provide abstractions. It can be argued that the complexity of the problems you’re able to solve is directly related to the kind and quality of abstraction. By “kind” I mean, “What is it that you are abstracting?” Assembly language is a small abstraction of the underlying machine. Many so-called “imperative” languages that followed (such as Fortran, BASIC, and C) were abstractions of assembly language. These languages are big improvements over assembly language, but their primary abstraction still requires you to think in terms of the structure of the computer rather than the structure of the problem you are trying to solve. The programmer must establish the association between the machine model (in the “solution space,” which is the place where you’re modeling that problem, such as a computer) and the model of the problem that is actually being solved (in the “problem space,” which is the place where the problem exists). The effort required to perform this mapping, and the fact that it is extrinsic to the programming language, produces programs that are difficult to write and expensive to maintain, and as a side effect created the entire “programming methods” industry.
1. by mapping what does the author actually want to say
2. in C does the programmer really need to think totally in terms of machine (i m not really gud in C so this foolish doubt had to come) what about the modern C approaches like 'Objective C??
thanx for ur help