Adding an implemented UNO interface

[Lionel Élie Mamane]

On Tue, Sep 05, 2023 at 08:34:56AM +0200, Noel Grandin wrote:
> On Mon, 4 Sept 2023 at 21:54, Noel Grandin <noelgrandin at gmail.com> wrote:
>> On Mon, 4 Sept 2023 at 20:43, Lionel Élie Mamane <lionel at mamane.lu> wrote:

>>> becomes an ambiguous base of class bar, as it is derived from twice
>>> :-|

> Likely you will have to implement disambiguation overrides like:

>    virtual SAL_CALL void setFoo() override { Baseclass::setFoo(); }

Pierre is more courageous than I anticipated, and it looks like he
will just change grault (in reality OMetaConnection) to declare
implementation of qux2 (which is css::sdbc::XConnection2) and change
all derived classes that derive from grault to actually implement
qux2.

An alternative idea I have is to make grault a templated class,
templated on which interface(s) it declares. Will try to do that.

Also, since I'm starting to think that we should maybe split qux2 into
several different interfaces that can optionally be implemented or
not, I would like to understand the UNO interface mechanism details
better: is there a difference between

interface qux2: qux
{
  void method();
}

and

interface qux2
{
  interface qux;
  void method();
}

and if yes, what is the difference?

Thank you for your patience,

Lionel