Difference between revisions of "Structured programming"
From Wiki @ Karl Jones dot com
Karl Jones (Talk | contribs) |
Karl Jones (Talk | contribs) (→Description) |
||
Line 5: | Line 5: | ||
This is in contrast to using simple tests and jumps such as the [[Goto|goto statement]] which could lead to [[spaghetti code]] which is difficult both to follow and to maintain. | This is in contrast to using simple tests and jumps such as the [[Goto|goto statement]] which could lead to [[spaghetti code]] which is difficult both to follow and to maintain. | ||
− | It emerged in the 1960s, particularly from a famous letter, Go To Statement Considered Harmful. | + | It emerged in the 1960s, particularly from a famous letter, [[Go To Statement Considered Harmful]]. |
It was bolstered theoretically by the structured program theorem, and practically by the emergence of languages such as ALGOL with suitably rich control structures. | It was bolstered theoretically by the structured program theorem, and practically by the emergence of languages such as ALGOL with suitably rich control structures. |
Revision as of 07:41, 2 September 2015
Structured programming is a programming paradigm aimed at improving the clarity, quality, and development time of a computer program by making extensive use of subroutines, block structures, and for and while loops.
Description
This is in contrast to using simple tests and jumps such as the goto statement which could lead to spaghetti code which is difficult both to follow and to maintain.
It emerged in the 1960s, particularly from a famous letter, Go To Statement Considered Harmful.
It was bolstered theoretically by the structured program theorem, and practically by the emergence of languages such as ALGOL with suitably rich control structures.
See also
- Computer programming
- Computer science
- Edsger Wybe Dijkstra
- Go To Statement Considered Harmful
- Goto
- Programming language
- Programming paradigm
- Software engineering
- Spaghetti code
External links
- Structured programming @ Wikipedia