spaghetti code is vastly underestimated. It is actually an advanced programming technique. You see, even though you have been told that it is a disgrace to the programmer to write such code, you have been lied to. In fact, I can present you with some reasons for it being good and I''m an expert. 1) Spaghetti code is much easier to write b/c goto statements are simpler that while loops and thealike 2) Spaghetti code is easier to read b/c you can just trace the goto statements whereas when you write strutcured code you have to follow the loops etc. 3) Spaghetti code is more natural b/c assembly is spaghetti code and you know what it translates to. Trust me on this. I''ve been programming for 15 yrs and i only use spaghetti code. it works.

lol

hmm...I don''t know anybody whose programmed for 15 years that would just decide one day to sign up on a message board and advocate spaghetti programming. You aren''t very convincing.

If you are trying to start a war, then you''ve probably got one.

If you write spaghetti code then you''ve probably never worked in a team before. Structured programming is fine if you are the only one working on that module, or that piece of code, but soon as you step foot in a office with 25+ very stressed developers working on several projects at once, the last thing they want to see is a load of unstructured crap and have to waste an hour working out why the f*ck you''ve used goto''s.

As for the statement: 3) Spaghetti code is more natural b/c assembly is spaghetti code and you know what it translates to. That is absolute crap. Assembly isn''t spaghetti code, assembly is the most structured code going. You know exactly what is going on with Assembly since you coded it in the first place. With most compilers, it is down to the whims of the compiler writers how the code translates to assembly since they are largely closed doors (with a couple of exceptions).

There''s several books on writing structured code out there which people heartily recommend. Since my project work was mainly done in small groups of 3-4 people at University, I don''t own nor have I read them. Since a *lot* of people recommend them, I guess that they must have a valid point, which is more than I can say about your 3.



Stay Lucky, Graham "Mournblade" Reeds,
ICQ: 30514803
http://homepage.dtn.ntl.com/grahamr

quote:

---

Original post by exprt_prg

spaghetti code is vastly underestimated. It is actually an advanced programming technique. You see, even though you have been told that it is a disgrace to the programmer to write such code, you have been lied to. In fact, I can present you with some reasons for it being good and I'm an expert.

1) Spaghetti code is much easier to write b/c goto statements are simpler that while loops and thealike
2) Spaghetti code is easier to read b/c you can just trace the goto statements whereas when you write strutcured code you have to follow the loops etc.
3) Spaghetti code is more natural b/c assembly is spaghetti code and you know what it translates to.

Trust me on this. I've been programming for 15 yrs and i only use spaghetti code. it works.

---

Lets get the facts straight, number 1, you're not a 15 year programmer. Number 2, you're probably just some 15 year old kid who thinks spaghetti code is easier because you don't know any other way of programming. Number 3, Assembler isn't spaghetti, there are no gotos in assembler, the JMP, JNZ, JZ, JNE, JE, etc are jumps according to a tested value( ie: an IF statement ) if you think I'm wrong, get a damn book and check it out. I've programmed a number of apps in ASM when DOS was still the OS of choice and I can tell you that I didn't have any problem at all reading the code and most of the guys on my team at that point were able to read the code without any problem either. I have one more thing to say about ASM, if you know how to code correctly in ASM, you almost don't have to use any JMP, JNZ, JZ, etc in your code. Now a programmer that has been on the scene for 15 years should know all of this and not post dumb unsupported facts that spaghetti code is good.

Oh and spaghetti code is not verry optimized, you lose time when executing your program and it's prone to having troubles debugging. If you want a really optimized method of coding that alot of expert firms use do a search for Extreme Programming in yahoo and you'll find out what a real programming method is. I personally don't use it but it's one of the methods that is vastly used in interprise. Besides, if spaghetti code was good, how come no one that I know use it anymore. I'm talking about the same people who started programming in GWBASIC when I was a kid, at that time, we didn't know better. We learned after about 2 months that gotos sucked and we never used it afterwards. Anyhow, I think that's enough wasted time. Hope you get the drift. If not, I recommend getting a real life.



"And that's the bottom line cause I said so!"

Cyberdrek
Headhunter Soft
A division of DLC Multimedia



Edited by - cyberdrek on April 19, 2001 10:04:30 AM

Your either kidding or your a VB programmer. Either way ick.



Joseph Fernald
Software Engineer
Red Storm Entertainment.
------------------------
The opinions expressed are that of the person posting
and not that of Red Storm Entertainment.

quote:

---

Original post by evaclear

Your either kidding or your a VB programmer. Either way ick.



Joseph Fernald
Software Engineer
Red Storm Entertainment.
------------------------
The opinions expressed are that of the person posting
and not that of Red Storm Entertainment.

---

Sorry to break the thread here but I was just wondering, what projects did you work on for Red Storm Entertainment? Yes, I''m just curious.



"And that''s the bottom line cause I said so!"

Cyberdrek
Headhunter Soft
A division of DLC Multimedia

Ever read "A Modest Proposal" by Jonathan Swift.

When I read this post I thought the only way somebody would make comments this backwards was inorder to sarcastically make a point.

Take it from someone who spent some time looking at really old (20+ years) COBOL code... control structures (if statements, while loops) are your friends. Same thing for procedures and sensible, accurate commenting. Goto''s in and of themselves are not evil, but the potential for misuse is very great and modern programming languages offer safer alternatives.

Spaghetti code is code that uses goto to jump around in a program that isn''t laid out in any particular, logical order. Early programmers often had to use the goto statement, but if the code was logically organized, well commented and made intelligent use of the goto statement then it was not spaghetti code.

L8r,
Murph


--------------------------------
Screw you guys! I''m going home.

Come on all, its quite obvious that the person joined up pretty much just to post this - look at the member since field.

Although, it was amusing for a time.

-Mezz

I am not sure what exprt_prg mean about spagetti programming. Does he really mean using goto. But reading his post i think there is some truth. When i program i hate having to think of this and that. There is so many solution to a single problem that when you start thinking of them which one is the best you can end up using more time then it is worth. Picking the first solution that come in your mind if often a good chose. I am not thinking of the back-bone problems of he project. You can''t go around doing analyse/design on those. This is more for leaves-problem and to problems that is small.

quote:

---

Original post by murph

Ever read "A Modest Proposal" by Jonathan Swift.

---

Just what I was thinking. I''m really amazed that people doesn''t understand that this is just a joke. Ofcourse, I can''t be sure, but ironi is my best friend so better laugh then flame.