|
After a loop, how do you know if you finished it or breaked out of it?
This post is not about just leaving a loop, but about knowing how you left it and act according it.
We probably all know how to do that in c, but this is about a language that adds syntax elements for that.
|
|
|
|
|
Looks like a nonsense reason, to me. You can just put a message before the break statement.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: You can just put a message before the break statement.
Goto! Before the goto statement!
Damn!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
How do you know the difference in Planc if you used exit***?
As I said, I don't understand what, exactly, these statements do, and the OP doesn't inidicate they do anything beyond breaking out of the loop. That's what break does, too. Hence my question.
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
|
|
|
|
|
After reading the original post again, I wasn't sure I got it right, so I had a look in wikipedia about PLANC.
Now I think EXITFOR specifies what to do if the for loop exits normally and the EXITWHILE specifies what to do when a WHILE clause (one of many) becomes true. Both blocks are specified inside the loop.
So I see a WHILE in PLANC as a "if() break;" construction in c.
And EXITFOR and EXITWHILE would be coded as something like
if (got_out_with_break) {// EXITWHILE block}
else {// EXITFOR block}
but I could be wrong 
As stated below - Python got it as well.
|
|
|
|
|
After reading the python remark below I think I've got it (good thing you pointed that out!  )
I'm not quite convinced of the benefits though. It may indeed - as the OP stated - safe you an extra if or flag variable. But the price you pay is readability: the conditional code can be in an entirely different place than the condition, with potentially a lot of code in between. Even worse, after reading over the OP again, it seems like there can be several while statements that can all trigger the same exitwhile, meaning that there can be several conditons that are all in different places, separated from the conditional code and the other conditions as well! How on earth are you supposed to keep track of the flow of control in code like that? 
There may be cases where such a language construct may make sense, and even be better readable than the alternatives offered in C and other languages. But I sense a great potential of abuse, and I suspect it takes both experience and sense of responsibility to use it well.
Should a programming language support such a feature? If you say "yes", will you also agree that cars should be allowed to use the sidewalks (provided they are wide enough)?. These are the same questions! So, the answer is also the same: we cannot assume that people will use that option responsibly, so we're better off without it!
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
|
|
|
|
|
You are right that in the Planc language you may have several 'while' conditions within a loop, and they all jump to the same exitwhile clause. If you need to distinguish between different reasons for leaving the loop prematurely, you must test variables in the exitwhile clause. It is important to note that block-wise (e.g. with respect to variable scopes), exitwhile is a part of the loop, so e.g. a for loop counter is available, as well as all local variables within the loop.
We used this quite extensively, with one or more while exits, but very rarely there was a need to run alternate execution paths in the exitwhile clause; the cleanup actions, or reporting actions or whatever, was almost always the same for all early exits (but different for loop completion).
I never saw any Planc programmer "abusing" this mechanism (even summer interns who were still students), and I cannot see how that abuse would be. If you need to handle the situation differently if you got to the end or if you did not get to the end, I see no cleaner way to do it in e.g. C constructs.
|
|
|
|
|
At this point I think we're down to the question of personal preference. Every language has some features that people like and are missing in other languages. People preferring those other languages may not consider those features as desirable. Maybe because the typical tasks they work on have no use for it, or maybe because the programming guidelines they're used to would not leave room for them.
Me, I don't see a need for exitwhile/exitfor in C/C++. I see sufficient alternatives, and while the risk for abuse is nowhere near the risk of statements like goto or #define macros, I'd still prefer to avoid it at the cost of slightly more verbose conditional code.
Then again, I'm biased by the kind of code I usually work with: there's no day that passes without me having to skim over unfamiliar code, so everything that isn't obvious from a quick glance on the code, makes it harder for me to do my job. Therefore I prefer the conditions listed in one place, at the start (or in case of a do loop, at the end) of the loop. Having to scan the entire loop body to find out what conditions may have caused the loop to end just means extra work for me. Therefore I try to avoid break and continue (not to mention goto). And for the same reason I wouldn't welcome exitwhile/exitfor.
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
|
|
|
|
|
"Are there other languages out there with something similar?"
Python has this "syntactic sugar" for alternate loop exit:
for item in iterable:
if condition(item):
break
process(item)
else:
print("No item in iterable meets the condition")
The else signifies that the for loop has finished without "break"-ing.
|
|
|
|
|
In Python, loops can take an 'else' clause. It's run if you don't break out of the loop.
For example:
for item in collection:
if some_test(item):
print('Found one!')
break
else:
print('No match found.')
|
|
|
|
|
Yes, this is in the right direction. As your example illustrate, you do not have a symmetrical handling of the two ways out of the loop: The "breakout handling" is embedded in the loop code. with no syntactical indication that it is anything but ordinary actions within the loop. The 'else' provides half of what I want, and half is far better than nothing
|
|
|
|
|
Visual Basic.NET supports similar constructs, such as:
Exit For
Exit While
Exit Do
and continuations like:
Continue For
Continue While
Continue Do
|
|
|
|
|
In fact I seem to remember an "exit for" in QBASIC. Loop exits go way back in many BASIC compliers.
But all you C# coders don't worry; you're still "the best". You'll become better coders as C# becomes more like BASIC. 
LOL, sorry couldn't help myself. 
- great coders make code look easy
- When humans are doing things computers could be doing instead, the computers get together late at night and laugh at us. - ¿Neal Ford?
|
|
|
|
|
But does it provide two ways out? I.e. alternate code blocks executed one but not the other, depending on how you exited the loop?
|
|
|
|
|
It depended on the specific language’s implementation. The general rule was it exits from the innermost loop. I seem to remember VB (pre .NET) was able to break from nested loops…
do while true
for i = 1 to 10
if i > 5 then
exit do
end if
next
loop
I also got something rattling around in my skull about exiting from named loops, but I don’t believe that was a BASIC language. Google/Bing isn’t being helpful at the moment. 
- great coders make code look easy
- When humans are doing things computers could be doing instead, the computers get together late at night and laugh at us. - ¿Neal Ford?
|
|
|
|
|
But if you had
for (...) {
for (...) {
I want to exitfor from the outer loop from a condition in the inner loop
}
}
How would you do it? goto was invented for a reason and this is it!!! 
|
|
|
|
|
CHILL has a very nice solution to this: Every block, whether a procedure, loop, switch or even a linear sequence of statements enclosed with BEGIN and END, could be prefixed with a label. In CHILL, a label does not identify a point in the program, but a block, and consequently label scopes could be nested. So to leave the outer loop, you would write
OuterLoop:
DO FOR (...)
InnerLoop:
DO FOR (...)
...
IF <done processing this element> THEN EXIT InnerLoop; FI;
...
IF <some fatal condition> THEN EXIT OuterLoop; FI
...
OD
OD
(Here I illustrate both leaving the inner loop and the outer loop.) However, CHILL doesn't provide what I asked for in my original post: If the post-loop processing depends on whether you completed the loop or left prematurely by EXIT, you must set some variable to a magic value and test it after the loop, and the post-loop processing would syntactically (e.g. with respect to variable scope) be outside the loop.
While we are at CHILL: Another nifty syntactic sugar cube is the keyword EVER:
DO FOR EVER
...
OD
The semantics of EVER is quite obvious. I like this so much that whenever I need to program an inner loop in C, I set up a
#define ever (;;)
to be able to code it as "for ever {...}" in C.
Sure, any well seasoned C programmer would prefer "while (1) {...}", but even though I have been writing more lines of C code than in any other language the last thirty years, I still read it as "while one what???"
|
|
|
|
|
BASIC provides several exit statements such as
EXIT LOOP
EXIT FOR
You can also set the condition in the call to the loop
WHILE Not [answer you want is found] ... WEND will exit when the condition is met (of course you have to add another exit test to avoid infinite loops There are a bunch of similar constructs.
To use this with some OOP type language just write a little function in BASIC (Visual Studio, PowerBasic), compile to a DLL and call it from the object you need to use.
Visual Studio would probably let you do it all in the same project but then you wouldn't have the DLL to reuse.
|
|
|
|
|
Delphi's version of Pascal has Break (quit the loop) and Continue (begin the next iteration).
|
|
|
|
|
That is like break and continue in C, isn't it?
Does it provide two alternatative ways out of a loop: One alternative is executed if the break was performed,the other if break was not performed? If it does, some more syntax must be defined.
|
|
|
|
|
I don't know C well enough to comment.
And yes, if you need to know whether you exited the loop because of the break or the for/while/repeat condition, you have to code it separately.
Usually there's some "natural" way to easily determine that, but obviously not always.
|
|
|
|
|
Hi All,
The first interview (for some time). Not really sure about it, they haven't really told me or the agent what they will ask (please no Labview)...
GLENN (Also my first post from my S3)
|
|
|
|
|
I am wishing you the best of luck and please tell us how it went when its done
Microsoft ... the only place where VARIANT_TRUE != true
|
|
|
|
|
|
Good luck, my friend!
I'm sure you won't need it...you'll be fine.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
