|
honey the codewitch wrote: But every C# dev should know how to write while(true) { }
while (true)
{
Console.WriteLine("C# is better than Javascript!");
}
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
At least GOTO got a name of a style - spaghetti code!
|
|
|
|
|
They have their place. OS's use them quite a bit. Otherwise your process would never get any time slot.
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
Yes, very common in daemons.
|
|
|
|
|
Definitely. I have no inherent problem with them. They have their place.
Real programmers use butterflies
|
|
|
|
|
When I need an infinite loop I do this
var False = true;
while(False)
{
}
|
|
|
|
|
That's evil ... I like it
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
youAreWrong:
if (youThinkGotoIsEvil) goto youAreWrong;
But seriously, goto is not intrinsically evil. But if it is the only thing you use in your codebase, you are evil!
|
|
|
|
|
BillWoodruff wrote: are an abomination ... as evil as using goto Try to write Assembly or program a PLC in STL without using JMP or similars...
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
suggested reading: [^]
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
state machines are a good argument for gotos. It is impossible as far as I know, to implement every scenario possible for a deterministic finite automata based state machine without using either array based tables, or goto statements. while/for/etc don't cut it because the flow can become too complicated for those constructs. There was a Knuth paper you linked to earlier** that presented a defense of goto that is similar to my defense of it just above.
** here's the code from that paper (Example 1):
for i := 1 step 1 until m do.
if A[i] = x then go to found fi;
not found: i := re+l; m := i;
A[i] := x; B[i] := 0;
found: B[i] := B[i]+I;
rewritten without goto it's even worse (Example 1a):
i:=1;
while i < m and A[i] # x do i :-- i+1;
if i > m then ra := i; A[i] := x; B[i] ::= 0 fi;
B[i] := B[i]+I;
Real programmers use butterflies
|
|
|
|
|
i think you just hoisted my attempt to play Hamlet on his own petard
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
I'm all kinds of no fun today, sorry.
Real programmers use butterflies
|
|
|
|
|
Knuth's "Example 1" problem using structured statements for alternate loop exits:
for i in 1:m do
// main loop body; may contain any number of statements:
while A[i] != x; // premature loop termination if x is found
exitwhile // do this on premature loop termination, i.e. "found"
B[i]++;
exitfor // do this if loop reaches end of (valid) A[], i.e. "not found"
A[i] := x;
B[i] := 1;
m = i; // new search limit for subsequent x searches
endfor I really miss this construct; I found it truly useful, but have seen it in a single language only, 30+ years ago.
Note that both the exitwhile and exitfor clauses are within the scope of the loop statement, with access to the loop control variable and any other variable declared within the loop. (This is essential to the usability of the construct.)
|
|
|
|
|
Yeah - i posted an alternate he provided in that same comment.
Real programmers use butterflies
|
|
|
|
|
I didn't find the alternative nearly as explicit and comprehensible as the exitfor/exitwhile mechanism.
|
|
|
|
|
True, it's not. I was simply pointing out that he *did* produce an alternative. As for me I'd prefer a state machine example.
Compiled state machines requires gotos (i'm excluding array driven ones here). It's true that some state machines can be implemented without them, but not all of them can.
The reason is you need to goto into and out of loops all of the time, just because of how they work. Furthermore state machines more clearly translate to drawn graphs which then directly map to the code, making the code easy to follow if it uses gotos, but not if it uses the array driven style. In this article[^] there's some coverage of what that looks like.
Real programmers use butterflies
|
|
|
|
|
Where does the block of the for statement end, please? I looked at the original article, page 266 for those interested, but I'm still not clear on it.
honey the codewitch wrote: for i := 1 step 1 until m do.
if A[i] = x then go to found fi;
not found: i := re+l; m := i;
A[i] := x; B[i] := 0;
found: B[i] := B[i]+I;
|
|
|
|
|
Looks as if someone has done a rather unsuccessful OCR of the Knuth paper
Preserving the indents and correcting the OCR errors (I should be 1, re should be m) make it look like
for i := 1 step 1 until m do.
if A[i] = x then go to found fi;
not found: i := m+1; m := i;
A[i] := x; B[i] := 0;
found: B[i] := B[i]+1; So, the for loop body is no more than the 'if .. goto' statement.
(Yet, even if this was in 1974, I am surprised that Knuth made that messy layout - especially the four statements after the 'not found' label. Structured statements came in Algol in 1960; Pascal arrived in 1970, so ideas of proper identetation and formatting shouldn't be new to him!)
|
|
|
|
|
I think it continues through the end of the code. I don't know that it is explicitly closed.
Frankly, I can't stand this form of pseudo code. It is like cave drawings.
Real programmers use butterflies
|
|
|
|
|
aha... and?
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Interesting that the paper you linked was headed Edgar Dijkstra when his name is Edsger.
Maybe Dutch is a bit too hard for the editors at the ACM.
|
|
|
|
|
well, my peers, and mentors, i intended this post as a tongue-in-cheek jiggery-pokery i hoped would not be taken seriously ...
back in the days some of us fossils can remember, languages, like Fortran, had simple control structures; you had to use 'goto to exit a DO loop; that, and BASIC, are the context in which Dijkstra's famous hyperbolic essay took aim [^].
in today's high-level languages, like C#, the underlying use of jumps/gotos is abstracted away for very good reasons.
if i see a while(true) in C#, i call that sloppy code that lacks documentation, and, is less maintainable, because you've got to study the interior code to figure out what, if anything, makes it stop.
and, it never returns? [^]
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
Essential in embedded coding. Pretty much every non-OS based embedded app will have a while(1) or similar in the main code. Ditto for an OS, you can't schedule the scheduler (well, you *can*, but...).
|
|
|
|
|
Works better than any break point...
|
|
|
|