Can you summarize the following document?
        
  In Simula, classes are defined in a block in which attributes, methods and class initialization are all defined together; thus all the methods that can be invoked on a class are defined together, and the definition of the class is complete.  In Flavors, a Mixin is a class from which another class can inherit slot definitions and methods. The Mixin usually does not have direct instances. Since a Flavor can inherit from more than one other Flavor, it can inherit from one or more Mixins. Note that the original Flavors did not use generic functions.  In New Flavors (a successor of Flavors) and CLOS, methods are organized in "generic functions". These generic functions are functions that are defined in multiple cases (methods) by class dispatch and method combinations.  CLOS and Flavors allow mixin methods to add behavior to existing methods: codice_1 and codice_2 daemons, whoppers and wrappers in Flavors. CLOS added codice_3 methods and the ability to call shadowed methods via. So, for example, a stream-lock-mixin can add locking around existing methods of a stream class. In Flavors one would write a wrapper or a whopper and in CLOS one would use an codice_3 method. Both CLOS and Flavors allow the computed reuse via method combinations. codice_1, codice_2 and codice_3 methods are a feature of the standard method combination. Other method combinations are provided.  An example is the codice_8 method combination, where the resulting values of each of the applicable methods of a generic function are arithmetically added to compute the return value. This is used, for example, with the border-mixin for graphical objects. A graphical object may have a generic width function. The border-mixin would add a border around an object and has a method computing its width. A new class codice_9 (that is both a graphical object and uses the codice_10 mixin) would compute its width by calling all applicable width methods—via the codice_8 method combination. All return values are added and create the combined width of the object.  In an OOPSLA 90 paper, Gilad Bracha and William Cook reinterpret different inheritance mechanisms found in Smalltalk, Beta and CLOS as special forms of a mixin inheritance.

  除了Flavors與CLOS (作為Common Lisp的部分),其他語言的支援:  一些語言允許執行時從一個物件拷貝方法到另一個物件。這可以“借”mixin的方法。  C#與Visual Basic.NET支援介面的擴充套件方法(extension method)。

  

  Common Lisp 在CLOS (Common Lisp Object System)也提供Minin設計方法,其相似於Flavors。  codice_12 是一個接受一個引數的通用函式,並使用codice_8方式結合。 這種結合方式,會讓所有應用這個方法的互叫,自動以加法結合其結果。  看個例子:  codice_14 類別擁有一段文字。  接著實現button物件的方法object-with,會計算文字長度後乘10作為回傳值。結合codice_8方法,會使此方法每次都被呼叫,並以加法結合(繼續看下面例子)。  另外,使用:method-combination定義個通用函式,在之後定義的方法,必須都有相同簽名。意思是對於同樣名稱方法object-width,其codice_8並不可省(將會報錯)。  定義另一個類別codice_17。 做為示例,只有名字沒有特別成員、沒有父類別。  定義其codice_18方法。單純的回傳4。  最後,codice_9類別同時繼承了codice_17和codice_14.  我們現在可以呼叫button的object-width,會得到 80。這個結果只呼叫了codice_14這意類別的codice_12方法。  嘗試呼叫codice_9的codice_12,會得到84。這結果是呼叫codice_14的codice_12和codice_17的codice_12結果總和。  我們還可以繼續在增加codice_9的codice_12方法。很簡單的想讓結果在加2。

  Python中,除了使用protocol以外,也可以用多繼承的形式來實現Mixin。為了區分普通的多繼承,mixin類的類名一般都會帶上字尾:“Mixin”,比如Python 2中的類codice_32。codice_33類包括部分實現,使用者的類只要實現幾個必須的函式介面,如:codice_34, codice_35, codice_36, codice_37。 Python的codice_38模組提供了codice_39類與codice_40類,作為UDP與TCP的socket伺服器。有兩個mixin類:codice_41與 codice_42。通過如以下程式碼的方式使用codice_42擴充套件codice_40:  codice_42類為TCP伺服器新增了新功能,使每個新連線都會建立出新執行緒。而如果是codice_41,則會使每個新連線fork出新的程序。

  在ruby中,並不直接使用Mixin這個單詞,而是使用在類的宣告中include一個module的辦法。  Most of the Ruby world is based around mixins via codice_47. The concept of mixins is implemented in Ruby by the keyword codice_48 to which we pass the name of the module as parameter.  Example:

  The "Object-Literal and codice_49 Approach"  It is technically possible to add behavior to an object by binding functions to keys in the object. However, this lack of separation between state and behavior has drawbacks:  An extend function (in this case from the Underscore.js library, which copies all of the functionality from a source object, to a destination object, attributes, functions, etc.) is used to mix the behavior in:  The pure function and delegation based "Flight-Mixin Approach"  Even though the firstly described approach is mostly widespread the next one is closer to what JavaScript's language core fundamentally offers - Delegation.  Two function object based patterns already do the trick without the need of a third party's implementation of codice_49.

  In the Curl web-content language, multiple inheritance is used as classes with no instances may implement methods. Common mixins include all skinnable codice_51s inheriting from codice_52, user interface delegate objects that require dropdown menus inheriting from StandardBaseDropdownUI and such explicitly named mixin classes as codice_53, codice_54 and codice_55 class. Version 7.0 added library access so that mixins do not need to be in the same package or be public abstract. Curl constructors are factories that facilitates using multiple-inheritance without explicit declaration of either interfaces or mixins.

  Java 8 introduces a new feature in the form of default methods for interfaces. Basically it allows a method to be defined in an interface with application in the scenario when a new method is to be added to an interface after the interface class programming setup is done. To add a new function to the interface means to implement the method at every class which uses the interface. Default methods help in this case where they can be introduced to an interface any time and have an implemented structure which is then used by the associated classes. Hence default methods adds a possibility of applying the concept in a mixin sort of a way.  Interfaces combined with aspect-oriented programming can also produce full-fledged mixins in languages that support such features, such as C# or Java. Additionally, through the use of the marker interface pattern, generic programming, and extension methods, C# 3.0 has the ability to mimic mixins. With C# 3.0 came the introduction of Extension Methods[2] and they can be applied, not only to classes but, also, to interfaces. Extension Methods provide additional functionality on an existing class without modifying the class. It then becomes possible to create a static helper class for specific functionality that defines the extension methods. Because the classes implement the interface (even if the actual interface doesn’t contain any methods or properties to implement) it will pick up all the extension methods also.  ECMAScript (in most cases implemented as JavaScript) does not need to mimic object composition by stepwise copying fields from one object to another. It natively supports Trait and Mixin based object composition via function objects that implement additional behavior and then are delegated via codice_56 or codice_57 to objects that are in need of such new functionality.

  Scala has a rich type system and Traits are a part of Scala’s type system which help implement mixin behaviour. As their name reveals, Traits are usually used to represent a distinct feature or aspect that is normally orthogonal to the responsibility of a concrete type or at least of a certain instance. For example, the ability to sing is modeled as such an orthogonal feature: it could be applied to Birds, Persons, etc.  Here, Bird has mixed in all methods of the trait into its own definition as if class Bird had defined method sing() on its own.  As codice_58 is also used to inherit from a super class, in case of a trait codice_58 is used if no super class is inherited and only for mixin in the first trait. All following traits are mixed in using keyword codice_60.  Scala allows mixing in a trait (creating an anonymous type) when creating a new instance of a class. In the case of a Person class instance, not all instances can sing. This feature comes use then:

  Mixin can be achieved in Swift by using a language feature called Default implementation in Protocol Extension.
Mixin是物件導向程式設計語言中的類,提供了方法的實現。其他類可以訪問mixin類的方法而不必成為其子類。Mixin有時被稱作"included"而不是"inherited"。mixin為使用它的class提供額外的功能,但自身卻不單獨使用(不能單獨生成例項物件,屬於抽象類)。因為有以上限制,Mixin類通常作為功能模組使用,在需要該功能時“混入”,而且不會使類的關係變得複雜。使用者與Mixin不是“is-a”的關係,而是「-able」關係