Related:

• HCF /H-C-F/ n. Mnemonic for `Halt and Catch Fire'
  any of several undocumented and semi-mythical machine instructions with destructive side-effects, supposedly included for test purposes on several well-known architectures going as far back as the IBM 360....
• HCF: Halt and Catch Fire
• killer poke: n. A recipe for inducing hardware damage on a machine via insertion of invalid values (see {poke}) into a memory-mapped control registe
  used esp. of various fairly well-known tricks on {bitty box}es without hardware memory management (such as the IBM PC and Commodore PET) that can overload and trash analog electronics in the monitor....
• boxed comments: n. Comments (explanatory notes attached to program instructions) that occupy several lines by themselve
  o called because in assembler and C code they are often surrounded by a box in a style something like thi...
• ack puke: n. Some processor architectures are said to `puke their guts onto the stack' to save their internal state during exception processing.
  The Motorola 68020, for example, regurgitates up to 92 bytes on a bus fault....
• death code: n. A routine whose job is to set everything in the computer -- registers, memory, flags, everything -- to zero, including that portion of memory where it is running
  its last act is to stomp on its own "store zero" instruction....
• bug n. An unwanted and unintended property of a program or piece of hardware, esp.
  one that causes it to malfunction. Antonym of feature....
• Classic C: /klas'ik C/ [a play on `Coke Classic'] n.
  The C programming language as defined in the first edition of {K&R}, with some small additions....
• oy language: n. A language useful for instructional purposes or as a proof-of-concept for some aspect of computer-science theory, but inadequate for general-purpose programming.
  {Bad Thing}s can result when a toy language is promoted as a general purpose solution for programming (see {bondage-and-discipline language})...