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.
Not quite (Score:1)
This had nothing to do with multiple inheritance. At all.
The problem was it wasn't a pure refactoring. It added functionality to a class (which was appropriate), and the setup code for the failing test wasn't amended to reflect this.
Re:Not quite (Score:2)
Are you saying that you don't have a problem with multiple inheritance, or that you're just not worried about it and eliminating it was just a side-effect of something else you were trying to do?
Reply to This
Parent
Re: (Score:1)
I'm saying the bug had nothing to do with MI.
My reply was referring to the last paragraph about the bug, not the whole post. Reading the reply again, I can see that wasn't clear.