The following code generates a syntax error, if the semicolon after the if/else statement is removed.
Is its absence a syntax error? Pascal version is 2.2.4

procedure TfrmHometel.SetSplitterSizes;
var
 i: integer;
begin
  for i:= 0 to ComponentCount - 1 do
  begin
   if Components[i] is TSplitter then
   begin
     with TSplitter(Components[i]) do
     begin
      if Cursor = crHSplit then
        Width := 7
      else if Cursor = crVSplit then
        Height := 7;
      ; // <-- removing this semicolon results in a syntax error. Is it
syntax error some kind of extra strict compiler check.
      Color := clBlue;
     end;
   end;
  end;
end;

Compiles just fine (with or without the semicolon) with Lazarus r25303M / fpc 2.4.1

Bart

Compiles just fine (with or without the semicolon) with Lazarus r25303M / fpc 2.4.1

2.5.1 eats both too.

Mattias

Compare with next:

      if Cursor =3D crHSplit then
        Width :=3D 7
      else
        if Cursor =3D crVSplit then
          Height :=3D 7; // <-- This semicolon is for the "if".
      ; // <-- This semicolon is for the "else".

Is like this:

IF ... THEN
BEGIN
  ...
END
ELSE BEGIN
  IF ... THEN
  BEGIN
    ...
  END;  // <-- This END is for the "IF".
END;  // <-- This END is for the "ELSE".

I recommend to use "BEGIN ... END" blocks in nested "IF" always to prevent this kind of mistakes.

Regards,
Guillermo "Ñuño" Martínez.

I will be upgrading to 2.4.0 soon.

It shouldn't be an error then.

2010/7/1 Guillermo Martínez Jiménez

Zitat von Frank Church :

No. A semicolon ends *all* open if/if-else/do statements. The second semicolon is an empty statement - a 'no operation'.

In general I agree, but in this case there are no nested ifs, so it won't help here.

Mattias

It is working now on 2.2.4. I think it was a temporary IDE glitch, which is what I suspected. Adding the ; made it go away, but it wasn't really the problem

2010/7/1 Mattias Gärtner

Frank Church wrote on Thu, 01 Jul 2010:

It is working now on 2.2.4. I think it was a temporary IDE glitch, which is what I suspected. Adding the ; made it go away, but it wasn't really the problem

If you are using the textmode IDE, you might want to wait with updating until 2.4.2, because there was a bug in the 2.4.0 IDE that, in many cases, causes compilation to always fail (until a restart of the IDE) after an error occurred once (even if you fix that error).

Jonas

---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.