
	Where results make sense

Topic: Spaghetti code

Related Topics

Program loop

Unstructured programming

GOTO

Functional programming

Structured programming

MBASIC

Comparison of C Sharp to Java

Comparison of Java to C Plus Plus

Data structure

Microsoft BASICA interpreter

Microsoft BASIC

Proprietary

Maria Theresa

ISO

GOTO

In the News (Wed 15 Feb 12)

EXECUTIVE POWER

Iran

ANALYSIS

Pakistan

Family compact

	Spaghetti code - Wikipedia, the free encyclopedia
		Spaghetti code is a pejorative term for source code which has a complex and tangled control structure, especially one using many GOTOs, exceptions, threads, or other "unstructured" branching constructs.
		Spaghetti code is an example of an anti-pattern.
		When using the many forms of assembly language (and also the underlying machine code) the danger of writing spaghetti code is especially great.
	en.wikipedia.org /wiki/Spaghetti_code (657 words)

	What is spaghetti code? - a definition from Whatis.com
		Spaghetti code sometimes exists as the result of older code being modified a number of times over the years.
		Another part of the spaghetti analogy is the way that making a change to one part of the code can have unpredictable effects on the rest of the program, just as pulling on one strand of spaghetti can affect other strands of spaghetti that in ways that are not foreseeable.
		Spaghetti code or any type of hard-to-understand code is sometimes referred to as write-only code.
	searchvb.techtarget.com /sDefinition/0,,sid8_gci864593,00.html (308 words)

	Spaghetti code
		Spaghetti code is a pejorative term for code with a complex and tangled control structure, especially one using many GOTOs, exceptions, or other "unstructured" branching constructs.
		It is named after spaghetti because a diagram of program flow tends to look like that.
		Also called kangaroo code because such code has so many jumps in it.
	www.ebroadcast.com.au /lookup/encyclopedia/ka/Kangaroo_code.html (79 words)

	PASCAL Programming: Modular Software Design
		Spaghetti code is the term used for a computer program that is not well structured and tends to have highly tangled flows of data and control.
		Additionally, concise code is easier to maintain because (a) there is less code to examine and modify, (b) there is less probability of making mistakes in modifying the code, and (c) debugging is easier due to limited scope of functionality.
		Spaghetti code is usually written piecewise, in the sense that a programmer might write Lines 1-50 on Monday, Lines 51-107 on Tuesday, and so forth.
	www.cise.ufl.edu /~mssz/Pascal-CGS2462/prog-dsn.html (3066 words)

	Spaghetti code
		Spaghetti code is often not organized and has portions of code that may belong at the bottom of the code at the top of the code or vice versa.
		Spaghetti code is considered bad practice because a program may be more prone to experience errors, and if errors are experienced, it is more difficult to locate what is causing the error to occur.
		Spaghetti code can be reduced by keeping your program organized, always commenting your code, and if possible, breaking your code into sections.
	www.computerhope.com /jargon/s/spaghett.htm (199 words)

	Executing Dynamic Code in .Net
		Its use often resulted in highly unreadable code or worse spaghetti code that was difficult to debug and was very slow.
		Code and data available in one application domain within a single process is not directly accessible from another application domain.
		So if there's code that dynamically uses the JIT compiler to compile code the code will remain in the app domain cached and compiled so only first access is relatively slow.
	www.west-wind.com /presentations/dynamicCode/DynamicCode.htm (4852 words)

	Spaghetti Code: A Sculpture Barnraising
		Spaghetti Code is computer science jargon for a poorly organized program, but the sculpture is actually highly organized.
		Spaghetti Code is constructed of 180 laser-cut, flat, aluminum parts.
		Spaghetti Code has 60 components in the twelve planes of the pentagons of one RID (five per pentagon) and has 120 components in the thirty planes of the squares of a larger concentric parallel RID (four per square).
	www.georgehart.com /spaghetti/spaghetti-code.html (1414 words)

	Big Ball of Mud
		The code exhibits the unmistakable signs of patch after patch at the hands of multiple maintainers, each of whom barely understood the consequences of what he or she was doing.
		Quick-and-dirty coding is often rationalized as being a stopgap measure.
		Code changes more slowly than data, and is the realm of programmers, analysts and designers.
	laputan.org /mud/mud.html (15085 words)

	'Spaghetti Code' makes future upgrades impossible
		Unfortunately, the development may exhibit that the methods under OO are process oriented and the objects are designated as processes, thereby the execution is controlled by object implementation and not by the clients of the objects.
		Moreover, because of the inability to reuse the Spaghetti Code, extension and future upgrades of the system is almost impossible.
		Code clean up will also result in the improvement of the performance as follows: the aim is to achieve a satisfactory structure and so the software team should identify the place where that portion of the performance-critical code exists.
	www.icmgworld.com /corp/news/Articles/RS/feb_0102.asp (861 words)

	Spaghetti Code- GNU Project - Free Software Foundation (FSF) (Site not responding. Last check: 2007-10-11)
		Lasagna code is used to describe software that has a simple, understandable, and layered structure.
		Lasagna code, although structured, is unfortunately monolithic and not easy to modify.
		In ravioli code, each of the components, or objects, is a package containing some meat or other nourishment for the system; any component can be modified or replaced without significantly affecting other components.
	www.gnu.org /fun/jokes/pasta.code.html (295 words)

	Spaghetti Code (Site not responding. Last check: 2007-10-11)
		Code in which control flow is tangled up like Spaghetti.
		As somebody joked above, spaghetti code often is all code that is not our own because it was generated by minds that think differently than us.
		Calling somebody else's code spaghetti code is almost a sure way to start a FlameWar.
	c2.com /cgi/wiki?SpaghettiCode (287 words)

	Rewriting Spaghetti Code
		The requirements are not reliably documented except by the source code itself, which is such a mess that you don't trust yourself to understand it.
		As you wrestle with the code you can become familiar with small pieces of it, recognize what the code is trying to do, and further massage it to achieve a good style.
		Transform the code in a systematic sequence of stages.
	home.swbell.net /mck9/cobol/style/rewrite.html (814 words)

	How to Write Bad Code
		Code that doesn't work at all doesn't satisfy any of the reasons for writing bad code--no one will want it, so no one will be screwed up by it.
		Spaghetti data on the other hand, requires a much larger amount of work to follow.
		Here's a simple bad code technique based on coupling that can be used in any language to really screw things up: It is frequently useful to build a table which is indexed with an enumeration.
	www.exmsft.com /~hanss/badcode.htm (4671 words)

	Anticlue: It is the revenge of the Spaghetti Code
		One of the arguments surrounding the code is that it is spaghetti code.
		I am sorry, but I would beg to state that most of the code in the world today is Spaghetti Code.
		It is a poor argument to exclude a language based on the ability to create spaghetti code.
	www.anticlue.net /archives/000663.htm (309 words)

	Y2K - Winter of Our Disconnect?
		Spaghetti Code is the term programmers use for source code that is too convoluted and big to understand.
		A majority of these programmers have some training, but many are trained on the job and learn as they write code.
		Over the years, new programmers add their own fixes and features, and soon the source code is too big for anyone to understand.
	www.pbs.org /y2kwinter/spaghetti.html (329 words)

	Andy Smith's Blog : Spaghetti, CodeInPage, CodeBehind, and CodeBeside (Site not responding. Last check: 2007-10-11)
		And at the same time that you have this over-seperation of the code and UI, you also have all this code in the UI declaration file, disguised in databinding syntax blocks.
		The code behind file is not reusable, is bound to the aspx file, and is descendant of the Page class, which is not exactly the right choice for BL.
		To me, the code that is in the code inside/code beside/code behind should be nothing more than wiring code.
	weblogs.asp.net /asmith/archive/2004/04/14/112916.aspx (3521 words)

	The Spaghetti Code - boakes.org
		One of the most famous examples of distributed computing logic can be found in the Dining Philosophers problem, which illustrates the need for cooperation if the issues of starvation and deadlock are to be avoided.
		In massively distributed computing, there are myriad global interrelationships between the complex tendrils of code & data and their mutations through time and space.
		Putting the pieces together it dawned on me that the Flying Spaghetti Monster may be preparing to take physical form on Earth, manifested as The Grid of all mankind’s knowledge and computation.
	boakes.org /the-spaghetti-code (484 words)

	DOES DOS STILL LIVE IN WINDOWS XP? -PC VS APPLE (Site not responding. Last check: 2007-10-11)
		XP was based on 2000 code which was based on NT code, which from what I understand was based on VMS code.
		In 1998, Windows NT 5.0 was estimated to have 20 million lines of code; by the time it was renamed Windows 2000 (in 1999) it had between 35 million and 60 million lines of code, depending on who you believe.
		Lines of code: It has been estimated that Windows 2000 Server is encumbered by the complexity of more than 30 million lines of code (other sources say Win 2000 with 29 to 60 million, Windows XP 40 to 50 million).
	www.jmusheneaux.com /index1.htm (6359 words)

	Ravioli code - Wikipedia, the free encyclopedia
		Ravioli code is a type of program structure, characterized by a number of small and (ideally) loosely-coupled software components.
		The term is in comparison with spaghetti code, comparing program structure to pasta; with ravioli (small pasta pouches containing cheese, meat, or vegetables) being analogous to objects (which ideally are encapsulated modules consisting of both code and data).
		Some consider ravioli code to be a good design methodology, especially when the components used are modular, highly interchangeable, well-encapsulated, and providing well-defined interfaces and behavior.
	en.wikipedia.org /wiki/Ravioli_code (171 words)

	Spaghetti-Code LOS Graph Technique (Site not responding. Last check: 2007-10-11)
		The code must be strictly graph-based (a state machine); the only runtime calculations permitted are coordinate translations to the viewer's position.
		The spaghetti code was generated by a program I wrote in Smalltalk.
		The demo code should display a reasonably sane field of view for a random distribution of blocking cells.
	jwelton.v-space.org /discuss/LOSSpaghetti.html (517 words)

	ongoing · On PHP (Site not responding. Last check: 2007-10-11)
		Spaghetti SQL wrapped in spaghetti PHP wrapped in spaghetti HTML, replicated in slightly-varying form in dozens of places.
		Having said that, if you were interested in looking at the code (as an example of some, hopefully, elegant PHP) then I’d be delighted to send you a copy of a standard install subject to it being kept in reasonable confidence (or something, nothing formal).
		When I was done porting a converter (http://hsivonen.iki.fi/php-utf8/) from Mozilla’s code base (the first place where I could find one), I no longer had the time to implement the feature I needed the converter for.
	www.tbray.org /ongoing/When/200x/2006/02/17/PHP (3208 words)

	2.9 State Machines and Indirect Jumps
		We'll just assume that a state machine is a piece of code which (somehow) remembers the history of its execution (its state) and executes sections of code based upon that history.
		Spaghetti code suffers from one major drawback- it's difficult (at best) to read such a program and figure out what it does.
		While it's true that producing some spaghetti code in your programs may improve its efficiency (e.g., destructuring your code, see "Efficient Implementation of IF Statements in Assembly Language" on page 642), doing so should always be a last resort after you've tried everything else and you still haven't achieved what you need.
	webster.cs.ucr.edu /AoA/Linux/HTML/LowLevelControlStructsa3.html (1251 words)

	Where to Put Code in Paradox by Mike Prestwood (Site not responding. Last check: 2007-10-11)
		There are many benefits for coding as low as possible, including the ability to copy objects with code on them from one form to another and still have it work.
		If you later need that same code on another button, convert it to a custom method and move it up the container path to the button's container object.
		Using this general rule of coding as low to the object as possible gives you maximum access to your code and saves you time.
	www.prestwood.com /community/paradox/info/where2code.html (1044 words)

	Information Landscapes and Spaghetti Code (Site not responding. Last check: 2007-10-11)
		Now this may all seem like a strange way to begin a talk entitled "Information Landscapes and Spaghetti Code", which is probably an equally strange title, but I promise to try to tie all this together as we go along.
		Spaghetti and monolithic technologies are not necessarily always bad, but I worry that the technologists among us can be a lot like Minnie.
		It is also hard to disassemble spaghetti and reuse specific noodles in another dish, and a mound of spaghetti, at least in the IT world, can involve a mountain of assumptions.
	librarycog.uwindsor.ca:8082 /artblog/librarycog/1067077701/index_html (4431 words)

	Naming
		Much of the skill in writing unmaintainable code is the art of naming variables and methods.
		If you confuse even yourself with acronymns, secretly write code using meaningful names, then, when the code in working, use the global rename feature of Eclipse to give your variables and methods unintelligible names and acronyms, just the way a mechanical obfuscator would.
		The importance of this rule cannot be overstated: if you fail to adhere to its principles the source code may become flooded with shorter variable names that have a higher vowel/consonant ratio.
	mindprod.com /jgloss/unmainnaming.html (2619 words)

	[No title]
		If one’s code could not be easily read and understood, he/she was judged to be a skilled programmer.
		These additional structures are designed to make code more readable, and make programming more efficient. Describe the comparison of the test value with the listed case values for the purpose of selecting which alternative to execute.
		Stress the fact that a do-while or a do-until loop guarantees that the code in the loop is executed at least once, regardless of the outcome of the test question..
	www.cerritos.edu /Pnguyen/cis103/cis103ch02.doc (1206 words)

	Spaghetti Code, al dente (Site not responding. Last check: 2007-10-11)
		The problem causing code is still there, lurking, until resurrected by another hurried fix.
		Unfortunately the developers, some of whom were drafted to put out earlier fires, must build on some of the mangled code.
		However, it is absolutely criminal to force the development staff to live with that code compromise.
	www.multi-platforms.com /Tips/SpaghettiCode.htm (382 words)

	Application Development Trends - DHL parent untangles 'spaghetti infrastructure'
		Spaghetti infrastructure, as Herr describes it, consists of things like a proliferation of point-to-point interfaces developed for one-off projects that are the antithesis of service-oriented architecture (SOA).
		The problem with spaghetti infrastructure is while one application may speak to second, it takes a whole lot of coding and testing to extend the conversation to a third application.
		Since uncovering the spaghetti, Herr and his Service Oriented Platform (SOP) Group colleagues working with consultants from IONA built an extensible SOA infrastructure on IONA’s Artix extensible enterprise service bus (ESB).
	www.adtmag.com /article.asp?id=10278 (315 words)

	Drawbacks of COBOL-Structuring Tools
		A restructuring tool may produce formally structured code, but it is not likely to produce well-structured code with a good style.
		In order to reproduce the original logic without GO TO, the tool is likely to invent a series of flags and switches to control the flow of execution.
		In various other respects the generated code will almost certainly not conform to your local standards and habits.
	home.swbell.net /mck9/cobol/style/robocode.html (251 words)

	What Is Quality
		Some software is written from scratch with every hack and tweak imaginable, producing the most obfuscated spaghetti code this side of a western...
		If the people writing the code aren't trying to produce good code, then either the process is broken or they are.
		When you use multiple layers of leverage (process, design, code) to accomplish something, as you are talking about here, it's dangerous to focus only on one layer and ignore the others.
	c2.com /cgi/wiki?WhatIsQuality (1286 words)

Try your search on: Qwika (all wikis)