Re: [viff-devel] Splitting the Runtime into smaller pieces

2008-02-08 Thread Martin Geisler
Martin Geisler [EMAIL PROTECTED] writes: Hello again, I have thought a little about how we can split the current Runtime class into smaller pieces. Currently runtime.py contains five classes and the Runtime class contains 26 methods. That is too much information in one file. I think we can

Re: [viff-devel] Splitting the Runtime into smaller pieces

2008-02-01 Thread Janus Dam Nielsen
Ohh so it is Turing complete? :) -- Janus Den 01/02/2008 kl. 1.52 skrev Martin Geisler: Janus Dam Nielsen [EMAIL PROTECTED] writes: Den 31/01/2008 kl. 14.21 skrev Martin Geisler: If you just want to select between two methods, then this also works: class Comb(Base, Mix1, Mix2):

Re: [viff-devel] Splitting the Runtime into smaller pieces

2008-01-31 Thread Thomas Jakobsen
Hi I'm not sure I understand completely the distinction between multiple inheritance and mix-ins. I guess I'd better go read a couple of pages in Learning Python before I say anything. But in my opinion, an important issue is encapsulation of protocol implementations. I think a typical user of

Re: [viff-devel] Splitting the Runtime into smaller pieces

2008-01-31 Thread Janus Dam Nielsen
Den 31/01/2008 kl. 14.21 skrev Martin Geisler: If you just want to select between two methods, then this also works: class Comb(Base, Mix1, Mix2): foo = Mix1.foo Brilliant! -- Janus ___ viff-devel mailing list (http://viff.dk/)

Re: [viff-devel] Splitting the Runtime into smaller pieces

2008-01-31 Thread Martin Geisler
Janus Dam Nielsen [EMAIL PROTECTED] writes: Den 31/01/2008 kl. 14.21 skrev Martin Geisler: If you just want to select between two methods, then this also works: class Comb(Base, Mix1, Mix2): foo = Mix1.foo Brilliant! Hehe, I think it's quite neat too :-) Being able to write