|
Hey anyone else miss the go to statement?
|
| I know I do. |
Blacknaks|
Re: Hey anyone else miss the go to statement?
Link |
by
on 2006-11-01 18:56:59 (edited 2006-11-16 09:13:53)
|
|
actually, the GOTO statement is very very bad. at my work, we are creating a virtual circuit representing an executable program. goto statements (ambiguous branches) really make things tough. the reason is, the circuit is basically a map of data dependancies. with GOTO, it is unclear what data is dependent on what. this same problem exists with conditional blocks and loops, but at lease those are well-defined constructs which can be resolved. GOTO makes me cry. now, gato, on the other hand; man, i miss that guy! 
|
|
Re: Hey anyone else miss the go to statement?
|
| LoL, yeah they were pretty bad. In my programming class (VB.net) my teacher was telling us about the old days of programming with goto. I thought it would be interesting to see what others thought about it. |
|
Re: Hey anyone else miss the go to statement?
|
|
I think the only time I use goto like statements is when I'm using assembly, but even then I'm mimicking the behavior of a function call so I don't get lost.
>,>; Did I just say that...?
|
|
Re: Hey anyone else miss the go to statement?
Link |
by Lord_Prakka
on 2006-11-15 22:20:31
|
|
I totally agree with you folks. The GOTO command makes your code look like noodles. In highschool we needed a TI 83+ calculator. Somethines i wrote "code" on that too. And for long pieces of code it became really messy and stuff. On the other hand, there are some tasks that cannot be straightforwardly accomplished in many programming languages without the use of GOTO statements, such as breaking out of nested loops and exception handling. But I still agree. You'll get spagetti code. And in 'modern' languages you can make fuctions which you can call. prakka |