Literate Programming, an Among Readers, Authors, and Critics Would Be I Approach to Programming Espoused by Sustained

Total Page:16

File Type:pdf, Size:1020Kb

Literate Programming, an Among Readers, Authors, and Critics Would Be I Approach to Programming Espoused by Sustained literate Moderated by Christopher J. Van Wyk programming n May and June 1986, Programming worth an experiment to see whether interest Pearls took up literate programming, an among readers, authors, and critics would be I approach to programming espoused by sustained. With his help, we commissioned Donald Knuth. Knuth’s premise is that the Christopher Van Wyk of AT&T Bell Laborato- best programs are meant for people as well as ries to be the moderator of a new column on machines; they are meant to be read as well literate programming, inaugurated with as run. He built a system, WEB, that scans this issue. Van Wyk received his Ph.D. from specially structured technical reports to Stanford University in 1980 and has spent extract Pascal statements interwoven the intervening years at Bell Labs with the text, forming from them working on programming lan- an executable program. Pascal is guages for graphics and algo- not essential; WEB can work as rithms for computational well with any other programming language, such as Fortran. As moderator, Van Wyk A literate program contains will pose the problems to be not only the needed state- considered, solicit and ments in a programming receive literate pro- language, but also a precise grams, obtain cri- problem statement, a summary tiques, and publish of the background needed to the results within understand the solution, an evaluation of alternatives, constraints of a assessments of trade-offs magazine-all between the runnin tasks that will use time and space, or between run- 1 ning time and programming time, and sugges- tions on how to modify the program. Program code segments are inserted in the text at points logical to the intellectual development of the algorithm. renewal. This experiment can succeed only A literate program pays careful attention to with your full support. If you are interested lucidity of presentation and presents all argu- in being the author of a literate program, or ments needed to understand why the pro- acting as the literary critic, contact Van Wyk gram will actually work as intended. To at the address listed in the masthead: emphasize the literary side, the second Pearl included a critique of Knuth’s program that Christopher J. Van Wyk evaluated it on these points. AT&T Bell Laboratories The response to both Pearls was strong Room 2C-457 and positive. Jon Bentley proposed that 600 Mountain Avenue Communications renularlv devote snace to Murray Hill, NJ 07974 interesting, literate programs andtheir well- Peter J. Denning written critiques. I agreed that it would be Editor-in-Chief July 1987 Volume 30 Number 7 Communications of the ACM 593 literate Moderated by Christopher J. Van Wyk programming PRINTING COMMON WORDS Moderator’s Introduction to Column 1 literate programming that involves much less machin- Two Programming Pearls columns in 1986 presented ery than WEB. Finally, note that Hanson solved a literate programs by Donald Knuth. The May 1986 col- slightly different problem than Knuth; although that umn contained a WEB program to generate a sorted list makes little difference to our discussion of literate pro- of M distinct numbers randomly chosen from 1 through grams, it highlights the importance of careful problem N. Programming Pearls of April 1987 contained readers’ specification in the design of large systems. comments on Knuth’s literate program, as well as an unimplemented solution to the problem by David Gries. The June 1986 Programming Pearls presented Knuth’s WEB program to print the k most common words in a file, in decreasing order by frequency. That column also elicited comments from many readers. Printing Common Words Several readers wondered how well a small example can serve to illustrate the features of a system for liter- 1. Introduction. In describing Don Knuth’s WEBsys- ate programming. The issue arose in two very different tem in one of his “Programming Pearls” [Communi- ways: One reader who thought WEB worked acceptably cations of the ACM 29, 5 (May 1986), 364-3691, Jon in the small doubted that it would serve a large project Bentley “aSsigned” the following programming problem: well; another suggested that the WEB solution’s appar- “Given a text file and an integer k, you are to print the k ent clumsiness in the small could be attributed to its most common words in the file (and the number of their being designed for larger, more complex programs. occurrences) in decreasing frequency.” A couple of readers very much appreciated Doug It is unclear from this problem statement what to do McIlroy’s addition of a figure to the documentation. with ‘%ies,” that is, does k refer to words or word fre- They also thought that trie-sorting in Sections 37-39 quencies? For example, in the problem statement, “the” needed more comments than “The restructuring opera- occurs three times “k ” “in ” “and ” and “file” each oc- tions are slightly subtle here.” curs twice, and td rek of t6e wor& each occurs once. If One sharp-eyed reader noticed that, although the program is invoked with the statement as input and Section 38 uses “the fact that count [ 01 = 0,” k = 2, which word should be output as the second most count [ 01 is never initialized. Although some Pascal common word? A rephrasing of the problem removes the compilers detect references to uninitialized variables, ambiguity: “Given a text file and an integer k, you are apparently the compiler that Knuth used at SAIL does to print the words (and their frequencies of occurrence) not. whose frequencies of occurrence are among the k largest In this inaugural column, we present another solu- in order of decreasing frequency.” tion to the problem of printing the k most common Using this problem statement, the output of ,the pro- words in a file. The author of this solution is David gram with the original problem statement as input and Hanson, a professor of computer science at Princeton with k = 2 is University and an editor of the journal Software-Prac- tice 6 Experience. Hanson’s program illustrates nicely 3 the the use of abstract data types on the way to the solution 2 file of a problem. It discusses the role of profiles of execu- 2and tion in the design of good programs, a topic that is also 2 in discussed in this month’s Programming Pearls. Han- 2k son’s solution shows how one can design a system for Tkii work WBB supported in part by the National Science Foundatian under Grant MCM2398. 0 1987 ACM OOOl-0782/137/0700-0594 $1.50 594 Communications of the ACM luly 1987 Volume 30 Number 7 Literate Programming Bentley posed this problem to present a “real” exam- /* initialize k */ ple of WEBusage. For more information about WEB,see /* initialize word table */ Knuth’s “Literate Programming,” The Computer Journal while (getwordcbuf , MAXWORD) != EOF) 67, 2 (May 1984), 97-111. Knuth’s solution appears in addword (buf > ; printwords (k) ; Communications of the ACM 29, 6 (June 1986), 471-483, along with a review by Doug McIlroy. where buf is a character array of MAXWORBcharacters, The solution given here is writ,ten in the C program- and getword places the next word in the input in buf ming language and presented using the loom system to and returns its length, or EOF at the end’of file. MAXWORD generate the printed program and its explanation. loom is defined to be 101 to allow room for a terminating null is a preprocessor whose input is a text file with embed- character. addword adds the word in buf to the table of ded references to fragments of the program. loom re- words, and printwords prints the words with the k trieves these fragments, optionally pushes them through largest frequencies. arbitrary filters, and integrates the result into the out- Getting program arguments and environment vari- put. ables, such as k and PAGESIZE, is a common feature of loom’s output is usually input to a document format- many UNIX0 programs and the code is idiomatic. Exam- ter, such as troff or ‘I&X. loom was originally written by ples can be found in The UNIX Programming Environ- Janet Incerpi and Robert Sedgewick and used in prepa- ment by B. W. Kernighsn and R. Pike (Prentice-Hall, ration of Sedgewick’s book Algorithms (Addison-Wesley, Englewood Cliffs, N.J., 1984). Reading, Mass., 1983). Starting from their program, I rewrote loom for use in writing a book and several pa- 4. Reading words. getword reads the next word from pers. the input. This is accomplished by discarding characters loom is not as ambitious or as comprehensive as WEB. up to the next occurrence of a letter, then gathering up It does, however, have the virtue of independence from the letters into the argument buffer: both formatting and programming languages. It does not, for example, provide the comprehensive indexing, int getwordcbuf, size) cross-referencing, or pretty printing facilities of WEB.With char *buf; help from its associated filters, loom does provide index- int size; ing of the identifiers used in the program fragments, al- c though the index is omitted here for brevity. And since char *p; it is not necessary to present the whole program, irrel- int c; evant details can be omitted permitting the documen- tation to concentrate on the important aspects of the p = buf; programs. I have formatted this program description in while ((c = getchar != EOF) if (isletter( < a style similar to WEBfor comparison purposes, but the do C formatting of loom’s output is not constrained to any one if (size > 1) C style. Using loom also has an effect similar to WEB:De- *p++ = c; veloping and writing about programs concurrently affect size--; both activities dramatically.
Recommended publications
  • Knuthweb.Pdf
    Literate Programming Donald E. Knuth Computer Science Department, Stanford University, Stanford, CA 94305, USA The author and his associates have been experimenting for the past several years with a program- ming language and documentation system called WEB. This paper presents WEB by example, and discusses why the new system appears to be an improvement over previous ones. I would ordinarily have assigned to student research A. INTRODUCTION assistants; and why? Because it seems to me that at last I’m able to write programs as they should be written. The past ten years have witnessed substantial improve- My programs are not only explained better than ever ments in programming methodology. This advance, before; they also are better programs, because the new carried out under the banner of “structured program- methodology encourages me to do a better job. For ming,” has led to programs that are more reliable and these reasons I am compelled to write this paper, in easier to comprehend; yet the results are not entirely hopes that my experiences will prove to be relevant to satisfactory. My purpose in the present paper is to others. propose another motto that may be appropriate for the I must confess that there may also be a bit of mal- next decade, as we attempt to make further progress ice in my choice of a title. During the 1970s I was in the state of the art. I believe that the time is ripe coerced like everybody else into adopting the ideas of for significantly better documentation of programs, and structured programming, because I couldn’t bear to be that we can best achieve this by considering programs found guilty of writing unstructured programs.
    [Show full text]
  • Programming Pearls: a Literate Program
    by jot1 Be~~tley programming with Special Guest Oysters Don Knuth and Doug McIlroy pearls A LITERATE PROGRAM Last month‘s column introduced Don Knuth’s style of frequency; or there might not even be as many as k “Literate Programming” and his WEB system for building words. Let’s be more precise: The most common programs that are works of literature. This column pre- words are to be printed in order of decreasing fre- sents a literate program by Knuth (its origins are sketched quency, with words of equal frequency listed in al- in last month‘s column) and, as befits literature, a review. phabetic order. Printing should stop after k words So without further ado, here is Knuth’s program, have been output, if more than k words are present. retypeset in Communications style. -Jon Bentley 2. The input file is assumed to contain the given Common Words Section text. If it begins with a positive decimal number Introduction.. , . , , . , . , . , , . 1 (preceded by optional blanks), that number will be Strategic considerations . , a the value of k; otherwise we shall assume that Basic input routines . , , . 9 k = 100. Answers will be sent to the output file. Dictionary lookup . , . , . , .17 define default-k = 100 (use this value if k isn’t The frequency counts . .32 otherwise specified) Sortingatrie . ...36 Theendgame................................41 3. Besides solving the given problem, this program is Index . ...42 supposed to be an example of the WEB system, for people who know some Pascal but who have never 1. Introduction. The purpose of this program is to seen WEB before.
    [Show full text]
  • Teaching Foundations of Computation and Deduction Through Literate Functional Programming and Type Theory Formalization
    Teaching Foundations of Computation and Deduction Through Literate Functional Programming and Type Theory Formalization Gérard Huet Inria Paris Laboratory, France Abstract We describe experiments in teaching fundamental informatics notions around mathematical struc- tures for formal concepts, and effective algorithms to manipulate them. The major themes of lambda-calculus and type theory served as guides for the effective implementation of functional programming languages and higher-order proof assistants, appropriate for reflecting the theor- etical material into effective tools to represent constructively the concepts and formally certify the proofs of their properties. Progressively, a literate programming and proving style replaced informal mathematics in the presentation of the material as executable course notes. The talk will evoke the various stages of (in)completion of the corresponding set of notes along the years (see [1, 2, 14, 5, 6, 10, 12, 16, 7, 15, 17, 9, 3, 13, 11, 4, 8]), and tell how their elaboration proved to be essential to the discovery of fundamental results. 1998 ACM Subject Classification F.3.1 Specifying and Verifying Programs, F.4.1 Mathematical Logic and G.4 Mathematical Software Keywords and phrases Foundations, Computation, Deduction, Programming, Proofs Digital Object Identifier 10.4230/LIPIcs.FSCD.2016.3 Category Invited Talk References 1 Gérard Huet. Initiation à la logique mathématique. Notes de cours du DEA d’Informatique, Université Paris-Sud, 1977. 2 Gérard Huet. Démonstration automatique en logique de premier ordre et programmation en clauses de horn. Notes de cours du DEA d’Informatique, Université Paris-Sud, 1978. 3 Gérard Huet. Confluent reductions: Abstract properties and applications to term rewriting systems.
    [Show full text]
  • Typeset MMIX Programs with TEX Udo Wermuth Abstract a TEX Macro
    TUGboat, Volume 35 (2014), No. 3 297 Typeset MMIX programs with TEX Example: In section 9 the lines \See also sec- tion 10." and \This code is used in section 24." are given. Udo Wermuth No such line appears in section 10 as it only ex- tends the replacement code of section 9. (Note that Abstract section 10 has in its headline the number 9.) In section 24 the reference to section 9 stands for all of ATEX macro package is presented as a literate pro- the eight code lines stated in sections 9 and 10. gram. It can be included in programs written in the If a section is not used in any other section then languages MMIX or MMIXAL without affecting the it is a root and during the extraction of the code a assembler. Such an instrumented file can be pro- file is created that has the name of the root. This file cessed by TEX to get nicely formatted output. Only collects all the code in the sequence of the referenced a new first line and a new last line must be entered. sections from the code part. The collection process And for each end-of-line comment a flag is set to for all root sections is called tangle. A second pro- indicate that the comment is written in TEX. cess is called weave. It outputs the documentation and the code parts as a TEX document. How to read the following program Example: The following program has only one The text that starts in the next chapter is a literate root that is defined in section 4 with the headline program [2, 1] written in a style similar to noweb [7].
    [Show full text]
  • Statistical Software
    Statistical Software A. Grant Schissler1;2;∗ Hung Nguyen1;3 Tin Nguyen1;3 Juli Petereit1;4 Vincent Gardeux5 Keywords: statistical software, open source, Big Data, visualization, parallel computing, machine learning, Bayesian modeling Abstract Abstract: This article discusses selected statistical software, aiming to help readers find the right tool for their needs. We categorize software into three classes: Statisti- cal Packages, Analysis Packages with Statistical Libraries, and General Programming Languages with Statistical Libraries. Statistical and analysis packages often provide interactive, easy-to-use workflows while general programming languages are built for speed and optimization. We emphasize each software's defining characteristics and discuss trends in popularity. The concluding sections muse on the future of statistical software including the impact of Big Data and the advantages of open-source languages. This article discusses selected statistical software, aiming to help readers find the right tool for their needs (not provide an exhaustive list). Also, we acknowledge our experiences bias the discussion towards software employed in scholarly work. Throughout, we emphasize the software's capacity to analyze large, complex data sets (\Big Data"). The concluding sections muse on the future of statistical software. To aid in the discussion, we classify software into three groups: (1) Statistical Packages, (2) Analysis Packages with Statistical Libraries, and (3) General Programming Languages with Statistical Libraries. This structure
    [Show full text]
  • Exploratory Data Science Using a Literate Programming Tool Mary Beth Kery1 Marissa Radensky2 Mahima Arya1 Bonnie E
    The Story in the Notebook: Exploratory Data Science using a Literate Programming Tool Mary Beth Kery1 Marissa Radensky2 Mahima Arya1 Bonnie E. John3 Brad A. Myers1 1Human-Computer Interaction Institute 2Amherst College 3Bloomberg L. P. Carnegie Mellon University Amherst, MA New York City, NY Pittsburgh, PA [email protected] [email protected] mkery, mahimaa, bam @cs.cmu.edu ABSTRACT engineers, many of whom never receive formal training in Literate programming tools are used by millions of software engineering [30]. programmers today, and are intended to facilitate presenting data analyses in the form of a narrative. We interviewed 21 As even more technical novices engage with code and data data scientists to study coding behaviors in a literate manipulations, it is key to have end-user programming programming environment and how data scientists kept track tools that address barriers to doing effective data science. For of variants they explored. For participants who tried to keep instance, programming with data often requires heavy a detailed history of their experimentation, both informal and exploration with different ways to manipulate the data formal versioning attempts led to problems, such as reduced [14,23]. Currently even experts struggle to keep track of the notebook readability. During iteration, participants actively experimentation they do, leading to lost work, confusion curated their notebooks into narratives, although primarily over how a result was achieved, and difficulties effectively through cell structure rather than markdown explanations. ideating [11]. Literate programming has recently arisen as a Next, we surveyed 45 data scientists and asked them to promising direction to address some of these problems [17].
    [Show full text]
  • Trisycl Open Source C++17 & Openmp-Based Opencl SYCL Prototype
    triSYCL Open Source C++17 & OpenMP-based OpenCL SYCL prototype Ronan Keryell Khronos OpenCL SYCL committee 05/12/2015 — IWOCL 2015 SYCL Tutorial • I OpenCL SYCL committee work... • Weekly telephone meeting • Define new ways for modern heterogeneous computing with C++ I Single source host + kernel I Replace specific syntax by pure C++ abstractions • Write SYCL specifications • Write SYCL conformance test • Communication & evangelism triSYCL — Open Source C++17 & OpenMP-based OpenCL SYCL prototype IWOCL 2015 2 / 23 • I SYCL relies on advanced C++ • Latest C++11, C++14... • Metaprogramming • Implicit type conversion • ... Difficult to know what is feasible or even correct... ;• Need a prototype to experiment with the concepts • Double-check the specification • Test the examples Same issue with C++ standard and GCC or Clang/LLVM triSYCL — Open Source C++17 & OpenMP-based OpenCL SYCL prototype IWOCL 2015 3 / 23 • I Solving the meta-problem • SYCL specification I Includes header files descriptions I Beautified .hpp I Tables describing the semantics of classes and methods • Generate Doxygen-like web pages Generate parts of specification and documentation from a reference implementation ; triSYCL — Open Source C++17 & OpenMP-based OpenCL SYCL prototype IWOCL 2015 4 / 23 • I triSYCL (I) • Started in April 2014 as a side project • Open Source for community purpose & dissemination • Pure C++ implementation I DSEL (Domain Specific Embedded Language) I Rely on STL & Boost for zen style I Use OpenMP 3.1 to leverage CPU parallelism I No compiler cannot generate kernels on GPU yet • Use Doxygen to generate I Documentation; of triSYCL implementation itself with implementation details I SYCL API by hiding implementation details with macros & Doxygen configuration • Python script to generate parts of LaTeX specification from Doxygen LaTeX output triSYCL — Open Source C++17 & OpenMP-based OpenCL SYCL prototype IWOCL 2015 5 / 23 • I Automatic generation of SYCL specification is a failure..
    [Show full text]
  • Ambiguous, Informal, and Unsound: Metaprogramming for Naturalness
    Ambiguous, Informal, and Unsound: Metaprogramming for Naturalness Toni Mattis Patrick Rein Robert Hirschfeld Hasso Plattner Institute Hasso Plattner Institute Hasso Plattner Institute University of Potsdam University of Potsdam University of Potsdam Potsdam, Germany Potsdam, Germany Potsdam, Germany [email protected] [email protected] [email protected] Abstract ACM Reference Format: Program code needs to be understood by both machines Toni Mattis, Patrick Rein, and Robert Hirschfeld. 2019. Ambigu- and programmers. While the goal of executing programs ous, Informal, and Unsound: Metaprogramming for Naturalness. In Proceedings of the 4th ACM SIGPLAN International Workshop requires the unambiguity of a formal language, program- on Meta-Programming Techniques and Reflection (META ’19), Octo- mers use natural language within these formal constraints to ber 20, 2019, Athens, Greece. ACM, New York, NY, USA, 10 pages. explain implemented concepts to each other. This so called https://doi.org/10.1145/3358502.3361270 naturalness – the property of programs to resemble human communication – motivated many statistical and machine learning (ML) approaches with the goal to improve software engineering activities. 1 Introduction The metaprogramming facilities of most programming en- The complexity of modern software systems requires col- vironments model the formal elements of a program (meta- laboration among multiple programmers. Hence, the source objects). If ML is used to support engineering or analysis code itself becomes an artifact of communication and per- tasks, complex infrastructure needs to bridge the gap be- sisted domain knowledge. The idea that programmers should tween meta-objects and ML models, changes are not reflected “concentrate rather on explaining to human beings what we in the ML model, and the mapping from an ML output back want a computer to do” has been a prominent hypothesis in into the program’s meta-object domain is laborious.
    [Show full text]
  • A Literate Programming Approach for Hardware Description Language In- Struction
    Paper ID #26263 A Literate Programming Approach for Hardware Description Language In- struction Dr. J.W. Bruce, Tennessee Technological University J.W. Bruce is with the Department of Electrical & Computer Engineering at Tennessee Technological University in Cookeville, Tennessee USA Dr. Bryan A. Jones, Mississippi State University Bryan A. Jones received the B.S.E.E. and M.S. degrees in electrical engineering from Rice University, Houston, TX, in 1995 and 2002, respectively, and the Ph.D. degree in electrical engineering from Clemson University, Clemson, SC, in 2005. He is currently an Associate Professor at Mississippi State University, Mississippi State, MS. From 1996 to 2000, he was a Hardware Design Engineer with Compaq, where he specialized in board lay- out for high-availability redundant array of independent disks (RAID) controllers. His research interests include engineering education, robotics, and literate programming. Dr. Mahnas Jean Mohammadi-Aragh, Mississippi State University Dr. Jean Mohammadi-Aragh is an assistant professor in the Department of Electrical and Computer Engi- neering at Mississippi State University. Dr. Mohammadi-Aragh investigates the use of digital systems to measure and support engineering education, specifically through learning analytics and the pedagogical uses of digital systems. She also investigates fundamental questions critical to improving undergraduate engineering degree pathways. She earned her Ph.D. in Engineering Education from Virginia Tech. In 2013, Dr. Mohammadi-Aragh was honored as a promising new engineering education researcher when she was selected as an ASEE Educational Research and Methods Division Apprentice Faculty. c American Society for Engineering Education, 2019 A Literate Programming Approach for Hardware Description Language Instruction INTRODUCTION Digital devices are ubiquitous in modern life.
    [Show full text]
  • Literate Programming and Reproducible Research
    JSS Journal of Statistical Software January 2012, Volume 46, Issue 3. http://www.jstatsoft.org/ A Multi-Language Computing Environment for Literate Programming and Reproducible Research Eric Schulte Dan Davison University of New Mexico Counsyl Thomas Dye Carsten Dominik University of Hawai`i University of Amsterdam Abstract We present a new computing environment for authoring mixed natural and com- puter language documents. In this environment a single hierarchically-organized plain text source file may contain a variety of elements such as code in arbitrary program- ming languages, raw data, links to external resources, project management data, working notes, and text for publication. Code fragments may be executed in situ with graphical, numerical and textual output captured or linked in the file. Export to LATEX, HTML, LATEX beamer, DocBook and other formats permits working reports, presentations and manuscripts for publication to be generated from the file. In addition, functioning pure code files can be automatically extracted from the file. This environment is implemented as an extension to the Emacs text editor and provides a rich set of features for authoring both prose and code, as well as sophisticated project management capabilities. Keywords: literate programming, reproducible research, compendium, WEB, Emacs. 1. Introduction There are a variety of settings in which it is desirable to mix prose, code, data, and compu- tational results in a single document. Scientific research increasingly involves the use of computational tools.
    [Show full text]
  • Literate Programming in the Encyclopedia of Computer Science, A
    Literate Programming in The Encyclopedia of Computer Science, A. Ralston and E. D. Reilly and D. Hemmendinger, eds., 4th edition, 1000{1002, Nature Publishing Group, 2000. For articles on related subjects see Documentation, Macro-instruction, Pretty-printing, Structured Programming,TEX. A programmer finds documentation difficult enough without trying to make it correspond to the program! Literate programming is a system of combining program and internal documentation, so that both may be developed closely together with ease. Various automatic aids to readability are provided, such as substantial cross-referencing and indexing, pretty printing and so on. Special macro processing allows the program to be written in any order to improve and simplify the exposition; macros are automatically numbered so that their usage is easily cross-referenced. An important point is that a literate programming system converts the doc- umentation and code into beautifully typeset material with no additional effort by the programmer. All features combine to simplify and encourage the docu- mentation process and to keep it in very close correspondence with the actual program. Efficient means are provided to extract the program code from the literate program so that it may be compiled or processed in the usual ways. @* Insert sort Extract from the source This is the standard insert sort algorithm. of a literate program | Assumes a sentinel at $a[0]$. illustrating interleaving @p of code, documentation for i := 2 to N do and macros. begin v := a[i]; j := i; @<Insert...@> The @ signs are this end system's convention for @ introducing various @<Insert $v$ in the array@>= literate programming while a[j-1]>v do features.
    [Show full text]
  • Research Tools and Methods for the Mathematical Science Lecture 5: Good Code and Data
    Research Tools and Methods for the Mathematical Science Lecture 5: Good Code and Data Matthew Roughan <[email protected]> http://www.maths.adelaide.edu.au/matthew.roughan/ Lecture_notes/ResearchToolsCourse/ School of Mathematical Sciences, University of Adelaide May 12, 2015 Proof by clever variable choice: "Let A be the number such that this proof works. " Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live. Rick Osborne Matthew Roughan (School of Mathematical Sciences, UniversityResearch of Adelaide) Tools May 12, 2015 2 / 32 Coding well readability [BF12] Good variable names [BF12, Kim10] Good comments [BF12, Eva10, Hen10] I clear and helpful I concise (don't comment x = x + 1) I remember the compiler doesn't check comments! Layout matters [Fre10, Kim10] I we're good at pattern recognition, and layout helps I modern editors usually make it easy I e.g. F indentation F whitespace (in formulae) F bracket placement Matthew Roughan (School of Mathematical Sciences, UniversityResearch of Adelaide) Tools May 12, 2015 3 / 32 Coding well DRY Accumulate idioms. Epigrams in Programming, 10., Alan Perlis DRY = Don't Repeat Yourself reuse tested code if a value is used more than once create a variable if a routine is used more than once create a procedure Have it in one place means it will be consistent, and easy to change the \single source of truth" principle Matthew Roughan (School of Mathematical Sciences, UniversityResearch of Adelaide) Tools May 12, 2015 4 / 32 Coding well Go To Statement Considered Harmful [Dij68] maybe the rule has been interpreted too strongly, but goto statements I increase inter-dependence I create multiple (different) pathways to a single point in the code I make it harder to read the code linearly Please don't fall into the trap of believing that I am terribly dogmatical about [the go to statement].
    [Show full text]