Syntax on conditional statements 4

[Froskoy]

Is saying

if (Intensity=24) or (Intensity=25) then TempGetColour:=RGB(168,168,168);

exactly the same as

if (Intensity=24 or 25) then TempGetColour:=RGB(160,160,160);

?

Thanks very much,

Froskoy.

 

[towerbase]

You should use your first example.

I imagine that the second example will give you a compile time syntax error.


Andrew
Hampshire, UK

 

[Froskoy]

It compiles fine.... it's a logical error I'm worried about. Will it ultimately give the same result?

 

[whosrdaddy]

since the binary operator (or) takes precedence, delphi will first execute the or statement.

so it finally boils down to

if (Intensity=25) then TempGetColour:=RGB(160,160,160);

because 24 OR 25 = 25

/Daddy

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!

 

[Glenn9999]

Another option if the data type supports it.

if Intensity in [24..25] then 
  TempGetColour:=RGB(168,168,168);

Measurement is not management.

 

[Froskoy]

Thanks very much whosrdaddy. That's really helpful and makes that sort of thing make more sense to me now so will be helpful in future as well.

Thanks also Glenn9999, that does look neat and something that I hadn't thought of off the top of my head.

 

[Bamben]

you guys have just given me an idea!!!

 

[Froskoy]

I am glad. What is it?

 

[Bamben]

procedure TMainForm.xALL;
begin
  repeat
    xManagerALL;
  until (CallPack[0..9].active = false);
end;

Instead of this:

procedure TMainForm.xALL;
begin
  repeat
    xManagerALL;
  until (CallPack[0].active = false) and
        (CallPack[1].active = false) and
        (CallPack[2].active = false) and
        (CallPack[3].active = false) and
        (CallPack[4].active = false) and
        (CallPack[5].active = false) and
        (CallPack[6].active = false) and
        (CallPack[7].active = false) and
        (CallPack[8].active = false) and
        (CallPack[9].active = false);
end;

It probably wont work though ('Array' and 'ISipCall' incompatible types). I like it though looks SNAZZY! I can use it some other time in the future.

 

[Froskoy]

Yes, that is pretty cool. Thanks for posting that idea.

 

[Bamben]

woooooooooooooo!!

 

[Griffyn]

Hi Bamben,

I hate to rain on your parade, but

procedure TMainForm.xALL;
begin
  repeat
    xManagerALL;
  until (CallPack[0..9].active = false);
end;

won't compile in Delphi. You can either refer to the entire array, or a single element of an array. You can never refer to multiple elements in an array in this way.

In your example, I would probably use

function AreElementsActive(ALow, AHigh: Integer): Boolean;
var
  c : Integer;
begin
  Result := False;
  for c := ALow to AHigh do
    Result := Result or CallPack[c].Active;
end;

procedure TMainForm.xALL;
begin
  repeat
    xManagerALL;
  until not AreElementsActive(0, 9);
end;

The logic in the line

Result := Result or CallPack[c].Active;

means that as it loops through the array, Result can become True, but never become False again. That way, if a single element is True, Result will be True.