Stories
Slash Boxes
Comments
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

use Perl Log In

Log In

[ Create a new account ]

Ovid (2709)

Ovid
  (email not shown publicly)
http://publius-ovidius.livejournal.com/
AOL IM: ovidperl (Add Buddy, Send Message)

Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.

Journal of Ovid (2709)

Tuesday January 15, 2008
09:03 AM

Proposed OSCON Talks

[ #35392 ]

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?

Turbo Charging Your Test Suites
This is broken down into two sections. The first is making your test suites run faster and the second is making your testers run faster :)
Using Traits To Solve OO Compositional Problems
For years programmers have tried to figure out composition in OO systems. MI, interfaces and mixins have all been approaches with pros and cons. I show examples of each failing and how traits get around their limitations.

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".

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I'd be more interested in the "traits" talk, but I probably qualify as an "advanced" programmer, and I currently don't plan to attend OSCON this year.
  • 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
  • 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.

    • 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.

  • I vote for the testing talk. Your O'Reilly blog was a good intro, but I'm interested in learning more.