Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
About using GOTO . . .
#21
I actually like line numbers. I just wish Basic's line numbers were more like fortran's statement numbers. (And of course it's just a matter of preference. It's only computer "science" theorists who keep insisting on trying to turn their preferences into laws of nature.)
ravelling Curmudgeon
(geocities sites require copying and pasting URLs.)
I liked spam better when it was something that came in a can.
Windows should be defenestrated.
Reply
#22
line numbers and GOTO mixes well in small, optimized, complicated routines that only you know or should know how to make. Smile
Peace cannot be obtained without war. Why? If there is already peace, it is unnecessary for war. If there is no peace, there is already war."

Visit www.neobasic.net to see rubbish in all its finest.
Reply
#23
programs) complicated routines too. Smile
ravelling Curmudgeon
(geocities sites require copying and pasting URLs.)
I liked spam better when it was something that came in a can.
Windows should be defenestrated.
Reply
#24
GOTO bad... :evil: there are ways to make programs that don't run out of stack while not using GOTO. As a group we should try to use our great programming knowledge to remove this archaic feature rather than be drawn in by its evil powers... :wink: :wink:
Reply
#25
As I told before, GOTO is still useful. Imagine yourself in the 27 nested loops I told you. It is clear that you can exit completely if you set correctly the exit conditions of each loop, but exiting directly is faster. I consider it good to keep existing, it is a good short-cut. What is bad about GOTO is using it when it is uncalled for and there is a loop structure which works better and looks clearer.
SCUMM (the band) on Myspace!
ComputerEmuzone Games Studio
underBASIC, homegrown musicians
[img]http://www.ojodepez-fanzine.net/almacen/yoghourtslover.png[/i
Reply
#26
I was reading a thread on this on a C board, and the conclusion was: Goto is not bad, you just must use it properly, and anything that you use goto to do can be solved in someother way.

Just dont overuse it.
b]Hard Rock[/b]
[The Stars Dev Company] [Metal Qb flopped] [The Terror]
Stop Double Posts!
Whats better? HTML or Variables?
Reply
#27
(It's alternatives might be though.) If you don't want to use it, don't...for whatever ridiculous reason. I've been using it since 1974 and have no intention of stopping because illiterate people can't deal with it. (And someone who programs in QB and using the word "archaic" is in the position of the nitwit living in a glass house throwing stones. Smile )
ravelling Curmudgeon
(geocities sites require copying and pasting URLs.)
I liked spam better when it was something that came in a can.
Windows should be defenestrated.
Reply
#28
Don't take programming advice from Glenn, you may take math or physics advice from but, but never programming.

There is nothing to discuss here, humans aren't computers. You don't use goto for the simple reason that it very hard to follow code that jumps from one place to another. That's what's called spagehtti code and Glenn is an expert on it.

It simply is bad programming practice, and in a 1-2 years or so when you'll look back on your code you'll think the same. It's very annoying trying to read bad code, even if it's your own you're looking back on. I don't know any case where using goto gives you any advantage from using an if statement or select case. I'm not saying that there isn't cases where you can only use goto. But such cases are very rare and very special. I doubt yours is one.

And becuase someone codes in C it doesn't he/she is an expert. There are plenty of n00bs in C too.
oship me and i will give you lots of guurrls and beeea
Reply
#29
I don't have any problem following code with GOTO statements in them. Just because you and other nitwits do doesn't mean other people have to. (That's a concept that I've never noticed you to understand.) Moreover, my compilers don't have trouble reading them--and compilers are what programs are written for, not people. Comment statements are for *people* to read. (Without fail, everytime I've heard someone complaining that they couldn't understand a program because it contained GOTO statements, the real problem turned out to be that they didn't have the qualifications to understand the program in the first place.)

There'd be a lot less junk programs lying around if the confused people calling themselves programmers would worry more about the computer reading their code and less about people reading it.

Further, if you're so lamebrained that you think it's particularly difficult to write code impossible for humans to follow when not using GOTO statements, I have some REXX programs that'll give you nightmares.

And, you damn bonehead, I wasn't giving anybody any programming advice. I don't give a hill of rat waste how other people program. I just wish other people would do likewise and mind their own business and keep *their* advice to themselves. (When I want someone's opinion, I tell them what it is first.)
ravelling Curmudgeon
(geocities sites require copying and pasting URLs.)
I liked spam better when it was something that came in a can.
Windows should be defenestrated.
Reply
#30
heeh
oship me and i will give you lots of guurrls and beeea
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)