Comments on: Are GOTO Statements Still Dirty? http://datapigtechnologies.com/blog/index.php/are-goto-statements-still-dirty/ A DataPig Technologies Blog Wed, 08 Feb 2012 00:53:00 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Mr. Goto http://datapigtechnologies.com/blog/index.php/are-goto-statements-still-dirty/comment-page-1/#comment-21440 Mr. Goto Thu, 20 Oct 2011 21:25:02 +0000 http://datapigtechnologies.com/blog/?p=1263#comment-21440 Once upon a time there were some programmers who did not use the GoTo statement right. Their code was bad and hard to understand. Then some college professors that never had a real job decided to ban the GoTo and called it bad. They would rather write 10 levels of loops that one GoTo statement would fix. That is GOOD code. Well the secret socieity of Goto is Good is waiting for space aliens with their advanced code techniques to come down to Earth. Have them show man kind GoTo is really Good used the right way! Some day it will happen. Once upon a time there were some programmers who did not use the GoTo statement right. Their code was bad and hard to understand.

Then some college professors that never had a real job decided to ban the GoTo and called it bad. They would rather write 10 levels of loops that one GoTo statement would fix. That is GOOD code.

Well the secret socieity of Goto is Good is waiting for space aliens with their advanced code techniques to come down to Earth. Have them show man kind GoTo is really Good used the right way! Some day it will happen.

]]> By: ross http://datapigtechnologies.com/blog/index.php/are-goto-statements-still-dirty/comment-page-1/#comment-2566 ross Thu, 19 Nov 2009 16:42:52 +0000 http://datapigtechnologies.com/blog/?p=1263#comment-2566 GoTo's are like Beers. If you have to many bad things happen, if you don't allow yourself any, you just being prudish, but at the right time and place they are just the ticket. But in VB you shouldn't really use them to go backwards! GoTo’s are like Beers. If you have to many bad things happen, if you don’t allow yourself any, you just being prudish, but at the right time and place they are just the ticket.

But in VB you shouldn’t really use them to go backwards!

]]> By: Francesco Giossi http://datapigtechnologies.com/blog/index.php/are-goto-statements-still-dirty/comment-page-1/#comment-2564 Francesco Giossi Thu, 19 Nov 2009 09:01:00 +0000 http://datapigtechnologies.com/blog/?p=1263#comment-2564 I'm with dermotb :p I’m with dermotb :p

]]> By: Jon Peltier http://datapigtechnologies.com/blog/index.php/are-goto-statements-still-dirty/comment-page-1/#comment-2539 Jon Peltier Mon, 16 Nov 2009 16:40:46 +0000 http://datapigtechnologies.com/blog/?p=1263#comment-2539 Call does not create spaghetti code. Call branches to another routine, then returns. It's really no different than calling a function except for not returning a value. Spaghetti code is where execution jumps around from place to place in a single procedure, so that tracking it is like trying to untangle a mass of spaghetti. Overcooked spaghetti, because if you pull on a strand too hard, it breaks, and you lose track of where you are. Call does not create spaghetti code. Call branches to another routine, then returns. It’s really no different than calling a function except for not returning a value.

Spaghetti code is where execution jumps around from place to place in a single procedure, so that tracking it is like trying to untangle a mass of spaghetti. Overcooked spaghetti, because if you pull on a strand too hard, it breaks, and you lose track of where you are.

]]> By: Ajay http://datapigtechnologies.com/blog/index.php/are-goto-statements-still-dirty/comment-page-1/#comment-2537 Ajay Mon, 16 Nov 2009 11:48:20 +0000 http://datapigtechnologies.com/blog/?p=1263#comment-2537 I feel goto statements are an excuse more than anything else. If used for error handling (and which is where I've used them most), one is essentially covering one's back beacuse MS did not provide better error handling constructs. If used otherwise, it is often because one did not anticipate that particular situation to occur when one started writing the code and then by that time, having written so much code, was lazy to go back and restructure it. Regards, Ajay I feel goto statements are an excuse more than anything else. If used for error handling (and which is where I’ve used them most), one is essentially covering one’s back beacuse MS did not provide better error handling constructs. If used otherwise, it is often because one did not anticipate that particular situation to occur when one started writing the code and then by that time, having written so much code, was lazy to go back and restructure it.

Regards,
Ajay

]]>