Related:

• An Ode to C: 0x0d2C ~~~~~~ May your signals all trap May your references be bounded All memory aligned Floats to ints rounded.
  And Remember ... Non-zero is true Use -> for a pointer ++ adds one A dot if it's not Arrays start with zero ?...
• C: Short for "chutzpah", a quality needed before tacling even the more simplest program with this language.
  C is also the symbol for the speed of light, but that has absolutely nothing to do with how quickly one can learn or use the language....
• vaxocentrism /vak`soh-sen'trizm/ n. [analogy with `ethnocentrism'] A notional disease said to afflict C programmers who persist in coding according to certain assumptions that are valid (esp.
  under Unix) on VAXen but false elsewhere. Among these are...
• decay: [from nuclear physics] n.,vi. An automatic conversion which is applied to most array-valued expressions in {C}
  hey `decay into' pointer-valued expressions pointing to the array's first element....
• ap: v. To replace a pointer to a pointer with a direct pointe
  to replace an old address with the forwarding address found there....
• mouse droppings: [MS-DOS] n. Pixels (usually single) that are not properly restored when the mouse pointer moves away from a particular location on the scree
  producing the appearance that the mouse pointer has left droppings behind....
• him: n. A small piece of data inserted in order to achieve a desired memory alignment or other addressing property.
  For example, the PDP-11 UNIX linker, in split I&D (instructions and data) mode, inserts a two-byte shim at location 0 in data space so that no data object will have an address of 0 (and be confused with the C null pointer)....
• fandango on core n. [Unix/C hackers, from the Iberian dance] In C
  a wild pointer that runs out of bounds, causing a core dump, or corrupts the malloc(3) arena in such a way as to cause mysterious failures later on, is sometimes said to have `done a fandango on core'....
• aliasing bug: n. A class of subtle programming errors that can arise in code that does dynamic allocation, esp.
  via `malloc(3)' or equivalent. If several pointers address (`aliases for') a given hunk of storage, it may happen that the storage is freed or reallocated (and thus moved) through one alias and then referenced through another, which may lead to subtle (and possibly intermittent) lossage depending on the state and the allocation history of the malloc {arena}....