Why is this an issue?

Empty routines are usually superfluous, and should be removed to prevent unexpected behaviour.

Some valid empty routines could include:

• A virtual method that is intended to be overridden
• An override method of a non-empty virtual method
• A method that exists only to implement an interface

In these cases, a comment should be added to the routine body to explain why the routine is blank.

How to fix it

If the empty routine is an omission, remove it.

If the routine should be empty, add a nested comment explaining why the routine is blank:

procedure TExample.MyEmptyMethod;
begin
end;

procedure TExample.MyEmptyMethod;
begin
  // Empty because I really want it to be!
end;