Revision as of 09:36, 19 September 2004 edit Esap (talk \| contribs) Extended confirmed users 535 edits →Interfaces in practice: exception specifications as part of interface ← Previous edit		Revision as of 04:45, 31 October 2004 edit undo Paul August (talk \| contribs) Autopatrolled, Administrators 211,961 edits m →Uses of interfaces: fix link Next edit →
Line 7: == Uses of interfaces == The concept of interface is the cornerstone of [[~~modular~~modularity (programming)\|modular]] programming, a forerunner and a standard ingredient of [[object-oriented programming]]. In object-oriented programming, an object's interface consists of a set of methods that the object will typically respond to. Note that the object does not make its instance variables a part of its interface - these are typically accessed by means of [[accessor method]]s. Some object-oriented programming languages mandate that the interface to the object be specified to the compiler separately from the implementation of that object, whilst others relax the requirement. For example, a class in a programming languages such as [[Objective-C]] consists of its interface, specified in a header file, and the implementation in the source file. Because of the [[dynamic typing\|dynamically typed]] nature of Objective-C, one can send messages to any object, and the interface to the class becomes important as it specifies the methods the class responds to.

Interface (computing): Difference between revisions