NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
traits, please (Score:1)
Making traits accessible (Score:2)
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 prospectiv
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Re: (Score:2)
http://www.klankboomklang.com/2007/11/25/modules-part-i-enter-the-include-class/ [klankboomklang.com]
Traits (Score:1)
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: (Score:2)
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.
Testing, please! (Score:1)