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

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.
  • If Perl can do it, why can't you you stupid framework.

    The answer is because they, like the Java camp, have declared multiple inheritance bad. The reasoned that the work arounds weren't good enough to solve the diamond pattern in every case or they wanted to make things more "simple".

    I would not agree that lack of it makes the language broken.

    • I suspect that too much (ab)use of MI in C++ land might have lead to the descision as well. Although it is worth pointing out that it is much more difficult to handle MI sanely when you have a class system which handles your instance variables for you. Throw in virtual methods and object upcasting and you have a real nightmare trying to determine which object slot you should write too at any given moment (this is especially true if you want to agressively optimize anything). However, this does not mean tha

    • I would consider anytime you have to write an interface and an implementation class and glue that into multiple other classes just to work around the lack of MI as broken. As a tanget, the .NET 3.5 Orcas stuff adds "method extensions", which is basically the ability to inject methods into any type, which in most cases, can fix the lack of MI. 3.5 is also picking up initializer, which finnally does things like:

      new Person(){Prop1="Val";Prop2=3;Prop3=new OtherClass(){OProp1=34}}

      automatically assign the va