Hello,

  Dunno if it's actual, but I think it is a good idea to add parameter
  to break; and continue; instructions. Like break (2); or continue
  (3);
  In my practice I've had some problems with several nested while ()
  and for() loops. One always needs to have some boolean variable to
  signal exiting from main loop.
  while (smth) do
   begin
    for i := 1 to 20 do
     if (smth2) then
       break; // HERE it is wiser in fact to break upper while() statement
   end;

Best regards,
Aleksey

Aleksey V. Vaneev wrote: > to break; and continue; instructions. Like break (2); or continue > (3); What is the mean, using goto and labels solves this problem. Labels in pascal is a bad

style, but who can say that these

"many-storied" breaks would be better? IMHO, "pretty programming style" should not be an

end in itself: effectivity of

solution of concrete problem is more important.

I agree here that using goto and a label is much nicer and creates less errors. Because adding an extra loop would require you to adjust all the continue(2) to continue(3), and forgetting one is easily done as it doesn't trigger a compiler error/warning

Aleksey V. Vaneev wrote

to break; and continue; instructions. Like break (2); or continue (3);

What is the mean, using goto and labels solves this problem. Labels in pascal is a bad style, but who can say that these "many-storied" breaks would be better? IMHO, "pretty programming style" should not be an end in itself: effectivity of solution of concrete problem is more important.

Sincerely, Pavel

Not to mention that Break/Continue are ugly constructs, which can be easily removed by making your 'for' a 'while' or 'repeat', and adapting the while/repeat condition.

Michael.