Marker interface pattern: Difference between revisions

Revision as of 10:09, 21 March 2006

Revision as of 13:41, 11 April 2006

Line 1:

The '''marker interface pattern''' is a [[design pattern (computer science)|design pattern]] in [[computer science]].

This pattern allows a [[Class (computer science)|class]] to implement a '''marker interface''', which exposes some underlying semantic property of the class that cannot be determined solely by the class' [[Method (computer science)|method]]s. Whereas a typical [[interface (computer science)|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 is the [[Java programming language]]. The {{Javadoc:SE|java/lang|Cloneable}} interface should be implemented by a class if it fully supports the {{Javadoc:SE|java/lang|Object|clone()}} method. Every class in Java has the {{Javadoc:SE|java/lang|Object}} class at the root of its inheritance hierarchy and so every object instantiated from any class ''has'' an associated <code>clone()</code> method. However, developers should only call <code>clone()</code> on objects of classes which implement the <code>Cloneable</code> interface, as it indicates that the cloning functionality is actually supported in a proper manner.