Interface (object-oriented programming) - Revision history

~2025-34701-44: Made link to Abstraction page point to the CS-specific one.

2025-12-18T20:03:06Z

Made link to Abstraction page point to the CS-specific one.

← Previous revision		Revision as of 20:03, 18 December 2025
Line 1:		Line 1:
	{{Short description\|Abstraction of a class}}		{{Short description\|Abstraction of a class}}
	In [[object-oriented programming]], an '''interface''' or '''protocol''' type{{efn\|Use of these terms varies by programming language. Java and languages derived from it tend to use ''interface'', while ''protocol'' is generally more popular elsewhere.}} is a [[data type]] that acts as an [[abstraction]] of a [[Class (computer science)\|class]]. It describes a set of [[method signature]]s, the implementations of which may be provided by multiple [[class (computer programming)\|class]]es that are otherwise not necessarily related to each other.<ref name="csharp-learn">{{cite web \|title=Interfaces - define behavior for multiple types \|url=https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/types/interfaces \|website=learn.microsoft.com \|access-date=16 November 2022 \|language=en-us}}</ref> A class which provides the methods listed in an interface is said to ''implement'' the interface,<ref name="csharp-learn"/> or to ''adopt'' the protocol.<ref name="swift-24h">{{cite book \|last1=Miller \|first1=BJ \|title=Sams Teach Yourself Swift in 24 hours \|date=2015 \|location=Indianapolis, Indiana \|isbn=978-0-672-33724-6 \|page=263 \|quote=Any type can '''adopt''' a protocol to help give it extra functionality to accomplish a particular set of tasks.}}</ref>		In [[object-oriented programming]], an '''interface''' or '''protocol''' type{{efn\|Use of these terms varies by programming language. Java and languages derived from it tend to use ''interface'', while ''protocol'' is generally more popular elsewhere.}} is a [[data type]] that acts as an [[Abstraction (computer science)\|abstraction]] of a [[Class (computer science)\|class]]. It describes a set of [[method signature]]s, the implementations of which may be provided by multiple [[class (computer programming)\|class]]es that are otherwise not necessarily related to each other.<ref name="csharp-learn">{{cite web \|title=Interfaces - define behavior for multiple types \|url=https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/types/interfaces \|website=learn.microsoft.com \|access-date=16 November 2022 \|language=en-us}}</ref> A class which provides the methods listed in an interface is said to ''implement'' the interface,<ref name="csharp-learn"/> or to ''adopt'' the protocol.<ref name="swift-24h">{{cite book \|last1=Miller \|first1=BJ \|title=Sams Teach Yourself Swift in 24 hours \|date=2015 \|location=Indianapolis, Indiana \|isbn=978-0-672-33724-6 \|page=263 \|quote=Any type can '''adopt''' a protocol to help give it extra functionality to accomplish a particular set of tasks.}}</ref>

	Interfaces are useful for [[Encapsulation (computer programming)\|encapsulation]] and reducing [[Coupling (computer programming)\|coupling]]. For example, in [[Java (programming language)\|Java]], the <code>Comparable</code> interface specifies the method <code>compareTo</code>. Thus, a sorting method only needs to take objects of types which implement <code>Comparable</code> to sort them, without knowing about the inner nature of the class (except that two of these objects can be compared via <code>compareTo()</code>).		Interfaces are useful for [[Encapsulation (computer programming)\|encapsulation]] and reducing [[Coupling (computer programming)\|coupling]]. For example, in [[Java (programming language)\|Java]], the <code>Comparable</code> interface specifies the method <code>compareTo</code>. Thus, a sorting method only needs to take objects of types which implement <code>Comparable</code> to sort them, without knowing about the inner nature of the class (except that two of these objects can be compared via <code>compareTo()</code>).

24.50.56.74: /* Examples */

2025-10-15T20:06:47Z

Examples

@@ Line 1: / Line 1: @@
 {{Short description|Abstraction of a class}}
-In [[object-oriented programming]], an '''interface''' or '''protocol''' type{{efn|Usage of these terms varies by programming language. Java and languages derived from it tend to use "interface", while "protocol" is generally more popular elsewhere.}} is a [[data type]] that acts as an [[abstraction]] of a [[Class (computer science)|class]]. It describes a set of [[method signature]]s, the implementations of which may be provided by multiple [[class (computer programming)|class]]es that are otherwise not necessarily related to each other.<ref name="csharp-learn">{{cite web |title=Interfaces - define behavior for multiple types |url=https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/types/interfaces |website=learn.microsoft.com |access-date=16 November 2022 |language=en-us}}</ref> A class which provides the methods listed in an interface is said to ''implement'' the interface,<ref name="csharp-learn" /> or to ''adopt'' the protocol.<ref name="swift-24h">{{cite book |last1=Miller |first1=BJ |title=Sams Teach Yourself Swift in 24 hours |date=2015 |location=Indianapolis, Indiana |isbn=978-0-672-33724-6 |page=263 |quote=Any type can '''adopt''' a protocol to help give it extra functionality to accomplish a particular set of tasks.}}</ref>
+In [[object-oriented programming]], an '''interface''' or '''protocol''' type{{efn|Use of these terms varies by programming language. Java and languages derived from it tend to use ''interface'', while ''protocol'' is generally more popular elsewhere.}} is a [[data type]] that acts as an [[abstraction]] of a [[Class (computer science)|class]]. It describes a set of [[method signature]]s, the implementations of which may be provided by multiple [[class (computer programming)|class]]es that are otherwise not necessarily related to each other.<ref name="csharp-learn">{{cite web |title=Interfaces - define behavior for multiple types |url=https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/types/interfaces |website=learn.microsoft.com |access-date=16 November 2022 |language=en-us}}</ref> A class which provides the methods listed in an interface is said to ''implement'' the interface,<ref name="csharp-learn"/> or to ''adopt'' the protocol.<ref name="swift-24h">{{cite book |last1=Miller |first1=BJ |title=Sams Teach Yourself Swift in 24 hours |date=2015 |location=Indianapolis, Indiana |isbn=978-0-672-33724-6 |page=263 |quote=Any type can '''adopt''' a protocol to help give it extra functionality to accomplish a particular set of tasks.}}</ref>
-<!-- rewrite todo: probably move this to an examples section later -->== Examples ==
+Interfaces are useful for [[Encapsulation (computer programming)|encapsulation]] and reducing [[Coupling (computer programming)|coupling]]. For example, in [[Java (programming language)|Java]], the <code>Comparable</code> interface specifies the method <code>compareTo</code>. Thus, a sorting method only needs to take objects of types which implement <code>Comparable</code> to sort them, without knowing about the inner nature of the class (except that two of these objects can be compared via <code>compareTo()</code>).
-Some [[programming language]]s provide explicit language support for interfaces: [[Ada (programming language)|Ada]], [[C Sharp (programming language)|C#]], [[D (programming language)|D]], [[Dart (programming language)|Dart]], [[Delphi (programming language)|Delphi]], [[Go (programming language)|Go]], [[Java (programming language)|Java]], [[Logtalk]], [[Object Pascal]], [[Objective-C]], [[OCaml]], [[PHP]], [[Racket (programming language)|Racket]], [[Seed7]], [[Swift (programming language)|Swift]], [[Python (programming language)|Python]] 3.8. In languages supporting [[multiple inheritance]], such as [[C++]], interfaces are implemented as [[abstract class]]es.
+== Examples ==
-In languages without explicit support, interfaces are often still present as conventions; this is known as [[duck typing]]. For example, in [[Python (programming language)|Python]], any class can implement an <code>__iter__</code> method and be used as a [[Collection (abstract data type)|collection]].<ref name="python-iter">{{cite web |title=Glossary — Python 3.11.0 documentation |url=https://docs.python.org/3/glossary.html#term-iterable |website=docs.python.org |access-date=16 November 2022}}</ref>
+In Java, an implementation of interfaces may look like:
-[[Type class]]es in languages like [[Haskell (programming language)|Haskell]], or module signatures in [[ML (programming language)|ML]] and [[OCaml]], are used for many of the things that interfaces are used for.{{clarify|date=November 2022}}
+<syntaxhighlight lang="java">
-In [[Rust (programming language)|Rust]], interfaces are called ''trait''s.<ref>{{cite web|title=Traits - The Rust Reference|date=January 2024|url=https://doc.rust-lang.org/reference/items/traits.html}}</ref>
+interface Flyable {
-==See also==
+interface Vocal {
 * [[Concept (generic programming)]]
 * [[Delegation (programming)]]
 * [[Class (computer science)]]
 * [[Application programming interface]]
-==Notes==
+== Notes ==
-{{notelist}}
+{{Notelist}}
-==References==
+== References ==
 {{Data types}}
-{{DEFAULTSORT:Protocol (Object-priented programming)}}
+{{DEFAULTSORT:Protocol (Object-oriented programming)}}
 [[Category:Object-oriented programming]]
 [[Category:Data types]]

imported>Villaida: removed stub template

2025-06-07T19:32:31Z

removed stub template

← Previous revision		Revision as of 19:32, 7 June 2025
Line 2:		Line 2:
	In [[object-oriented programming]], an '''interface''' or '''protocol''' type{{efn\|Usage of these terms varies by programming language. Java and languages derived from it tend to use "interface", while "protocol" is generally more popular elsewhere.}} is a [[data type]] that acts as an [[abstraction]] of a [[Class (computer science)\|class]]. It describes a set of [[method signature]]s, the implementations of which may be provided by multiple [[class (computer programming)\|class]]es that are otherwise not necessarily related to each other.<ref name="csharp-learn">{{cite web \|title=Interfaces - define behavior for multiple types \|url=https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/types/interfaces \|website=learn.microsoft.com \|access-date=16 November 2022 \|language=en-us}}</ref> A class which provides the methods listed in an interface is said to ''implement'' the interface,<ref name="csharp-learn" /> or to ''adopt'' the protocol.<ref name="swift-24h">{{cite book \|last1=Miller \|first1=BJ \|title=Sams Teach Yourself Swift in 24 hours \|date=2015 \|location=Indianapolis, Indiana \|isbn=978-0-672-33724-6 \|page=263 \|quote=Any type can '''adopt''' a protocol to help give it extra functionality to accomplish a particular set of tasks.}}</ref>		In [[object-oriented programming]], an '''interface''' or '''protocol''' type{{efn\|Usage of these terms varies by programming language. Java and languages derived from it tend to use "interface", while "protocol" is generally more popular elsewhere.}} is a [[data type]] that acts as an [[abstraction]] of a [[Class (computer science)\|class]]. It describes a set of [[method signature]]s, the implementations of which may be provided by multiple [[class (computer programming)\|class]]es that are otherwise not necessarily related to each other.<ref name="csharp-learn">{{cite web \|title=Interfaces - define behavior for multiple types \|url=https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/types/interfaces \|website=learn.microsoft.com \|access-date=16 November 2022 \|language=en-us}}</ref> A class which provides the methods listed in an interface is said to ''implement'' the interface,<ref name="csharp-learn" /> or to ''adopt'' the protocol.<ref name="swift-24h">{{cite book \|last1=Miller \|first1=BJ \|title=Sams Teach Yourself Swift in 24 hours \|date=2015 \|location=Indianapolis, Indiana \|isbn=978-0-672-33724-6 \|page=263 \|quote=Any type can '''adopt''' a protocol to help give it extra functionality to accomplish a particular set of tasks.}}</ref>

	<!-- rewrite todo: probably move this to an examples section later -->		<!-- rewrite todo: probably move this to an examples section later -->== Examples ==
	If objects are fully [[encapsulation (object-oriented programming)\|encapsulated]] then the interface is the only way in which they may be accessed by other objects. For example, in [[Java (programming language)\|Java]], the <code>Comparable</code> interface specifies a method <code>compareTo()</code> which implementing classes must implement. This means that a sorting method, for example, can sort a collection of any objects of types which implement the Comparable interface, without having to know anything about the inner nature of the class (except that two of these objects can be compared by means of <code>compareTo()</code>).		If objects are fully [[encapsulation (object-oriented programming)\|encapsulated]] then the interface is the only way in which they may be accessed by other objects. For example, in [[Java (programming language)\|Java]], the <code>Comparable</code> interface specifies a method <code>compareTo()</code> which implementing classes must implement. This means that a sorting method, for example, can sort a collection of any objects of types which implement the Comparable interface, without having to know anything about the inner nature of the class (except that two of these objects can be compared by means of <code>compareTo()</code>).

Line 34:		Line 34:

	{{DEFAULTSORT:Protocol (Object-priented programming)}}		{{DEFAULTSORT:Protocol (Object-priented programming)}}
	~~{{compu-prog-stub}}~~
	[[Category:Object-oriented programming]]		[[Category:Object-oriented programming]]
			[[Category:Data types]]

imported>Remsense: Reverted 1 edit by Wukuendo (talk): Like I already told you in edit summary, I see no reason for mention of this little-known language in every possible location where it possibly relevant. It's not WP:DUE, or at least you've made no attempt to demonstrate that it is (i.e. that its mention is of any real relevance to readers, and doesn't amount to advertising.)

2025-05-24T14:07:38Z

Reverted 1 edit by Wukuendo (talk): Like I already told you in edit summary, I see no reason for mention of this little-known language in every possible location where it possibly relevant. It's not WP:DUE, or at least you've made no attempt to demonstrate that it is (i.e. that its mention is of any real relevance to readers, and doesn't amount to advertising.)

New page

{{Short description|Abstraction of a class}}
In [[object-oriented programming]], an '''interface''' or '''protocol''' type{{efn|Usage of these terms varies by programming language. Java and languages derived from it tend to use "interface", while "protocol" is generally more popular elsewhere.}} is a [[data type]] that acts as an [[abstraction]] of a [[Class (computer science)|class]]. It describes a set of [[method signature]]s, the implementations of which may be provided by multiple [[class (computer programming)|class]]es that are otherwise not necessarily related to each other.<ref name="csharp-learn">{{cite web |title=Interfaces - define behavior for multiple types |url=https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/types/interfaces |website=learn.microsoft.com |access-date=16 November 2022 |language=en-us}}</ref> A class which provides the methods listed in an interface is said to ''implement'' the interface,<ref name="csharp-learn" /> or to ''adopt'' the protocol.<ref name="swift-24h">{{cite book |last1=Miller |first1=BJ |title=Sams Teach Yourself Swift in 24 hours |date=2015 |location=Indianapolis, Indiana |isbn=978-0-672-33724-6 |page=263 |quote=Any type can '''adopt''' a protocol to help give it extra functionality to accomplish a particular set of tasks.}}</ref>


If objects are fully [[encapsulation (object-oriented programming)|encapsulated]] then the interface is the only way in which they may be accessed by other objects. For example, in [[Java (programming language)|Java]], the <code>Comparable</code> interface specifies a method <code>compareTo()</code> which implementing classes must implement. This means that a sorting method, for example, can sort a collection of any objects of types which implement the Comparable interface, without having to know anything about the inner nature of the class (except that two of these objects can be compared by means of <code>compareTo()</code>).

Some [[programming language]]s provide explicit language support for interfaces: [[Ada (programming language)|Ada]], [[C Sharp (programming language)|C#]], [[D (programming language)|D]], [[Dart (programming language)|Dart]], [[Delphi (programming language)|Delphi]], [[Go (programming language)|Go]], [[Java (programming language)|Java]], [[Logtalk]], [[Object Pascal]], [[Objective-C]], [[OCaml]], [[PHP]], [[Racket (programming language)|Racket]], [[Seed7]], [[Swift (programming language)|Swift]], [[Python (programming language)|Python]] 3.8. In languages supporting [[multiple inheritance]], such as [[C++]], interfaces are implemented as [[abstract class]]es.

In languages without explicit support, interfaces are often still present as conventions; this is known as [[duck typing]]. For example, in [[Python (programming language)|Python]], any class can implement an <code>__iter__</code> method and be used as a [[Collection (abstract data type)|collection]].<ref name="python-iter">{{cite web |title=Glossary — Python 3.11.0 documentation |url=https://docs.python.org/3/glossary.html#term-iterable |website=docs.python.org |access-date=16 November 2022}}</ref>

[[Type class]]es in languages like [[Haskell (programming language)|Haskell]], or module signatures in [[ML (programming language)|ML]] and [[OCaml]], are used for many of the things that interfaces are used for.{{clarify|date=November 2022}}

In [[Rust (programming language)|Rust]], interfaces are called ''trait''s.<ref>{{cite web|title=Traits - The Rust Reference|date=January 2024|url=https://doc.rust-lang.org/reference/items/traits.html}}</ref>

==See also==
* [[Concept (generic programming)]]
* [[Delegation (programming)]]
* [[Objective-C#Protocols|Protocols in Objective-C]]
* [[Class (computer science)]]
* [[Encapsulation (computer science)]]
* [[Public interface]]
* [[Interface (Java)]]
* [[Application programming interface]]
* [[Interface (computing)]]
* [[List of basic computer science topics]]

==Notes==
{{notelist}}

==References==

{{reflist}}
{{Data types}}

{{DEFAULTSORT:Protocol (Object-priented programming)}}
{{compu-prog-stub}}
[[Category:Object-oriented programming]]