All the Perl that's Practical to Extract and Report
use Perl Log In
Ovid (2709)
(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.
Mixins Considered Harmful
I know many folks are tired of the "X Considered Harmful" writeups, (I should do a "Considered Harmful Considered Harmful" writeup?), but there's an interesting one by Michele Simionato, a moderately well-known Python programmer. He's written a multi-part series on this.
- Mixins Considered Harmful/1
- Mixins Considered Harmful/2
- Mixins Considered Harmful/3
- Mixins Considered Harmful/4
Interestingly, one proposed solution he's put forward is implementing traits (roles) in Python. He argues that while mixins seem fine for smaller systems, they start to become unwieldy in larger systems. That was one of the driving issues which led to the Refactoring with Roles talk I gave.
My only disappointment is that he seems focused on primarily on eliminating multiple inheritance rather than inheritance in general, but then, I think I've displayed my bias here.
I pour myself a cup of strong coffee. :-)
-- Jarkko Hietaniemi
Role organization (Score:1)
How do you store roles in a project (where do they go in your namespace)?
Do you have a special package, like:
MyFramework::Role::Does*
Re: (Score:2)
Yes, that's exactly where I put them. However, if you prefix everything with Does..., the Role portion of the namespace is almost redundant. Maybe MyFramwork::Does::...?
Re: (Score:1)
I like Does::
(insert picture of a Pakled)
http://img522.imageshack.us/img522/9214/pakled1.jpg [imageshack.us]
Considered Harmful Essays Considered Harmful (Score:1)
I should do a "Considered Harmful Considered Harmful" writeup?
"Considered Harmful" Essays Considered Harmful [meyerweb.com]
/-\