I've just submitted my proposed OSCON talks to the BBC who will, in turn, submit them to OSCON. In doing that, if either is accepted, the BBC will pick up the travel tab for me.
If you are going to OSCON or would go if you could, would either of the following two talks interest you?
The traits talk is long overdue and far more important, but I need to think of a way to spice it up better and make it more accessible. It's for advanced programmers, but the concept itself is dirt-simple once it "clicks".
Either talk would interest me, although sadly I'm not going.
To make the traits talk accessible to me, you would need to give a brief introduction to each of the other methods, and those pros and cons you mentioned. I know what multiple inheritance is, I know why Java doesn't use it and I think interfaces are grand, although in Perl (and what little C++ programming I did) I never had any problems with multiple inheritance. I know zilch about mixins.
Not sure where anyone else would be in your prospective audience, but that's what it would take to make it accessible to me, and it's a talk I'd definitely try to go to if I was there.
Re:Making traits accessible
djberg96 on 2008-01-17T02:54:20
I know zilch about mixins.Here's the nitty gritty for Ruby's implementation if you're interested:http://www.klankboomklang.com/2007/11/25/modules-part-i-enter-the-include-class
/
I will go if I can, and the traits talk is definitely something I'd like to see.
While making tests run faster is also of interest, I suspect I could work out for myself how to do it by reading your module's documentation. Whereas traits, being a conceptual thing, benefit from exposition — understanding the fundamental idea, not just learning about some steps to follow.
Re:Traits
Ovid on 2008-01-15T17:57:18
Actually, the testing talk is about far more than just Test::Aggregate. I'll be covering a lot of issues regarding databases, different aggregation strategies, refactoring, making tests easier to write (and therefore faster to write) etc.
