Furthermore, this book's answers are intended for the most part to be definitively correct, and to avoid propagating any misconceptions. Within the elaborate answers you will find shortcuts and simplifications where necessary, and in the Glossary beginning on page xxx you will find definitions of the precise terms which accurate explanations often demand. As we'll see particularly in chapters 3 and 11, the standard definitions of C do not specify the behavior of every C program which can be written. This book is about portable C programming, so its answers advise against using nonportable constructs if at all possible. That feedback has been invaluable in refining the form of the answers.
Many answers also contain references and notes.
The examples are written primarily for clarity of exposition. The author and publisher invite you to use and modify these code fragments in your own programs, but of course we would appreciate acknowledgment if you do so. To underscore certain points, it has unfortunately been necessary to include a few code fragments which are examples of things not to do. Organization As was already mentioned, this book's questions are based on real questions asked by real people, and real-world questions do not always fall into neat hierarchies. Usually, before you can start writing code you have to declare your data structures, so chapter 1 starts out by talking about declaration and initialization.