Why is this an issue?

Empty routines are usually superfluous, and should be removed to prevent unexpected behaviour. In some cases, however, empty routines are necessary. In these cases they should be accompanied by an explanatory comment in the body of the routine.

This rule ignores the following, when annotated with a comment:

• Virtual methods (e.g. to provide a no-op default behaviour for child classes)
• Override methods (e.g. to not run behaviour implemented in ancestor classes)
• Methods that implement an interface
• Anonymous methods

How to fix it

If the empty routine is an omission, remove it.

If the routine has a valid reason to be empty, add a nested comment explaining why the routine is blank:

procedure TExample.OverriddenMethod;
begin
end;

procedure TExample.OverriddenMethod;
begin
  // Overrides base class behaviour
end;