From the assembly language to the Library Framework

I saw a question in the Forum a few days ago. I have a reply below.

[Quote = reference reply on the 21st floor:]
The C ++ language can indeed create various wonders. I don't know whether it is its glory or sorrow.
[/Quote]

His reply does not help the landlord's problem because it is not a language problem.
So when I saw his complaint, I wanted to refute him, but then I only helped the landlord solve the problem and did not reply to him.

The landlord's problem is caused by "rules and requirements.

 

At the lowest level, if there are no requirements or rules, you can use the machine code to write anything at will. In this way, no compiler is involved in the middle, so there will be no problem with the landlord, it's just whether the machine can execute the machine code as required. In this way, there is no language to talk about, and there is no need to complain about the wonderful language.

 

Upgrade to a higher level, and then have an assembly program (the Assembly engine can be mistakenly understood as the compiler of the assembly language), in order to let the assembly program understand your source code, therefore, a small number of syntax rules have been customized. However, different machine codes are identified by different readable instruction codes according to the working method of the processor. Not to mention that compilation is difficult, but it is complicated to use compilation for development ]. [Syntax rules are relatively simple and the development process is cumbersome]

 

Then with the C language, everything is starting from here. The C language specifies the "syntax rule", which is much more complicated than the Assembly syntax rule! C language syntax rules are more complex than assembly, but the development process is much easier than Assembly, because the C compiler has done a lot of tedious things for you. [Syntax rules are cumbersome and the development process is relatively easy]

 

With the C ++ language, C ++ not only has more complex syntax rules than C, but also introduces and supports the [Object Oriented Thinking]. Aside from the object-oriented thinking, the syntax of C ++ is somewhat higher than that of C language, and the increase in keywords is positive. I will not list other added features. The C ++ development process does not reduce the workload much than the C development process, but there are also improvements. Again, it proves that the more complex the syntax rules, the easier the development process]

 

Then, in the [object-oriented thinking], object-oriented thinking is a set of abstract rules that can be completely separated from programming. I often hear people say what language is object-oriented. In fact, many languages only support object-oriented, it doesn't mean that this language is object-oriented (you can say that Smalltalk is object-oriented, and I have nothing to say). With the support of object-oriented ideas, how easy the development process has become! Or [the more complex the syntax rules and programming ideas are, the easier the development process is]

 

After Java and C #, I will not talk about it, and the idea has been introduced into programming. In order to improve the development efficiency, awesome companies or organizations simply implement some basic functional modules for programmers, and then STL, boost, MFC, ATL, VCL, DOTNET, [jfc, javaapi] (I still don't know the exact name of the Java class library) and so on, a series of class library frameworks came into being ...... Then the programmer is exhausted in learning these class library frameworks.