Today , I finally finished reading the APUE, basically the main knowledge is in these chapters.
Before reading "unix/linux Programming Practice Tutorial", there is a sense of enlightened, relaxed feeling, at the code level to understand a lot of Linux system mechanisms, and never understand the programming details, and Unix The overall knowledge structure of programming has a good grasp.
Apue is a well-known classic, the detailed explanation of every knowledge is very thorough, there are a lot of careful hints. But the process does not seem so good, for the following reasons:
- 1. The translator's bad level! Many sentences are not Chinese can speak at all. Helpless English rotten, at most can look at the level of man, can only see the Chinese version. This book is Yu Jinyuan and several graduate students together, some places barely able to read, but some chapters, really want to carefully try to figure out what the original intention is. If you happen to encounter some difficult to understand the knowledge point, feel the pit Father home, not to Baidu Google some can be happy to go on. Although the translation is so, still can appreciate the author's rigorous level of compilation.
- 2. Many chapters are too much for detail. Cause it is easy to get into the intricacies of the details, and forget the chapter of the overall knowledge of the context. System programming many functions side-by-side functions, many flags, many parameters set, let people complain incessantly.
- 3. Only to explain the interface, there is not much knowledge of the expansion of the UNIX system itself, some mechanisms and principles are not much involved. This practical tutorial is well done, directory structure, redirection, process, scripting features, and theshell principle with relish.
- 4. Few legends, memory analysis, structure relationships, program structures, System kernel interaction diagrams, these are diagrams that are very helpful for understanding knowledge.
- 5. There are very few instances, many of which are specific to an interface, and there are few practical examples of the concatenation of knowledge points. And some difficult to understand the chapter, no instance, just introduce the interface function, and as to how to use, in the actual programming play what role, do not know. As if to say, now show you, have this interface, and so on which day you use, to refer to it.
- 6. The spirit of academic research embodies too much, many times to a critical point. The entire platform is filled with various contrast judgments. I believe many people will not be happy to tangle with these things for the first time. Maybe chatty books, especially UNIX like so many versions, want a book to cover all the circumstances, the result of the last resort, but this is also a cross-platform must consider the details.
- 7. It does look like a UNIX key Interface Reference manual, do not expect to be able to thoroughly understand at once, read the ideal situation should be like this: remember what features, interfaces and features, as for the details and usage, then check should be able to understand immediately.
- 8. He is very unfriendly to the novice, as if the reader has been in the UNIX field of programming, but has not formed the experience, knowledge system. Without Linux operating experience, it is completely impossible to look directly at this book, even with many Linux operations (common commands,Linux system mechanisms, file systems, pipelines, process features,Shell script), but there is no complete C language, data structure, and a little operating system,gcc compiler knowledge, will encounter a lot of size difficulties. In fact, this book, is essentially a reference book, not a primer, has tried to step up gradually.
As for the merits of the book, not to mention, online praise too much. For me, the main thing is that the functionality that an operating system can provide to the user's program layer, the so-called System interface , has a comprehensive and profound understanding--let me know what the program can do, and I can know roughly what the complex software is, and what technologies are used at the bottom. have a good understanding of C language security, stable programming, and cross-platform program development. Finally understand the straight, direct hit the key C language and minimalist first, only do one thing the relationship between the UNIX blood.
Finally, let's talk about the process of reading this book . Of course it's against the computer, and it's a must for a networked computer with a UNIX like system.
No use vi, but I do not object to use him, and even appreciate the use of 6 of the people. I just do not want to be bound by those religious beliefs, do not want to interfere with other details of my energy, just want to learn programming, do a good thing, this is the main, do not give up the end.
Virtual machine Ubuntu12.04 with console gedit and GCC is the development environment, constantly manually compiled and debugged, in order to understand the program construction process.
One thing is not to say, in the information age, all the objective difficulties are almost nonexistent, there is a speed of the computer, plus a broadband, and dedication to the determination, you can have any of the programming realm you want to have.
Network material is too useful, learning difficulties encountered, the predecessors have almost met, this is almost the best teacher.
Apue "UNIX Environment Programming"
