词条 | Marker interface pattern |
释义 |
The marker interface pattern is a design pattern in computer science, used with languages that provide run-time type information about objects. It provides a means to associate metadata with a class where the language does not have explicit support for such metadata. To use this pattern, a class implements a marker interface[1] (also called tagging interface), and methods that interact with instances of that class test for the existence of the interface. Whereas a typical interface specifies functionality (in the form of method declarations) that an implementing class must support, a marker interface need not do so. The mere presence of such an interface indicates specific behavior on the part of the implementing class. Hybrid interfaces, which both act as markers and specify required methods, are possible but may prove confusing if improperly used. An example of the application of marker interfaces from the Java programming language is the {{Javadoc:SE|java/io|Serializable}} interface. A class implements this interface to indicate that its non-transient data members can be written to an {{Javadoc:SE|java/io|ObjectOutputStream}}. The CritiqueA major problem with marker interfaces is that an interface defines a contract for implementing classes, and that contract is inherited by all subclasses. This means that you cannot "unimplement" a marker. In the example given, if you create a subclass that you do not want to serialize (perhaps because it depends on transient state), you must resort to explicitly throwing Another solution is for the language to support metadata directly:
See also
References1. ^{{cite book | last = Bloch | first = Joshua | title = Effective Java (Second edition) | page = 179 | chapter = Item 37: Use marker interfaces to define types | year = 2008 | isbn = 978-0-321-35668-0 | publisher = Addison-Wesley}} 2 : Software design patterns|Java (programming language) |
随便看 |
开放百科全书收录14589846条英语、德语、日语等多语种百科知识,基本涵盖了大多数领域的百科知识,是一部内容自由、开放的电子版国际百科全书。