From the DOS era, there are a large number of books. The article involves the so-called unapplicted calls. It is still that. Microsoft's DDK should be the official documentation of the people who write drive to Windows, according to the truth Microsoft should have DDK The document is very well, after all, a bad ordinary application is not easy to bring a fatal impact on the entire system, and a bad driver can cause the entire system crash at any time. Because of the needs of work, I saw a little DDK. I had to use a kernel API: ZwcreateFile. The result found that DDK gave several constants actually continuous detail descriptions, and found two articles. The document is associated with these constants, and there is no explanation in both. What is this? ! faint!
Personally, many times Microsoft always complicates simple questions and then packaged with some fast development tools. At first glance, I have to use somewise that it should not be complicated in the past.
A colleague developed under UNIX is difficult to understand the complexity of the COM interface implementation and application of MS. I explained him about COM's goals, he said to me, these things we will encounter under UNIX, it will not be very complicated, although it may be a bit ugly, the function may not be comprehensive and powerful, but Absolutely you can work.
It is now more hard to make a slightly underlying development on Windows now. If the difficulty of the project itself is still there, many times you have to face the MS half-mask hidden even the incomplete document, and a lot of energy is spent on the place where the flower is not. We are only easy to count the product of two prices, but this work is an NP problem. Many times, comrades on the ground-level development must have to find some urgent needs but there is no documentation.
Microsoft, when can you give the programmer a clear white? ? ?
