Chapter 13. Interfaces
There are times when you may not want to create a new type, but you do want to describe a set of behaviors that any number of types might implement. For example, you might want to describe what it means to be storable (capable of being written to disk) or printable.
Such a description is called an interface. An interface is a contract. When you design an interface, youâre saying âif you want to provide this capability, you must implement these methods, provide these properties and indexers, and support these events.â The implementer of the interface agrees to the contract and implements the required elements.
Tip
See Chapter 8 for information about methods and properties, Chapter 17 for information about events, and Chapter 14 for coverage of indexers.
When specifying interfaces, it is easy to get confused about who is responsible for what. There are three concepts to keep clear:
- The interface
This is the contract. By convention, interface names begin with a capital I, so your interface might have a name such as
IPrintable
. TheIPrintable
interface might require, among other things, aPrint( )
method. This states that any class that wants to implementIPrintable
must implement aPrint( )
method, but it does not specify how that method works. That is up to the designer of the implementing class.- The implementing class
This is the class that agrees to the contract described by the interface. For example,
Document
might be a class that implementsIPrintable
Get Learning C# 2005, 2nd Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.