[chuck-users] multiple inheritance
hems.inlet at gmail.com
Tue Oct 9 13:51:19 EDT 2012
In my personal opinion "composition" is more safe/organised than multiple
just create a class C, and inside of it create two properties,
one instance of B another of A.
Mix their functionalities to taste under one unified API.
For me sounds more fun, than inheriting :P
On 5 October 2012 17:24, Julien Saint-Martin <
julien.saintmartin at googlemail.com> wrote:
> Ok no problem,
> Have nice show!
> 2012/10/5 Kassen <signal.automatique at gmail.com>
>> On Fri, Oct 05, 2012 at 05:15:45PM +0200, Julien Saint-Martin wrote:
>> > I am not sure to understand what I should try with "this" parameter. Do
>> > know where can I find an example?
>> Never mind. Right now I am suspecting that what I wanted to do may run
>> into type-system issues. I would need to actually test it and for that
>> I don't have the time right now as I have to prepare a little event.
>> I hope to get back to this.
>> chuck-users mailing list
>> chuck-users at lists.cs.princeton.edu
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the chuck-users