16 Aug
2007
16 Aug
'07
8:59 p.m.
From: brian at quarterbyte.com> To: cctalk at
classiccmp.org> Date: Thu, 16 Aug 2007 10:25:30 -0700> Subject: Re: Shifting
meanings: "Spaghetti Code"?> > > "... It is also easier to debug
because it does not use the > > structures of nested if-then-else statements known
as spaghetti code > > popular in conventional programming languages.">
...> > When did the meaning change?> > It hasn't. Let's just say that
the quoted speaker has > his own take on things.> > http://www.vsmerlot.com/>
> Click the "Wasn't the GOTO" link to see what he's> talking
about.> > Then take a look at the QuickSort example, to see how he's> brought
new clarity to the ghastly confusion of the> usual coded implementation.> >
Hi
State machines have their place. A calculator is a good
example. It is too bad that not all software makes sense
as a state table, just as an all OOP solution can be
clumsy.
Some of the best software I've seen was written by a friend.
It was for a Reed-Solomon error correction. When he showed
the code to his manager, the manager said he sent the wrong
file. What the manager thought he saw was the specification
for the code. What he really saw was the actual code.
When code is written that well, anyone can maintain it.
I've seen bad spaghetti code done in most any language.
The worst was still in BASIC.
Dwight
_________________________________________________________________
Find a local pizza place, movie theater, and more?.then map the best route!
http://maps.live.com/default.aspx?v=2&ss=yp.bars~yp.pizza~yp.movie%20th…