Exit from several, nested while or for loops with one command

Question

0 个投票

Hello Is there an easy way to quit nested while loops with a command?

For example:

 while condition1 = true
    ...
    while condition2 = true
       ...
       while condition3 = true
          ...
          if condition4 = true
              leave all while loops and continue with 'command1';
          end
       end
    end
 end
 command1;

I know that in nested loops, 'break' exits only from the loop in which it occurs. Control passes to the statement that follows the end of that loop.

1 个评论
显示 -1更早的评论隐藏 -1更早的评论

Jan 2013-1-14

编辑：Jan 2013-1-15

I've seen the "goto" tag! Evil.

Be sure to read the related: Loren about a vectorized GOTO in Matlab

请先登录，再进行评论。

请先登录，再回答此问题。

Follow Question

Answer 1

Jan 2013-1-14

编辑：Jan 2013-1-14

在 MATLAB Online 中打开

2 个投票

doRun = true;
while condition1 && doRun
   ...
   while condition2  && doRun
     ...
     while condition3  && doRun
        ...
        if condition4 == true
            leave all while loops and continue with 'command1';
            doRun = false;
        end
     end
  end
end
Command1;

Alternative:

% Call subfunction:
myLoops
command1;
...
function myLoops
while condition1 == true
  ...
  while condition2 == true
     ...
     while condition3 == true
        ...
        if condition4 == true
           return;
        end
      end
   end
end

4 个评论
显示 2更早的评论隐藏 2更早的评论

Paul 2013-1-15

Very interesting! I never knew that the effort for debugging grows exponentially with the number of GOTOs. I cannot find any informations on that in the internet(?) You have any link?

On this site, it is said, that GOTO can be useful for quitting nested loops, but should be used always with care: http://www.dotnettoad.com/index.php?/archives/20-when-not-to-use-the-goto-keyword.html

Jan 2013-1-15

编辑：Jan 2013-1-15

Another rule is, that professionally written software (educated and experienced programmers, bug control in a team work, unit tests, bug tracking, version control, costs > 1$ per line) contains about 1 bug per 1000 lines of code. Fixing a bug in a certain line affects three other lines also, which partially require further fixes afterwards.

Debugging a code seriously demands for a coverage report. A bunch of GOTOs increase the effort to find a valid set of inputs, which is appropriate to run each part of the code. The software for controlling the Tornado battle plane has been debugged to 99% only, while the last 1% has been performed during low-level flights over inhabitted areas in the densly settled middle Europe.

In consequence "GOTO should be used with care" means, that avoiding it is a good programming practice. Or in other words: When you avoid GOTO (and the rest of the axis of evil: EVAL and GLOBAL), you will find another way to implement bugs.

My favorite link about GOTO is:

http://blogs.mathworks.com/loren/2006/04/01/goto-coming-at-long-last-vectorized-no-less/

Searching this forum will be helpful also:

http://www.mathworks.com/matlabcentral/answers/?term=GOTO

请先登录，再进行评论。