
	Where results make sense

Topic: Go To Statement Considered Harmful

	Go To Statement Considered Harmful
		For a number of years I have been familiar with the observation that the quality of programmers is a decreasing function of the density of go to statements in the programs they produce.
		The unbridled use of the go to statement has an immediate consequence that it becomes terribly hard to find a meaningful set of coordinates in which to describe the process progress.
		The go to statement as it stands is just too primitive; it is too much an invitation to make a mess of one's program.
	www.cs.utsa.edu /~wagner/CS3723/nogoto/harm2.html (1231 words)

	"Considered Harmful" Essays Considered Harmful
		Because "considered harmful" essays are, by their nature, so incendiary, they are counter-productive both in terms of encouraging open and intelligent debate, and in gathering support for the view they promote.
		Usually such "considered harmful" essays are intended to draw attention to a little-known subject about which the author is passionate, or to highlight what the author feels to be a poor decision by someone else.
		The writing of a "considered harmful" essay often serves to inflame whatever debate is in progress, and thus makes it that much harder for a solution to be found through any means.
	www.meyerweb.com /eric/comment/chech.html (1229 words)

	Considered harmful - Wikipedia, the free encyclopedia
		In computer science and related disciplines, "considered harmful" is a phrase popularly used in the titles of diatribes and other critical essays.
		It originates with Edsger Dijkstra's letter "Go To Statement Considered Harmful", published in the March 1968 Communications of the ACM, in which he criticized the excessive use of the GOTO statement in the programming languages of the day and advocated structured programming instead.
		Structured programming is not as widely debated in contemporary computer science, but the pithy and adaptable phrase "X considered harmful" (actually the invention of the ACM editor Niklaus Wirth, and not Dijkstra) continues to be used to indicate that an article contains controversial and strongly asserted views.
	en.wikipedia.org /wiki/Considered_harmful (221 words)

	Goto (command) - Wikipedia, the free encyclopedia
		GOTO is a command found in many programming languages which instructs the computer to jump to another point in the computer program, specified by a label or line number.
		In that letter Dijkstra argued that unrestricted GOTO statements should be abolished from higher-level languages because they complicated the task of analyzing and verifying the correctness of programs (particularly those involving loops).
		Donald Knuth's Structured Programming with go to Statements (see external links) considers some of the places where GOTO may be the appropriate tool.
	en.wikipedia.org /wiki/Go_to (539 words)

	jargon, node: considered harmful (Site not responding. Last check: 2007-10-11)
		considered harmful /adj./ Edsger W. Dijkstra's note in the March 1968 "Communications of the ACM", "Goto Statement Considered Harmful", fired the first salvo in the structured programming wars (text at http://www.acm.org/classics).
		Amusingly, the ACM considered the resulting acrimony sufficiently harmful that it will (by policy) no longer print an article taking so assertive a position against a coding practice.
		In the ensuing decades, a large number of both serious papers and parodies have borne titles of the form "X considered Y".
	www.jargon.net /jargonfile/c/consideredharmful.html (119 words)

	TechThemes: ... Considered Harmful (Site not responding. Last check: 2007-10-11)
		Prominent computer scientist Edsger Dijkstra (the pioneer of structured programming) submitted an article "A case against the goto statement", which was published in the March 1968 edition of the Communications of the ACM (Association for Computing Machinery).
		Not surprisingly the infamous "… Considered Harmful" letter had not won the argument on its own, and Dikstra was still making his case years later.
		Before using those two words, authors should consider whether their idea is anywhere near as good as structured programming, whether they have Dijkstra-like ability to sustain the argument for a long time, and whether "… Considered Harmful" is the best way to influence people.
	member.melbpc.org.au /~tgosbell/articles/harmful (1041 words)

	Go To Statement Considered Harmful: A Retrospective
		However, he is attempting to go beyond simply tracking the location of the current execution thread, to making an explicit connection between a statement in the source code text and a program execution state.
		The number of statement pointers needed is simply the number of procedure calls that are currently active at a given point in the execution, i.e., the depth of the call stack.
		The set of flow control statements and clauses provided should be powerful and flexible enough so that a programmer can express his ideas clearly and succintly without having to resort to the use of extraneous control variables or to rearrange his code unnaturally just to get around the syntactical restrictions of the language.
	david.tribble.com /text/goto.html (8110 words)

	Scott Rosenberg’s Wordyard » Blog Archive » Code Reads #2: Dijkstra’s “Go To Statement ...
		The title of Edsger Dijkstra’s 1968 “Go To Statement Considered Harmful” is among the best-known phrases in the history of programming.
		His argument is straightforward enough: “Go to” is problematic because, in jumping arbitrarily from one spot in a process to another, it fails to maintain context (or “state awareness”) — and that invites messes.
		“Go To Considered Harmful” ushered in a considerable debate over the shape and nature of structured programming, which produced at least two key documents — Dijkstra’s 1969 “Notes on Structured Programming” and Donald Knuth’s 1974 “Structured Programming with go to Statements” (thanks to Jim Jinkins for the suggestion).
	www.wordyard.com /2006/10/10/dijkstra-goto (5765 words)

	Green Hat Journal: IF considered harmful (Site not responding. Last check: 2007-10-11)
		In the spirit of Dijsktra's Go To Statement Considered Harmful, I believe conditional statements within a function are undesirable because it makes the program too rigid and inflexible.
		Predicate dispatching is the best way to implement a flexible language that doesn't rely on conditionals buried in the function body.
		Rather than rely strictly on conditional statements, the conditionals should be in the function signature, much as it is for typed OO (types) and functional (pattern matching) languages.
	rover.cs.northwestern.edu /~surana/blog/past/000195.html (276 words)

	Csh Programming Considered Harmful
		Consider the common C construct: if (p andand p->member) Undefined variables are not fatal errors in the Bourne shell, so this issue does not arise there.
		Consider: % alias foo 'echo hi' ; foo foo: Command not found.
		Consider this statement: exit (i) Of course, they really meant exit (1) or just exit 1 Either shell will complain about this.
	www.faqs.org /faqs/unix-faq/shell/csh-whynot (2440 words)

	Concerning Dholgyal with reference to the views of past masters and other related matters
		Even if it were considered to have been written by the Fifth Dalai Lama, it must have been written during the initial period (of this affair) when he has stated himself that he tried skilfully to employ peaceful methods.
		Considering how inappropriate was this turn of events he issued an edict to the assembly of monks that as there had been no tradition of propitiating worldly spirits and protectors within the premises of this seat of learning since the time of Je Tsongkhapa, henceforth, nobody would be allowed to engage in such activities.
		This is why the statements in the letters of enquiry sent by the previous Dalai Lama to Kyabje Phabongkha Rinpoche, stating that ‘physically putting on the three robes and then taking refuge in ghostly spirits is not correct”, turns out to be absolutely accurate.
	www.dalailama.com /page.155.htm (9115 words)

	Steven Engelhardt: "Considered Harmful" Considered Harmful (Site not responding. Last check: 2007-10-11)
		The phrase was originally popularized by the computer science icon Edgser W. Dijkstra in his oft-referenced paper Go To Statement Considered Harmful, it has become a blemish in the technical community.
		If you are considering using "Considered Harmful" in your paper, please rethink your decision.
		A simple Google search of the phrase considered harmful turns up an enormous number of links.
	www.deez.info /sengelha/writings/considered-harmful (149 words)

	AMA (CSAPH) Report 9 of the Council on Scientific Affairs (I-99) Full Text
		In the belief that elements of their Consensus Statement are aligned with current American Medical Association (AMA) policy, this group has asked for AMA endorsement of the Consensus Statement.
		In previous communications from the AMA, the Physician Leadership group was informed that their Consensus Statement would be considered in the context of an ongoing AMA/American Bar Association initiative intended to produce a joint policy paper on drug abuse.
		The Consensus Statement acknowledges that "alcohol causes a substantial burden of disease and antisocial behavior which requires vigorous, widely accessible treatment and prevention programs;" this is supported by numerous policies (eg, H-30.958, H-30.972, H-30.
	www.ama-assn.org /ama/pub/category/13551.html (1230 words)

	Go To Statement Considered Harmful - Waikato Linux Users Group
		For a number of years I have been familiar with the observation that the quality of programmers is a decreasing function of the density of GoTo statements in the programs they produce.
		The unbridled use of the GoTo statement has an immediate consequence that it becomes terribly hard to find a meaningful set of coordinates in which to describe the process progress.
		The GoTo statement as it stands is just too primitive; it is too much an invitation to make a mess of one's program.
	www.wlug.org.nz /GoToStatementConsideredHarmful (1328 words)

	Untitled
		The famous letter that sparked the original controversy was Edsger Dijkstra's "Go To Statement Considered Harmful" in the March 1968 Communications of the ACM.
		Donald Knuth's marvelous article, "Structured Programming with go to Statements," gives several examples of cases in which using gotos is slower and larger (Knuth 1974).
		Consider all the factors that have been presented, then make a project-wide decision about which method to favor in your programs.
	www.stevemcconnell.com /ccgoto.htm (3054 words)

	Weblogging Considered Harmful
		Have any of these companies considered the possibility that if they showed some respect for the consumer, the consumer might show some respect for them? Instead, media corporations seem to be treating their customers with complete and utter contempt by basing their distribution systems on the idea that all of said customers are potential crooks.
		The few people to whom I've shown a new Considered Harmful design have been pretty positive about it, and this existing page is pretty bland, but I still worry.
		My parents are going to West Virginia on an upcoming trip, so I'm trying to find any links on the ancient Celtic artifacts found there.
	c_harmful.pitas.com (1515 words)

	2005 Legislative Report
		SB 89, “Mutual Dependence Benefits Contract Act,” sought to ameliorate some of the harm done by last fall’s passage of a constitutional amendment prohibiting same-sex marriage.
		Also, for the ninth year in a row, legislators failed to amend the state’s hate crimes law, and many believe that as in past years, the failure of HB 50, “Criminal Penalty Amendment,” was due in large part to the inclusion of sexual orientation in the bill’s list of biases.
		HB 260 S3, “Amendments Related to Pornographic and Harmful Materials,” seeks to put the government in charge of what should be the responsibility of parents—namely identifying and restricting Internet sites that are inappropriate for children.
	www.acluutah.org /05legrep.htm (1702 words)

	Statement-Level Control Structures (Site not responding. Last check: 2007-10-11)
		In Python as we saw in an earlier lab the offside rule is used to avoid the need for an ending keyword.
		statements provide multiway branching based on the value of a particular expression.
		statement is one that causes a statement or collection of statements to be executed zero, one, or more times.
	www.cs.montana.edu /courses/355/lectures/chapter8 (535 words)

	Hallvard's Blog: The with-statement considered harmful
		As have been mentioned by several people in several places (newsgroups, blogs, QC etc.) Delphi's with-statements can be harmful to the readability, maintainability and robustness of your code.
		Much like the problem with potential duplicate identifiers from used unit scopes, the with-statement problem could be mitigated by enhancing the compiler to produce Warnings for ambiguous with-statements.
		IMO, if we could have this kind of warning for with-statements, it would be the first steps towards patching one of the very few sorespots of the otherwise elegant Object Pascal language.
	hallvards.blogspot.com /2004/08/with-statement-considered-harmful.html (590 words)

	Course Technology--InfoWeb: GOTO
		Dijkstra opened a can of worms when he submitted his famous letter, "Go To Statement Considered Harmful" to the Communications of the ACM in 1968.
		Control Statements At this page from the Professional Programmer's Guide to Fortran 77, you can see how the go to statement fits into the context of other program control structures.
		In general, the go to statement is considered obsolete or deprecated in most programming languages.
	www.cciw.com /content/goto.html (192 words)

	Edgser W. Djkstra
		In 1968 Edsger Dijkstra(7) laid the foundation stone in the march towards creating structure in the domain of programming by writing, not a scholarly paper on the subject, but instead a letter to the editor entitled "GO TO Statement Considered Harmful".
		The next problem that computer engineers must deal with that Dijkstra recognized was the "dining philosophers problem." In this problem, five philosophers are sitting at a table with a bowl of rice and a chopstick on either side of the bowl.
		This means that the more GO TO statements there are in a program the harder it is to follow the program's source code.
	www.thocp.net /biographies/dijkstra_edsger.htm (881 words)

	STRUCTURED PROGRAMMING CONSIDERED HARMFUL
		This mini-paper was written by myself and Bill Slater when we were both Graduate students at the University of Texas at Arlington in the mid-to-late 70's.
		We intended it purely as a spoof of the "X Considered Harmful" articles that seemed to be all the rage at that time.
		One of the earliest tenets of SP was that the BRANCH control structure, epitomized by FORTRAN's GOTO statement, is inherently "dangerous".
	www.modell.com /Magery/SPharmful.html (1277 words)

	Goto - Art History Online Reference and Guide
		However, others believed that even though the use of GOTO is often bad practice, there are some tasks that cannot be straightforwardly accomplished in many programming languages without the use of GOTO statements, such as exception handling.
		One famous criticism of GOTO is a letter by Edsger Dijkstra called Go To Statement Considered Harmful.
		Donald Knuth's Structured Programming with goto Statements considers some of the places where GOTO may be the appropriate tool.
	www.arthistoryclub.com /art_history/Goto (518 words)

	Ch.13 Goto Statement Considered Harmful
		In 1991, a.EXE contributor (who shall remain nameless) highlighted the GOTO statement as 'the greatest source of ill-considered hysteria' in the domain of programming standards.
		More than two decades earlier, in 1968, Edsger Dijkstra called, in what is arguably the most famous 'letter to the editor' in I.T. publishing history, for the abolition of GOTO from the programmer's arsenal.
		Break terminates a loop unconditonally and jumps to the first statement after the loop, while Continue skips to the top of the loop to start the next iteration immediately.
	www.keysound.com /html/ch_13_goto_statement_considere.htm (718 words)

	E.W. Dijkstra Archive: A Case against the GO TO Statement. (EWD215)
		E.W. Dijkstra Archive: A Case against the GO TO Statement.
		Since a number of years I am familiar with the observation that the quality of programmers is a decreasing function of the density of go to statements in the programs they produce.
		Later I discovered why the use of the go to statement has such disastrous effects and did I become convinced that the go to statement should be abolished from all "higher level" programming languages (i.e.
	www.cs.utexas.edu /users/EWD/transcriptions/EWD02xx/EWD215.html (850 words)

	Web Wise Seniors
		These e-mails are considered essential to the provision of the service you have requested.
		You will not be able to choose to unsubscribe to these mailings, as they are considered a part of the service you have chosen.
		If there are material changes to this Statement or in how Web Wise Seniors will use your personally identifiable information, Web Wise Seniors will prominently post such changes prior to implementing the change.
	www.webwiseseniors.com /PRIVACYPOLICY1.asp (2567 words)

	Weblogging Considered Harmful
		[very common] Edsger W. Dijkstra's note in the March 1968 "Communications of the ACM", "Goto Statement Considered Harmful", fired the first salvo in the structured programming wars (text at http://www.acm.org/classics).
		(Years afterwards, a contrary view was uttered in a CACM letter called, inevitably, "`Goto considered harmful' considered harmful'").
		This page is the fault of Brennan M. O'Keefe.
	web.pitas.com /c_harmful/archive.html (153 words)

	Considered Harmful
		...why are there going to be at least ten sequels? Game company Square has announced the next three episodes (IX, X, and XI) of its Final Fantasy console RPG series.
		As far as IX goes, I don't mind going back to roots high fantasy from the science-fantasy settings of the games I'm familiar with, but I'm disappointed that Square may be going for cartoony "super deformed" characters rather than the more realistic models of VIII.
		'Considered Harmful' is one; 'Scratch Monkey' is another.
	web.pitas.com /c_harmful/arch013100.html (2110 words)

Try your search on: Qwika (all wikis)