Microsoft released the Basic compiler in the 20th century, which announced the birth of the Basic language. Since "ancient", the Basic language has been applicable to the programming language of beginners, and is "low energy" by C / C programmer. Under Windows, Microsoft released Visual Basic, which is also "low energy low energy" by C / C programmer, because in general, the MFC is lower than the VB, so VB programmers are all white rice, so To make a good program, you can learn C , so the VB programmer is caught down.
Below, I will ask the following questions on the underlying problem:
Assembly language and C that bottom
MFC and API's underlying?
Obviously, assembly language and API are more underdeveloped. Since VB uses the API, we need the underlying service, you can use the API, because the API call is convenient, do not have to do anything to use MFC, because the common operation VB has greatly simplified our code, the system calls a statement, statement ,easy and convenient.
As for the implementation of the pointer, there are all of the API, we can also package components and call more convenient. Multi-threaded, there are all in the API, we can still package into components. As long as there is an API, we can do anything.
At the beginning of the new century, Microsoft issued an epoch-rancing .NET Framework, this runtime completely changed the "low" hat of VB. Since the language running library is the same. Therefore, C can do things, VB can do it. Moreover, in VS2002, large-scale modification is made to the VB language, so that VB is completely object-oriented programming language, there is a reference, inheritance, passionate function, a callback. And the language is simple.
Now, I officially announced that things that can do, VB can do, and more beautiful than they are!
