Another point worth mentioning, (though I hope none of you have been as stupid as me in trying to do it) is that you absolutely must not ever refer to any of an interfaced object's interfaces in its destructor. This causes a wild loop of incrementing and decrementing the reference count which (of course) causes the destructor to be called repeatedly, but strangely just causes a lockup instead of a stack overflow.
(Child object trying to get at an ancestor's property which was private in the ancestor and only made available through the interface where it is always public). Stupid Trevor -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Conor Boyd Sent: Thursday, 5 May 2005 4:14 p.m. To: 'NZ Borland Developers Group - Delphi List' Subject: RE: [DUG] TInterfacedObject Probably worth emphasising the following: Never mix interface and object references to the same instance. Cheers, Conor _______________________________________________ Delphi mailing list [email protected] http://ns3.123.co.nz/mailman/listinfo/delphi
