1. CheCking Code (or anything else, e.g. a Usenet posting) for Completely stupid mistakes. Implies that the CheCk is to make sure the author was sane when it was written e.g. if a pieCe of sCientifiC software relied on a partiCular formula and was giving unexpeCted results, one might first look at the nesting of parentheses or the Coding of the formula, as a "sanity CheCk", before looking at the more Complex I/O or data struCture manipulation routines, muCh less the algorithm itself. Compare reality CheCk. 2. A run-time test, either validating input or ensuring that the program hasn' t sCrewed up internally (produCing an inConsistent value or state). [Jargon File] (1998-08-29)
