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
several minutes ago. We don't need no stinkin' tactical nukes.
(By the way, do you have change for 10 million people?) --lwall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
So... (Score:1)
... I'm still not totall clear about this roles nonsense :-) :-)
Re: (Score:2)
I knew someone would bring that up :)
Roles are shared behavior with methods which can't conflict. It's tough to get any simpler than that.
Re: (Score:1)
I'm partially kidding :-)
I don't really buy your law though. It was tough for me to "get" roles for various reasons. It was tough for me to get declarative Prolog-ish languages when I first encountered them. I know a bunch of people who took a hell of a time to understand OO. I know a bunch of folk who don't really "get" TDD, XP or Scrum.
Yes - there are nice sound bites for all of them. But they don't really "explain". The concepts are often deep - even if they have a simple container.
Re:So... (Score:1)
I like the simple description above, too.
For me, who learned from the OO gurus and now practice accordingly, I had to see roles as a safe form of (hush!) Multiple Inheritance (hush!) which solves the crippling problem of method name conflicts.
Reply to This
Parent