Hi,

fpc allows to declare a method with the destructor keyword, that is not a real destructor, because it does not free the memory. For what is this feature good for?
For example:

Type
  TClassA = class
  public
    destructor Foo;
  end;
destructor TClassA.Foo;
begin
end;
var
  o: TClass;
begin
  o:=TClass.Create;
  o.Foo; // does not call FreeInstance
  o.Destroy; // does call FreeInstance
end.

Mattias

2017-01-24 12:48 GMT+01:00 Mattias Gaertner :

fpc allows to declare a method with the destructor keyword, that is not a real destructor, because it does not free the memory. For what is this feature good for?

with trunk works as expected (Foo does call FreeInstance).

True.
Sorry, I mixed two destructors. Now I understand the Note: Class should have one destructor only.

Mattias

As I understand this: It may sometimes well be necessary to write your own destructor to clean up. But if you do this, don't call it foo; call it destructor and override it: destructor destroy; override; In your own destructor method, don't forget to call inherited in the end.