The Elements of Programming Style: Difference between revisions

Content deleted Content added

Revision as of 04:07, 9 January 2022 edit Ser Amantio di Nicolao (talk \| contribs) Autopatrolled, Administrators 6,590,756 edits m now in infobox template, removed: {{italic title}} Tag: AWB ← Previous edit		Latest revision as of 14:11, 10 August 2025 edit undo Chris the speller (talk \| contribs) Autopatrolled, Extended confirmed users, Pending changes reviewers 894,091 edits m →Lessons: replaced: recursively-defined → recursively defined Tag: AWB
(One intermediate revision by one other user not shown)
Line 71: # Don't patch bad code – rewrite it. # Write and test a big program in small pieces. # Use recursive procedures for recursively- defined data structures. # Test input for plausibility and validity. # Make sure input doesn't violate the limits of the program. Line 109: # Format a program to help the reader understand it. # Document your data layouts. # Don't over-comment. Modern readers may find it a shortcoming that its examples use older [[procedural programming languages]] ([[Fortran]] and [[PL/I]]) ~~which~~that are quite different from those popular today. Few of today's popular languages had been invented when this book was written. However, many of the book's points that generally concern stylistic and structural issues transcend the details of particular languages. ==Reception==