In my personal opinion "composition" is more safe/organised than multiple inheritance...

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

happy chucking

On 5 October 2012 17:24, Julien Saint-Martin <julien.saintmartin@googlemail.com> wrote:
Ok no problem,
Have nice show!


2012/10/5 Kassen <signal.automatique@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 you
> 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.

Kas.
_______________________________________________
chuck-users mailing list
chuck-users@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users


_______________________________________________
chuck-users mailing list
chuck-users@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users