VehicleList, not VL or vehicle-list. This convention makes it easier to differentiate local names from attribute and class names.
Obj (object), WS (workspace), and Win (window) for certain common local variables.
begin
for ... do
repeat
case (...) of
on error
collect data
end, which matches any of the above statements.
begin
<statements>
end;
repeat
<statements>
end;for I = 0 to N do
<statements>
end;
if <condition> then <statement>
else <statement>;
if <condition> then begin
<statements>
end
else begin
<statements>
end
case (<symbol expression>) of
TAG1: <statement>
TAG2: <statement>
TAG3: <statement>
otherwise: <statement>
end;
begin
<statements>
end on error (<arguments>)
<statements>
end
collect data (timing out after N seconds)
<statements>
if timeout then begin
<statements>
end;
end;
|
 |
Indentation Conventions for Rules
Similar to the indentation conventions you use for methods and procedures, you should place blocks of code within the same control boundaries of a rule at the same level of indentation. Specifically:
for prefix on a line by itself at the same level of indentation.
whenever, if, and so on.
and, or, then, and when on the same line as the preceding statement.
in order statements indented on a line by themselves.
 |
 |