[fpc-devel] {$Interfaces Corba} and TInterfacedObject

[Graeme Geldenhuys]

On 29/11/2007, Sergei Gorelkin <sergei_gorelkin at mail.ru> wrote:
> >
> Think of Corba-styled interfaces as about "interfaces without COM glue",
> not just as about "interfaces without refcounting". To get runtime
> typecasting features, you have to implement it yourself. OTOH, you are
> free to implement anything you want.


So everything I have read up till now about Interfaces are all just
based on COM interfaces!  I thought seeing that I can't find info in
FPC's docs, I would look at Kylix 3 help.  Seeing that Kylix is not
dependent on COM, in should have a neutral (platfrom independant)
interfaces implementation.  Yet all the docs in Kylix mentions
Supports(), QueryInterface() and TInterfacedObject, so no matter the
platform, it seems everything about interfaces are based on
Microsoft's COM design.  Wow!


Can somebody confirm the following....

I read in a message thread from 2005 that when you use Corba style
interfaces, interfaces are also not allowed to inherit from each
other.  Is this correct?

{$Interfaces Corba}

type
   MyInterfaceA = Interface
     ...
   end;

   MyInterfaceB = Interface(MyInterfaceA)         <===    Not allowed??
    ...
   end;


If the above it true, this is another thing that could be added to the
FPC docs.  Maybe we should start a "Using Interfaces" chapter in the
Programmers Guide or the Language Guide.



Regards,
  - Graeme -


_______________________________________________
fpGUI - a cross-platform Free Pascal GUI toolkit
http://opensoft.homeip.net/fpgui/