跳至內容

Mixin

維基百科,自由的百科全書

這是本頁的一個歷史版本,由Linwe2012對話 | 貢獻2019年2月6日 (三) 04:14 (删除歧义内容)編輯。這可能和目前版本存在着巨大的差異。

Mixin面向對象程式語言中的,提供了方法的實現。其他類可以訪問mixin類的方法而不必成為其子類。[1]Mixin有時被稱作"included"而不是"inherited"。mixin為使用它的class提供額外的功能,但自身卻不單獨使用(不能單獨生成實例對象,屬於抽象類)。因為有以上限制,Mixin類通常作為功能模塊使用,在需要該功能時「混入」,而且不會使類的關係變得複雜。使用者與Mixin不是「is-a」的關係,而是「-able」關係

Mixin有利於代碼復用[2]又避免了多繼承的複雜。[3][4]使用Mixin享有單一繼承的單純性和多重繼承的共有性。接口與mixin相同的地方是都可以多繼承,不同的地方在於 mixin 是帶實現的。Mixin也可以看作是帶實現的interface英語Interface (object-oriented programming)。這種設計模式實現了依賴反轉原則[5]

實現

已隱藏部分未翻譯內容,歡迎參與翻譯

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: :before and :after daemons, whoppers and wrappers in Flavors. CLOS added :around methods and the ability to call shadowed methods via CALL-NEXT-METHOD. 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 :around method. Both CLOS and Flavors allow the computed reuse via method combinations. :before, :after and :around methods are a feature of the standard method combination. Other method combinations are provided.

An example is the + 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 bordered-button (that is both a graphical object and uses the border mixin) would compute its width by calling all applicable width methods—via the + method combination. All return values are added and create the combined width of the object.

In an OOPSLA 90 paper,[6] 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

已隱藏部分未翻譯內容,歡迎參與翻譯

Common Lisp provides mixins in CLOS (Common Lisp Object System) similar to Flavors.

object-width is a generic function with one argument that uses the + method combination. This combination determines that all applicable methods for a generic function will be called and the results will be added.

(defgeneric object-width (object)
  (:method-combination +))

button is a class with one slot for the button text.

(defclass button ()
  ((text :initform "click me")))

There is a method for objects of class button that computes the width based on the length of the button text. + is the method qualifier for the method combination of the same name.

(defmethod object-width + ((object button))
   (* 10 (length (slot-value object 'text))))

A border-mixin class. The naming is just a convention. There are no superclasses, and no slots.

(defclass border-mixin () ())

There is a method computing the width of the border. Here it is just 4.

(defmethod object-width + ((object border-mixin))
  4)

bordered-button is a class inheriting from both border-mixin and button.

(defclass bordered-button (border-mixin button) ())

We can now compute the width of a button. Calling object-width computes 80. The result is the result of the single applicable method: the method object-width for the class button.

? (object-width (make-instance 'button))
80

We can also compute the width of a bordered-button. Calling object-width computes 84. The result is the sum of the results of the two applicable methods: the method object-width for the class button and the method object-width for the class border-mixin.

? (object-width (make-instance 'bordered-button))
84

Python

Python中,除了使用protocol以外,也可以用多繼承的形式來實現Mixin。為了區分普通的多繼承,mixin類的類名一般都會帶上後綴:「Mixin」,比如Python 2中的類UserDict.DictMixinDictMixin類包括部分實現,使用者的類只要實現幾個必須的函數接口,如:__getitem__(), __setitem__(), __delitem__(), keys()[10]

Python的SocketServer模塊[11]提供了UDPServer類與TCPServer類,作為UDPTCPsocket伺服器。有兩個mixin類:ForkingMixInThreadingMixIn。通過如以下代碼的方式使用ThreadingMixIn擴展TCPServer

class ThreadingTCPServer(ThreadingMixIn, TCPServer):
  pass

ThreadingMixIn類為TCP伺服器添加了新功能,使每個新連接都會創建出新線程。而如果是ForkingMixIn,則會使每個新連接fork出新的進程。

Ruby

在ruby中,並不直接使用Mixin這個單詞,而是使用在類的聲明中include一個module的辦法。

已隱藏部分未翻譯內容,歡迎參與翻譯

Most of the Ruby world is based around mixins via Modules. The concept of mixins is implemented in Ruby by the keyword include to which we pass the name of the module as parameter.

Example:

class Student
  include Comparable # The class Student inherits the Comparable module using the 'include' keyword
  attr_accessor :name, :score

  def initialize(name, score)
    @name = name
    @score = score
  end

  # Including the Comparable module requires the implementing class to define the <=> comparison operator
  # Here's the comparison operator. We compare 2 student instances based on their scores.

  def <=>(other)
    @score <=> other.score
  end

  # Here's the good bit - I get access to <, <=, >,>= and other methods of the Comparable Interface for free.
end

s1 = Student.new("Peter", 100)
s2 = Student.new("Jason", 90)

s1 > s2 #true
s1 <= s2 #false

JavaScript

已隱藏部分未翻譯內容,歡迎參與翻譯

The Object-Literal and extend 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:

  1. It intermingles properties of the model domain with that of implementation domain.
  2. No sharing of common behavior. Metaobjects solve this problem by separating the domain specific properties of objects from their behaviour specific properties.[12]

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:[13]

// This example may be contrived.
// It's an attempt to clean up the previous, broken example.
var Halfling = function (fName, lName) {
    this.firstName = fName;
    this.lastName = lName;
}

var NameMixin = {
    fullName: function () {
        return this.firstName + ' ' + this.lastName;
    },
    rename: function(first, last) {
        this.firstName = first;
        this.lastName = last;
        return this;
    }
};

var sam = new Halfling('Sam', 'Lowry');
var frodo = new Halfling('Freeda', 'Baggs');

// Mixin the other methods
_.extend(Halfling.prototype, NameMixin);

// Now the Halfling objects have access to the NameMixin methods
sam.rename('Samwise', 'Gamgee');
frodo.rename('Frodo', 'Baggins');

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 extend.

// Implementation
var EnumerableFirstLast = (function () { // function based module pattern.
    var first = function () {
        return this[0];
    },
    last = function () {
        return this[this.length - 1];
    };
    return function () {      // function based Flight-Mixin mechanics ...
        this.first  = first;  // ... referring to ...
        this.last   = last;   // ... shared code.
    };
}());

// Application - explicit delegation:
// applying [first] and [last] enumerable behavior onto [Array]'s [prototype].
EnumerableFirstLast.call(Array.prototype);

// Now you can do:
a = [1, 2, 3];
a.first(); // 1
a.last();  // 3

其他語言

已隱藏部分未翻譯內容,歡迎參與翻譯

In the Curl web-content language, multiple inheritance is used as classes with no instances may implement methods. Common mixins include all skinnable ControlUIs inheriting from SkinnableControlUI, user interface delegate objects that require dropdown menus inheriting from StandardBaseDropdownUI and such explicitly named mixin classes as FontGraphicMixin, FontVisualMixin and NumericAxisMixin-of 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.[來源請求]

接口與trait

已隱藏部分未翻譯內容,歡迎參與翻譯

Java 8 introduces a new feature in the form of default methods for interfaces.[14] 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.[15][16][17]

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[18] supports Trait and Mixin[19][20] based object composition via function objects that implement additional behavior and then are delegated via call or apply to objects that are in need of such new functionality.

Scala

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.[21] For example, the ability to sing is modeled as such an orthogonal feature: it could be applied to Birds, Persons, etc.

trait Singer{
  def sing { println(" singing … ") }
  //more methods
}

class Birds extends Singer

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 extends is also used to inherit from a super class, in case of a trait extends is used if no super class is inherited and only for mixin in the first trait. All following traits are mixed in using keyword with.

class Person
class Actor extends Person with Singer
class Actor extends Singer with Performer

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:

class Person{
  def tell {  println (" Human ") }
  //more methods
}

val singingPerson = new Person with Singer
singingPerson.sing

Swift

Mixin can be achieved in Swift by using a language feature called Default implementation in Protocol Extension.

protocol ErrorDisplayable {
    func error(message:String)
}

extension ErrorDisplayable {
    func error(message:String) {
        // Do what it needs to show an error
        //...
        print(message)
    }
}

struct NetworkManager : ErrorDisplayable{
    func onError() {
        error("Please check your internet Connection.")
    }
}

參見

參考文獻

  1. ^ http://c2.com/cgi/wiki?MixIn
  2. ^ http://naildrivin5.com/blog/2012/12/19/re-use-in-oo-inheritance.html
  3. ^ http://culttt.com/2015/07/08/working-with-mixins-in-ruby/
  4. ^ Boyland, John; Giuseppe Castagna. Type-Safe Compilation of Covariant Specialization: A Practical Case. Pierre Cointe (編). ECOOP '96, Object-oriented Programming: 10th European Conference. Springer. 26 June 1996: 16–17 [17 January 2014]. ISBN 9783540614395. 
  5. ^ http://justinleitgeb.com/ruby/moving-beyond-mixins/
  6. ^ OOPSLA '90, Mixin based inheritance (pdf)
  7. ^ slava. Factor/Features/The language. concatenative.org. 2010-01-25 [2012-05-15]. Factor's main language features: … Object system with Inheritance, Generic functions, Predicate dispatch and Mixins  外部連結存在於|publisher= (幫助)
  8. ^ Mixin Class Composition. École polytechnique fédérale de Lausanne. [16 May 2014]. 
  9. ^ Mixin classes in XOTcl
  10. ^ 3.7 UserDict -- Class wrapper for dictionary objects. 
  11. ^ Source code for SocketServer in CPython 3.5
  12. ^ http://raganwald.com/2014/04/10/mixins-forwarding-delegation.html
  13. ^ http://bob.yexley.net/dry-javascript-with-mixins/
  14. ^ https://docs.oracle.com/javase/tutorial/java/IandI/defaultmethods.html
  15. ^ Implementing Mix-ins with C# Extension Methods
  16. ^ I know the answer (it's 42) : Mix-ins and C#
  17. ^ Mixins, generics and extension methods in C#
  18. ^ The many talents of JavaScript for generalizing Role Oriented Programming approaches like Traits and Mixins, April 11, 2014.
  19. ^ Angus Croll, A fresh look at JavaScript Mixins, published May 31, 2011.
  20. ^ JavaScript Code Reuse Patterns, April 19, 2013.
  21. ^ https://gleichmann.wordpress.com/2009/07/19/scala-in-practice-traits-as-mixins-motivation

外部連結