Thankfully, spaghetti is inherently harder to create in xTalk languages,
since you can't use labels as in Basic, COBOL, etc. You should *see*
what some people have done! During the 70's we used to jokingly call it
"organic programming, man!"
Assuming that spaghetti code is created by folks who don't know any
better, it makes me think: in software design and implementation,
simplicity is often harder to create than complexity.
Richard Gaskin wrote:
>
> >What is spaghetti code and how should one avoid it?
>
> "Spaghetti code" is code written in a convoluted or otherwise
> hard-to-follow manner. Sloppy variable naming practices, not breaking
> routines down into separate handlers enough, or into two many, zero
> comments, etc.
>
> For some tips on avoiding spaghettiism, check out:
>
> http://www.fourthworld.com/Research/ScriptStyle.html
>
> - Richard Gaskin
> Fourth World
> Multimedia Design and Development for Mac, Windows, UNIX, and the Web
> _____________________________________________________________________
> [EMAIL PROTECTED] http://www.FourthWorld.com
> US: 800-288-5825 Int'l: 323-225-3717 Fax: 323-225-0716
--
Phil Davis
------------------
[EMAIL PROTECTED]
