Considered harmful

Considered harmful is a part of a phrasal template "X considered harmful". , its snowclones have been used in the titles of at least 65 critical essays in computer science and related disciplines. Its use in this context originated with a 1968 letter by Edsger Dijkstra published as "Go To Statement Considered Harmful". Considered harmful was already a journalistic cliché used in headlines, well before the Dijkstra article, as in, for example, the headline over a letter published in 1949 in The New York Times: "Rent Control Controversy / Enacting Now of Hasty Legislation Considered Harmful". Considered harmful was popularized among computer scientists by Edsger Dijkstra's letter "Go To Statement Considered Harmful", published in the March 1968 Communications of the ACM (CACM), in which he criticized the excessive use of the GOTO statement in programming languages of the day and advocated structured programming instead. The original title of the letter, as submitted to CACM, was "A Case Against the Goto Statement", but CACM editor Niklaus Wirth changed the title to "Goto Statement Considered Harmful". Regarding this new title, Donald Knuth quipped that "Dr. Goto cheerfully complained that he was always being eliminated." Frank Rubin published a criticism of Dijkstra's letter in the March 1987 CACM where it appeared under the title "'GOTO Considered Harmful' Considered Harmful". The May 1987 CACM printed further replies, both for and against, under the title "'"GOTO Considered Harmful" Considered Harmful' Considered Harmful?". Dijkstra's own response to this controversy was titled On a Somewhat Disappointing Correspondence. (Full proposal text was included in post-meeting distribution; see summary.) This article is the namesake of a Cat-v.org Random Contrarian Insurgent Organization, which maintains a directory of "considered harmful" articles and hosts some Plan 9-related software. (Rob Pike was a main figure in the creation of Plan 9 and wrote extensively on bad designs found in UNIX.) See C shell.

About this result

This page is automatically generated and may contain information that is not correct, complete, up-to-date, or relevant to your search query. The same applies to every other page on this website. Please make sure to verify the information with EPFL's official sources.

Related concepts (4)

Related courses (4)

Related lectures (46)

Seifert van Kampen: demonstration and relationship with rectangles

Covers the demonstration of Seifert van Kampen theorem and the relationship with rectangles and paths.

General Mechanics: Inverted Classroom

Covers general mechanics in an inverted classroom setting, including quizzes on spheres and cylinders rolling without slipping.

Lattice Dynamics: Vibrational Modes and Symmetry Relations

Explores lattice dynamics, lattice vibrations' properties, and their impact on heat, specific heat, thermal expansion, and thermal conductivity.

MATH-225: Topology

On étudie des notions de topologie générale: unions et quotients d'espaces topologiques; on approfondit les notions de revêtements et de groupe fondamental,et d'attachements de cellules et on démontre

CIVIL-430: Concrete bridges

Ce cours traite les principaux aspects de la conception et du dimensionnement des ponts en béton armé et précontraint. L'accent est mis sur les ponts poutres. Etude des aspects suivants : optimisation

CS-423: Distributed information systems

This course introduces the key concepts and algorithms from the areas of information retrieval, data mining and knowledge bases, which constitute the foundations of today's Web-based distributed infor

Goto

Goto (goto, GOTO, GO TO, GoTo, or other case combinations, depending on the programming language) is a statement found in many computer programming languages. It performs a one-way transfer of control to another line of code; in contrast a function call normally returns control. The jumped-to locations are usually identified using labels, though some languages use line numbers. At the machine code level, a goto is a form of branch or jump statement, in some cases combined with a stack adjustment.

Control flow

In computer science, control flow (or flow of control) is the order in which individual statements, instructions or function calls of an imperative program are executed or evaluated. The emphasis on explicit control flow distinguishes an imperative programming language from a declarative programming language. Within an imperative programming language, a control flow statement is a statement that results in a choice being made as to which of two or more paths to follow.

Considered harmful