[fpc-pascal] Interface performance

Ryan Joseph ryan at thealchemistguild.com
Fri Nov 11 12:25:36 CET 2016

> On Nov 11, 2016, at 5:52 PM, Tony Whyman <tony.whyman at mccallumwhyman.com> wrote:
> Someone else may correct me, but with CORBA, I believe you have to explicitly add a function to the interface such as
> function GetObject: TMyObject;
> and implement as
> function TMyObject.GetObject: TMyObject;
> begin
>  Result := self;
> end;

I think I’m out of time now but I’ll try this in my code that was crashing before.

How is this different from just casting the interface to an object? There’s your example below basically like I was doing it before with the seemingly random crashes. Isn’t MyObject2 still pointing to MyObject1?

IMyInterface = interface
   procedure MyProc;

TMyObjectClass = class(TInterfacedObject,IMyInterface)
  procedure MyProc;

var MyObject1, MyObject2: TMyObjectClass;
     MyInterface: IMyInterface;

 MyObject1 := TMyObjectClass.Create;
 MyInterface := MyObject1;


 MyObject2 := TMyObjectClass(MyInterface);

 MyObject1.Free {OK for CORBA - will cause an exception in COM}
 {MyObject1, MyObject2 and MyInterface are now all invalid}

	Ryan Joseph

More information about the fpc-pascal mailing list