break, exit, continue sintaxhighlight and documentation

[Thaddy]

Indeed, for the docs I always do approach Michael via mantis. The wiki is free to edit.

[cpicanco]

https://bugs.freepascal.org/view.php?id=32281

He said they are compiler intrisics.

[ASerge]

Sorry, my bad, only break and continue are reserved words:
https://www.freepascal.org/docs-html/rtl/system/break.html
https://www.freepascal.org/docs-html/rtl/system/continue.html

Strange, but the documentation is wrong. In Delphi docs Break and Continue these are procedures from that perform the necessary actions in the context of the loop. Accordingly, there are no restrictions. In FPC this also, the following code is normally compiled.

Code: Pascal  [Select][+][-]

1. program Project1;
2.  
3. procedure Test;
4. var
5.   i, Break, Continue: Integer;
6. begin
7.   Break := 10;
8.   Continue := 5;
9.   for i := 0 to Break - 1 do
10.   begin
11.     if i = Continue then
12.       System.Continue;
13.     if i = Break - 1 then
14.       System.Break;
15.   end;
16. end;
17.  
18. begin
19.   Test;
20. end.

[cpicanco]

Maybe it should not compile. I have a feeling taht the following code is more readable:

Code: Pascal  [Select][+][-]

1.     program Project1;
2.      
3.     procedure Test;
4.     var
5.       i : integer;
6.       EndOfList : integer = 10;
7.       MustJump: Integer = 5;
8.     begin
9.       for i := 0 to EndOfList - 1 do
10.       begin
11.         if i = MustJump then
12.           Continue;
13.         if i = EndOfList - 1 then
14.           Break;
15.       end;
16.     end;
17.      
18.     begin
19.       Test;
20.     end.

[ASerge]

I have a feeling taht the following code is more readable:

My code was not intended for training, it is useless and does not require improvements. It simply demonstrates the ability to use Break and Continue as ordinary identifiers.

[cpicanco]

Hi ASerge, please, don't get me wrong. I was not assuming your code was intended for training. I just wrote training code based on your code. I was trying to make a point not about your code, but your well received results.