[fpc-pascal] Interface performance
ryan at thealchemistguild.com
Fri Nov 11 11:59:40 CET 2016
> On Nov 11, 2016, at 5:44 PM, Tony Whyman <tony.whyman at mccallumwhyman.com> wrote:
> With CORBA you are responsible for freeing the objects that provide an interface in the same way that you are always responsible for freeing the objects that you create. If you free an object before you finish using it then it's a bug and using interfaces does not change that.
I’m happy to use CORBA but that means I can’t cast an interface back to an object using “as” but I’m not sure that’s the reason I was getting that crash (I need to make a test example I guess) but you seem to think “as” is needed but CORBA doesn’t allow this.
Tried to switch CORBA interface to a COM now and got another strange crash accessing memory.
What does memory management even mean for interfaces? I never allocate an interface I just implement it in a class so what’s there to be freed? All these crashes I’m getting suggest memory is being trashed by the compiler at some point without my knowledge. I never explicitly allocate an interface like an object so there’s nothing to manage in my mind.
More information about the fpc-pascal