Talk:Multiple inheritance

message: Compare the most recent edit (10:09, 3 January 2007) to the one before it (13:34, 22 December 2006).  I actually agree that Multiple Inheritance is very useful and its problems can be overcome, but this is pretty blatant POV.  If there are no objections, I'll revert it tomorrow. 152.23.77.52 17:46, 17 January 2007 (UTC)
thread_title:  POV 

message: I just wanted to note a Recent discussion in the Microsoft C@ language forum ...
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.dotnet.languages.csharp&lang=en&cr=US
...  that is relevant to an articulate and definitive definition of Multiple
Inheritance.
See Thread : Strategic Functional Migration and Multiple Inheritance
Introduced in this discussion is the importance of separating the following
issues relevant to Multiple Inheritance.
[1] Syntax
[2] Composition
[3] Under the cover (compiler implementation) issues
In dropping these issues (temporarily of course) we were able to focus the discussion of MI
to its utility in the structural aggregation of the target functionality.
A key concept introduced in the discussion is Shawnk's (USA) term of 'functional normalization'
to qualify Redek Cerny's comment regarding normalizing code functionality via Multiple Inheritance (MI).
Redek Cerny's (Australia) excellent comment on 'functional normalization' is
a concise term to articulate the 'realized benefit' of MI relative to providing a
structural aggregation mechanism while still retaining the functional
normalization of the orignal code base.
Functional normalization may well be the core architectural impetus of Multiple Inheritance (MI).
It appears (jury still out) that C# and .NET do not support a functionally normalized code base
BECAUSE there is no support for MI in any .NET language.
The importance of a functionally normalized code base to programming is equal to the importance
of a normalized data base in data base systems.
I encourage all contributors to the WikiPedia definition of Multiple Inheritance to review
Redek Cerny's contribution to the SFM (Strategic Functional Migration) discussion.
The term 'functional normalization' may be an important qualifier to better articulate
the benefits and architectural impetus of Multiple Inheritance.
Shawnk
--------------------------------------------------------
I suggest that the 'see Also' section should contain a link to the Interfaces WikiPedia page.
A link to an 'Implementation Inheritance' page should also be made when that page is created.
Shawnk
There is two Common Lisp solution to diamond inheritance problem written here. Can we get rid one of them.  — Preceding unsigned comment added by 95.10.101.218 (talk) 23:47, 26 August 2012 (UTC)
thread_title:  Comments 

message: The text suggests that the problems of multiple inheritance go away by using interfaces (see the last paragraph of the introduction). This is not true: most of the problems are related to multiple subtyping (having multiple paths through the type hierarchy to the same parent) and not multiple inheritance (getting the same code multiple times). I really think that there is a clarification needed. --Schoelle 18:47, 14 November 2007 (UTC)
thread_title:  Multiple subtyping 

message: The example using Filter circuits and their components is quite poor - while a fair example, those not used to fundamental electronics will not be able to grasp the example.  Much better to use something everyone understands, such as bikes and cars, the de facto standard example objects for OOP problems. dimo414 (talk) 06:29, 25 May 2008 (UTC)
replies: text: Agreed, and done. Joe (talk) 14:40, 23 September 2008 (UTC)
replies: text: Sorry, but the provided example seems a little unclear to me. I'm not sure if it was saying in multiple inheritance the streetMusician inherited from Human, Musician, and Worker, or if it inherited Musician, which inherited from Worker, which inherits human. As well, because Musician inherits from Worker and Human, is it even necessary for StreetMusician to inherit from these if it already inherits Musician? 184.33.23.14 (talk) 05:38, 7 October 2010 (UTC)
thread_title:  Debate: Example 

message: Maybe the article can indicate the earliest language to utilize this feature.72.84.141.136 (talk) 17:37, 23 March 2009 (UTC)
thread_title:  Origins 

message: Hi there, can we please have a minimal example of this behaviour, if possible in C++? This is the first time I hear this claim and I could not replicate it. Thank you. 118.7.198.171 (talk) 08:25, 14 June 2009 (UTC)
thread_title:  Order of inheritance changes class semantics 

message: This page was flagged as a copyright problem at Wikipedia talk:India Education Program#Multiple inheritance and listed at Wikipedia:Copyright problems/2011 November 2. I've now reverted to the last pre IEP revision. 
Further 
:"The Overview section from "Multiple inheritance allows" to the end of the three line table is an almost word for word copy of section 1.11.6.1 from Object Oriented Modeling And Design By B.S.Ainapure (). -84user (talk) 22:30, 3 November 2011 (UTC)
replies: text: copied from User talk:Salix alba, move here to keep discussion in one place--Salix (talk): 18:12, 9 November 2011 (UTC)

text: Other uses brought attention to the copyvio issue on Wikipedia talk:India Education Program#Multiple inheritance and indeed two different of copyvios were found, although it does seem that yours do not seem to be copyvios. There are problems with your edits though, the image is poor and blurry, it would be better done in SVG. Further its somewhat confusing as you are using the same arrow type for inheritance and labelling.  I've got to rush now but I'll have a closer look to see what can be kept.--Salix (talk): 18:12, 9 November 2011 (UTC)
thread_title:  Copyvio problems 

message: In section "Mitigation", item "Python", it is currently stated that "That algorithm [C3] enforces two constraints: children precede their parents". Unless I'm mistaken, this is not correct, see the second example here: http://www.python.org/download/releases/2.3/mro/#examples. Since I'm not an expert pythonist, I'd like someone more experienced than me to comment before editing this sentence.
Manuel (mpg) (talk) 14:08, 21 September 2012 (UTC)
replies: text: Hum, I now realise I didn't pay attention: "children always precede their parents" does not mean the same as "all parents always precede any grandparent". I remove the "dubious" template and added a sentence which hopefully helps make things clearer. Manuel (mpg) (talk) 19:31, 24 September 2012 (UTC)
thread_title:  Python MRO: children don't always precede their parents 

message: I've create Java classes that worked fine with multiple interfaces in Java 5-7, and seen other code that does this.  Clearly this was allowed before Java 8, unless I've slipped into a parallel time line.  As the alternative seems ridiculous I must be a simple and absolute fact that Java allowed multiple interfaces (though not true multiple inheritance) before Java 8.  --50.149.180.189 (talk) 16:30, 6 July 2014 (UTC)
thread_title:  Java and Multiple Interfaces 

message: Is it consistent that Scala is marked as featuring MI while Java, whose object system it uses, after having upgraded to the most possible degree, is marked as not? Scala's traits are not classes but generalization of Java's interfaces (actually, typeclasses built on top of those, heh?). In Scala, a type has only one parent type and mixins are but types with traits.  — Preceding unsigned comment added by 31.173.81.65 (talk) 01:11, 13 February 2016 (UTC)
thread_title:  Scala vs. Java 

message: Somebody who understands the Rust language should add a paragraph to the Mitigation section about how Rust avoids the Diamond problem. —MiguelMunoz (talk) 21:43, 27 November 2020 (UTC)
thread_title:  Rust