A Discipline of Programming

Dijkstra, E. W. (1976). A Discipline of Programming. Prentice Hall.

Type

Book

Intellectual base

Textbook

Year

1976

ISBN

9780132158718

Link

https://openlibrary.org/books/OL5211853Mmatched

Cited from

computer_science, linguistics_semiotics, mathematics

Cited by

5 citations across 5 artifacts.

Each citation links to the sentence it supports in the citing article.

Primes

• Constraint
  • … as a distinct computer-science subfield; Floyd's 1967 "Assigning Meanings to Programs" and Hoare's 1969 axiomatic semantics recast program correctness as the preservation of logical invariants under each program step, treating invariants as constraints on reachable states; Dijkstra's 1976 A Discipline of Programming

    This sourceGuarded commands, weakest-precondition calculus, constraint-based program derivation. Pedagogical extension: Gries, The Science of Programming (Springer, 1981).

• Iteration
  • The structural kinship with Newton's method is precise— same diagnostic questions (what is the state update, what is the progress measure, what is the stopping rule), same failure modes (no measurable progress, bad step size, wrong stopping rule)— even though the substrate is product development rather than function-zero finding
• Meta-Symbolic Reflection
  • Listed in the references but not attached to a specific claim.
• Recursion
  • A common failure is mutual recursion where both functions increase their arguments, creating infinite loops that appear valid locally

    This sourceGuarded commands, weakest-precondition calculus, constraint-based program derivation. Pedagogical extension: Gries, The Science of Programming (Springer, 1981).

Domain-specific

• Hoare Logic
  • Dijkstra developed this into a program-construction discipline in which programs and proofs can be derived together.

    This sourceFoundational treatment of guarded commands and weakest-precondition reasoning.

Verification

Does it exist? Confirmed. This work's ISBN resolves to a registered record, which fixes its identity. That is all it fixes.

Does it back the claim? Not recorded. Neither this nor any other of the 5 citations of this work carries a recorded support check.

Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.

See how references were verified.

Registry ID ref:50aa68638edc · see in the full table