On Tue, Mar 2, 2010 at 2:01 PM, Christian Jaeger chrjae@gmail.com wrote:

Don't miss Oops from Ken Dickey (some version is on the dumping grounds) in case you want multiple inheritance

Thanks, Christian. I don't need multiple inheritance; I think it generally is bad design anyway. Meroon is really fast and the most sophisticated one I've seen, but I will check out Oops. I'm writing a scene graph and it'll be fun to run some benchmarks soon.

On Tue, Mar 2, 2010 at 2:23 PM, Bradley Lucier lucier@math.purdue.edu wrote:

I've now felt embarrassed enough to add a web page that introduces and distributes Meroon. If you have suggestions then please send them to me. (Specifically, if you think things are still broken, I'd like to know.)

Thanks Brad, that's great! I added the page to the dumping grounds entry. Lets hope we can get it high up in the search results. Who maintains the deprecated Meroon page, is it Christian Queinnec? We should try to get a note up on there about what has happened with a link to your page.

Also, I completely agree that Meroon should be ported to hygienic macros. That would be a very interesting project which I wish I had to time to work on. Maybe I will find time.

Hey guys!

I just wanted to let you know that I also wrote an object system for gambit. It's supporting multiple inheritance and a bunch of other features. It's extensively described in my master's thesis, but the document is written in French. I'm sure that with the help of google translations, you proably be able to get most of the content. It also contains benchmarks comparing my system to meroon, oops and clos (if I remember correctly).

For a good usage example, you can refer to my Lode Runner implentation that is based on it.

The thesis, the object system and the lode runner sources can all be found in my github (user: sthilaid).

I'll send you the direct links when I get back home.

Cheers!

-- David

Le 2010-03-02 à 16:01, Christian Jaeger chrjae@gmail.com a écrit :

...

Thanks, Christian. I don't need multiple inheritance; I think it generally is bad design anyway. Meroon is really fast and the most sophisticated one I've seen, but I will check out Oops. I'm writing a scene graph and it'll be fun to run some benchmarks soon.

The point of Oops is not to be faster than Meroon in the single-inheritance case! So doing those benchmarks probably won't make much sense.

I've once written an object system in Perl (based on arrays instead of hashes, using integer constants as field names, for compile-time typo checking and "performance") and thought that single inheritance should suffice; only a couple years later I wanted to implement an object hierarchy with multiple implementations and realized that I needed multiple inheritance; I hacked around the object system and added the common classes ("interfaces") to the inheritance tree manually, and luckily Perl would still allow code in those common classes, but I was unable to add fields there. That project never became a success, and so it didn't matter so much, but I implemented a new object system layer for Perl later (there are so many of those in the meantime that it didn't really matter anymore whether I'd create another one), providing for multiple inheritance, and using the only implementation strategy there is for it on Perl, hashes; of course I would still use the old system for all existing classes, because the way objects were implemented (array access) would mean I'd have to change the syntax of all field accesses... Maybe what this taught me was that you can't foresee what you need and what not. (And that abstract syntax is a good thing.)

I'm not claiming that you'll need MI (*), but you better be prepared to adapt your code once you do.

Christian.

(*) there *may* be alternatives _______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list

On Tue, 2010-03-02 at 22:03 -0500, David St-Hilaire wrote:

As promised:

Object system sources: http://github.com/sthilaid/class

I hope this is of interest to anyone... x_x'

It is, but I can't get benchmark.scm to run, even with a bit of hacking. Missing directories, files, getting errors in symbol-append, things like that.

Any hints about how to get this to run? Should I try the version in the loderunner sources?

Brad

James Long wrote:

David - Thanks for pointing out your work - I too had trouble as Bradly mentioned. I finally got it loaded (after hacking around), and your library looks good. Do you have any detailed documentation?

It is widely discussed in my thesis, but there is no other documentation so far. It is experimental code, but if there is interest enough, I will right some documentation to get people started. (I never thought that someone other than myself would be using it).

-- David