The typographical style of this book is similar to that of other programming books:
File, library, GConf keys, and URLs , such as gobject.h , /apps/gconfdemo/ pictures_as_words , and http://www.gnome.org/ are set in italic.
Glossary terms appear in boldface italic at first mention.
, separated by an angle
code, shell commands, function names, and variable
GtkWidget *foo = gtk_widget_new();
Note that you can distinguish a function by its trailing parentheses:
Class names like GtkWidget are set in boldface.
Object names also appear in monospace . Therefore, you might see phrases like "The object gconf belongs to the GConfClient class" and " gconf is a GConfClient ." However, you will frequently see "a GConfClient object" used to refer to an indefinite object of a class.
Parameters such as object in G_OBJECT( object ) are in monospaced italic .
Properties and signals such as
Pseudocode such as << save humanity >> is monospaced between two sets of angle brackets. You will often see << ... >> . This means that there's no reason to say what this pseudocode does, because it's either obvious or undefined .
References to literature such as [Wirth] and [Pennington] appear in brackets. Appendix C is a bibliography.
There are note indicators in the margin to denote material that is particularly helpful or important.
Likewise, if you see a warning in the margin, you should read the material
Because the text in this book has a maximum width of 83 monospaced
GTK+ and GNOME have gradually become platform independent. In spite of this, the primary working environment for this book is Unix. When there is a difference among Unix systems, this book leans toward a GNU system with a Linux kernel (
The examples in this book are quite important. At the very least, you should skim them, acquiring a good idea of what they do and a fundamental understanding of how they work. This text
In the continuing effort to keep this book's page count down, many of the examples here are not complete valid C programs. The first few chapters contain primarily short multiline
If you come across a variable that doesn't seem to have a declaration and you don't know its type or significance, take a look at the previous pages; you should find it there. For instance, the listings
When a preprocessor directive such as #include appears just before some function calls, then you must use the directive somewhere at the beginning of your source code. This is similar to the style of the online Unix programming manual; run man gethostbyname and look at the SYNOPSIS section.