From: "lyle@..." <lyle@...>
Date: 2003-03-11T01:43:09+09:00
Subject: Re: [Swig-dev] Limited Support for Multiple Inheritance in  SWIG/Ruby


On Mon, 10 Mar 2003 17:06:50 +0100, Luigi Ballabio
<luigi.ballabio@fastwebnet.it> wrote :

> you surely thought of it already---I'm just wondering what the 
> reason was for discarding the possibility. How about mixins?

That is still a possibility; the only potential drawback is that (I think)
you'd have to wrap the non-primary base classes twice, once as a regular
Ruby Class and once as a Module. Using the previous example, we'd wrap
Base1, Base2, Base3 and Derived as classes, and Base2 and Base3 as modules,
then mix the Base2 and Base3 modules into Derived.

This is assuming that the developer wants to be able to instantiate Base2
and Base3 objects directly, use them as bases for other classes, and
anything else that you'd want to do with a class. If that were *not* the
case, I guess we could introduce a special directive that says "Wrap this
class as a Ruby module *only*, and not as a class".

What do you think?

Lyle