2023-05-09 13:25:39 +02:00
|
|
|
<!DOCTYPE html>
|
2019-03-21 09:57:27 +01:00
|
|
|
<html lang="en">
|
2023-05-09 13:25:39 +02:00
|
|
|
<head>
|
|
|
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
|
|
|
<link rel="stylesheet" href="./3rdparty/highlight/styles/default.css" />
|
|
|
|
|
<link rel="stylesheet" href="../css/doctest.css" />
|
|
|
|
|
<script src="./3rdparty/highlight/highlight.pack.js"></script>
|
|
|
|
|
<script src="../dist/iwmlib.js"></script>
|
|
|
|
|
</head>
|
|
|
|
|
<body onload="Doctest.run()">
|
|
|
|
|
<h1><a href="index.html">lib.</a>Interfaces</h1>
|
|
|
|
|
<p>
|
|
|
|
|
Interfaces are objects that specify (document) the external behavior of objects that “provide” them. An
|
|
|
|
|
interface specifies behavior through method definitions that specify functions and their signatures.
|
|
|
|
|
</p>
|
|
|
|
|
<p>Let's look at an example of an interface and a class implementing the interface:</p>
|
|
|
|
|
<script class="doctest">
|
|
|
|
|
class ITestable extends Interface {
|
|
|
|
|
reset() {}
|
|
|
|
|
run() {}
|
|
|
|
|
}
|
2019-03-21 09:57:27 +01:00
|
|
|
|
2023-05-09 13:25:39 +02:00
|
|
|
class Testable {
|
|
|
|
|
reset() {
|
|
|
|
|
print('Resetting testable object')
|
|
|
|
|
}
|
2019-03-21 09:57:27 +01:00
|
|
|
|
2023-05-09 13:25:39 +02:00
|
|
|
run() {
|
|
|
|
|
print('Running testable object')
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
</script>
|
|
|
|
|
<p>We can now check whether the promised interface methods are implemented by the class:</p>
|
|
|
|
|
<script class="doctest">
|
|
|
|
|
Doctest.expect(ITestable.implementedBy(Testable), true)
|
|
|
|
|
</script>
|
|
|
|
|
<p></p>
|
|
|
|
|
<h2>References</h2>
|
|
|
|
|
<ul>
|
|
|
|
|
<li><a href="https://zopeinterface.readthedocs.io">Zope Interfaces</a></li>
|
|
|
|
|
</ul>
|
|
|
|
|
</body>
|
|
|
|
|
</html>
|
