Dead code: Difference between revisions

Revision as of 15:19, 26 November 2002

Revision as of 08:32, 5 July 2003

Line 1:

In [[computer programming]], '''dead code''' consists of blocks of programming instructions or entire 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. (SometimesMany ittimes simplydead meanscode thatis aninserted by extremelya defensive programmer has insertedfor [[can't happen]] tests whichthat really can't happen --(yet). Other times dead code is inserted by the programmer for debugging purposes but has yet to be removed.)