The Jargon File, Version 4.0.0, 24 Jul 1996 by Various
page 169 of 773 (21%)
page 169 of 773 (21%)
![]() | ![]() |
|
|
a spirit of irony by real hackers years after the fact. 2. /vt./
The Macintosh resource decompiler. On a Macintosh, many program structures (including the code itself) are managed in small segments of the program file known as `resources'; `Rez' and `DeRez' are a pair of utilities for compiling and decompiling resource files. Thus, decompiling a resource is `derezzing'. Usage: very common. :dead: /adj./ 1. Non-functional; {down}; {crash}ed. Especially used of hardware. 2. At XEROX PARC, software that is working but not undergoing continued development and support. 3. Useless; inaccessible. Antonym: `live'. Compare {dead code}. :dead code: /n./ Routines that can never be accessed because all calls to them have been removed, or code that cannot be reached because it is guarded by a control structure that provably must always transfer control somewhere else. The presence of dead code may reveal either logical errors due to alterations in the program or significant changes in the assumptions and environment of the program (see also {software rot}); a good compiler should report dead code so a maintainer can think about what it means. (Sometimes it simply means that an *extremely* defensive programmer has inserted {can't happen} tests which really can't happen -- yet.) Syn. {grunge}. See also {dead}, and {The Story of Mel, a Real Programmer}. :dead link: /n./ [WWW] A World-Wide-Web URL that no longer points to the information it was written to reach. Usually this |
|


