Use procedure call with parentheses instead of assign value

[Arthurvdv]

To prevent confusion (and maybe future compatibility issues) create a new rule: do not assign a value directly to a procedure, but always call the procedure using parentheses.

Example 1: Built-in methods

codeunit 50100 MyCodeunit
{
    procedure MyProcedure()
    var
        MyTable: Record MyTable;
    begin
        // Assigning a value (currently allowed, but not recommended)
        MyTable.ReadIsolation := IsolationLevel::ReadCommitted;

        // Correct approach: pass the value as a parameter
        MyTable.ReadIsolation(IsolationLevel::ReadCommitted);
    end;
}

Both lines currently compile and work. However, only the second form makes it clear that a method is being called.

Example 2: Public procedures on a codeunit

codeunit 50100 MyCodeunit
{
    procedure SetValue(NewValue: Integer)
    begin
    end;
}

codeunit 50101 MyOtherCodeunit
{
    procedure MyProcedure()
    var
        MyCodeunit: Codeunit MyCodeunit;
    begin
        MyCodeunit.SetValue := 5;
    end;
}

While assigning a value to a procedure may look like a formatting choice, it could introduces ambiguity.
If the AL language would evolves to support properties on objects (such as table, codeunits, ...) statements like these could become unclear; Is this a property assignment or a method call?