On 10/27/2016 06:01 AM, Tony Whyman wrote:
That is you can build an object hierarchy to parallel an interface
hierarchy.
I don't use the "Supports" primitive. - so maybe there is a bug in this
feature but otherwise, what is the problem with interface inheritance?
Yes, the problem is with
On 10/27/2016 05:18 AM, Graeme Geldenhuys wrote:
On 2016-10-27 12:42, Marcos Douglas B. Santos wrote:
It is a "bug by design".
The worst kind!
Actually, I think this is should be corrected in both modes (COM and CORBA).
Indeed, and even if it is fixed in FPC, it shouldn’t break any
On 27/10/16 03:47, Graeme Geldenhuys wrote:
A common misconception about how interfaces work. In fact, I don't
actually know why FPC and Delphi bother with Interface Inheritance,
because I simply don't see the point.
To make your "t_2" class support both interface, you need to specify
both in
On Thu, Oct 27, 2016 at 10:18 AM, Graeme Geldenhuys
wrote:
>> It is a "bug by design".
>
> The worst kind!
Yeah, you're right.
>> Actually, I think this should be corrected in both modes (COM and CORBA).
>
> Indeed, and even if it is fixed in FPC, it shouldn’t
On 2016-10-27 12:42, Marcos Douglas B. Santos wrote:
> It is a "bug by design".
The worst kind!
> Actually, I think this is should be corrected in both modes (COM and CORBA).
Indeed, and even if it is fixed in FPC, it shouldn’t break any existing
code either. So it’s a win-win situation.
If
On Thu, Oct 27, 2016 at 1:12 AM, Graeme Geldenhuys
wrote:
> In the Stack Overflow link I posted - further down the page - a person
> named Jasper mentions that in is QueryInterface implementation bug where
> QueryInterface on checks for valid Interface signatures in
On 2016-10-27 03:47, Graeme Geldenhuys wrote:
> Again, I don't know why it is done like this, and works very different
> to class inheritance. Delphi 7 works exactly the same in this regard.
> Maybe somebody with more knowledge on the subject could shed some light.
I did some quick internet
On 2016-10-27 02:13, David Emerson wrote:
>t_2 = class (_obj_type_, i_2)
> // i_2 inherits from i_1, compiler requires i_1 implementation
> procedure do_one;
> procedure do_two;
> end;
A common misconception about how interfaces work. In fact, I don't
actually know why
Hi all,
I am a bit perplexed / disappointed to see that the Supports /
QueryInterface functions for interfaces are not behaving the way I would
expect them to behave, when using an interface that inherits from
another interface.
note, _obj_type_ might be TObject, TInterfacedObject, or