1
0
Fork 0
mirror of https://github.com/ganelson/inform.git synced 2024-07-08 18:14:21 +03:00
inform7/docs/kinds-module/P-htitm.html

157 lines
11 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>How To Include This Module</title>
<link href="../docs-assets/Breadcrumbs.css" rel="stylesheet" rev="stylesheet" type="text/css">
<meta name="viewport" content="width=device-width initial-scale=1">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Language" content="en-gb">
<link href="../docs-assets/Contents.css" rel="stylesheet" rev="stylesheet" type="text/css">
<link href="../docs-assets/Progress.css" rel="stylesheet" rev="stylesheet" type="text/css">
<link href="../docs-assets/Navigation.css" rel="stylesheet" rev="stylesheet" type="text/css">
<link href="../docs-assets/Fonts.css" rel="stylesheet" rev="stylesheet" type="text/css">
<link href="../docs-assets/Base.css" rel="stylesheet" rev="stylesheet" type="text/css">
<link href="../docs-assets/Colours.css" rel="stylesheet" rev="stylesheet" type="text/css">
</head>
<body class="commentary-font">
<nav role="navigation">
<h1><a href="../index.html">
<img src="../docs-assets/Inform.png" height=72">
</a></h1>
<ul><li><a href="../compiler.html">compiler tools</a></li>
<li><a href="../other.html">other tools</a></li>
<li><a href="../extensions.html">extensions and kits</a></li>
<li><a href="../units.html">unit test tools</a></li>
</ul><h2>Compiler Webs</h2><ul>
<li><a href="../inbuild/index.html">inbuild</a></li>
<li><a href="../inform7/index.html">inform7</a></li>
<li><a href="../inter/index.html">inter</a></li>
</ul><h2>Inbuild Modules</h2><ul>
<li><a href="../supervisor-module/index.html">supervisor</a></li>
</ul><h2>Inform7 Modules</h2><ul>
<li><a href="../core-module/index.html">core</a></li>
<li><a href="../assertions-module/index.html">assertions</a></li>
<li><a href="../values-module/index.html">values</a></li>
<li><a href="../knowledge-module/index.html">knowledge</a></li>
<li><a href="../imperative-module/index.html">imperative</a></li>
<li><a href="../runtime-module/index.html">runtime</a></li>
<li><a href="../if-module/index.html">if</a></li>
<li><a href="../multimedia-module/index.html">multimedia</a></li>
<li><a href="../index-module/index.html">index</a></li>
</ul><h2>Inter Modules</h2><ul>
<li><a href="../bytecode-module/index.html">bytecode</a></li>
<li><a href="../building-module/index.html">building</a></li>
<li><a href="../pipeline-module/index.html">pipeline</a></li>
<li><a href="../final-module/index.html">final</a></li>
</ul><h2>Services</h2><ul>
<li><a href="../arch-module/index.html">arch</a></li>
<li><a href="../calculus-module/index.html">calculus</a></li>
<li><a href="../html-module/index.html">html</a></li>
<li><a href="../inflections-module/index.html">inflections</a></li>
<li><a href="index.html"><span class="selectedlink">kinds</span></a></li>
<li><a href="../linguistics-module/index.html">linguistics</a></li>
<li><a href="../problems-module/index.html">problems</a></li>
<li><a href="../syntax-module/index.html">syntax</a></li>
<li><a href="../words-module/index.html">words</a></li>
<li><a href="../../../inweb/docs/foundation-module/index.html">foundation</a></li>
</ul>
</nav>
<main role="main">
<!--Weave of 'How To Include This Module' generated by Inweb-->
<div class="breadcrumbs">
<ul class="crumbs"><li><a href="../index.html">Home</a></li><li><a href="../compiler.html">Services</a></li><li><a href="index.html">kinds</a></li><li><a href="index.html#P">Preliminaries</a></li><li><b>How To Include This Module</b></li></ul></div>
<p class="purpose">What to do to make use of the kinds module in a new command-line tool.</p>
<ul class="toc"><li><a href="P-htitm.html#SP1">&#167;1. Status</a></li><li><a href="P-htitm.html#SP2">&#167;2. Importing the module</a></li><li><a href="P-htitm.html#SP3">&#167;3. Using callbacks</a></li></ul><hr class="tocbar">
<p class="commentary firstcommentary"><a id="SP1" class="paragraph-anchor"></a><b>&#167;1. Status. </b>The kinds module is provided as one of the "services" suite of modules,
which means that it was built with a view to potential incorporation in
multiple tools. It can be found, for example, in <a href="../inform7/index.html" class="internal">inform7</a> and
<a href="../kinds-test/index.html" class="internal">kinds-test</a>.
</p>
<p class="commentary">By convention, the modules considered as "services" have no dependencies on
other modules except for <a href="../../../inweb/docs/foundation-module/index.html" class="internal">foundation</a> and other "services" modules.
</p>
<p class="commentary">A tool can import <a href="index.html" class="internal">kinds</a> only if it also imports <a href="../../../inweb/docs/foundation-module/index.html" class="internal">foundation</a>,
<a href="../words-module/index.html" class="internal">words</a>, <a href="../syntax-module/index.html" class="internal">syntax</a>, <a href="../inflections-module/index.html" class="internal">inflections</a> and <a href="../linguistics-module/index.html" class="internal">linguistics</a>.
</p>
<p class="commentary firstcommentary"><a id="SP2" class="paragraph-anchor"></a><b>&#167;2. Importing the module. </b>We'll use the term "parent" to mean the tool which is importing <a href="index.html" class="internal">kinds</a>,
that is, which will include its code and be able to use it. As with any
imported module,
</p>
<ul class="items"><li>&#9679; The contents page of the parent's web must identify and locate the
module:
</li></ul>
<pre class="displayed-code all-displayed-code code-font">
<span class="element-syntax">Import</span><span class="plain-syntax">:</span><span class="string-syntax"> somepath/kinds</span>
</pre>
<ul class="items"><li>&#9679; The parent must call <a href="1-km.html#SP3" class="internal">KindsModule::start</a> just after it starts up, and
<a href="1-km.html#SP3" class="internal">KindsModule::end</a> just before it shuts down. (But just after, and just
before, the corresponding calls to <a href="../../../inweb/docs/foundation-module/index.html" class="internal">foundation</a>.)
</li></ul>
<p class="commentary firstcommentary"><a id="SP3" class="paragraph-anchor"></a><b>&#167;3. Using callbacks. </b>Shared modules like this one are tweaked in behaviour by defining "callback
functions". This means that the parent might provide a function of its own
which would answer a question put to it by the module, or take some action
on behalf of the module: it's a callback in the sense that the parent is
normally calling the module, but then the module calls the parent back to
ask for data or action.
</p>
<p class="commentary">The parent must indicate which function to use by defining a constant with
a specific name as being equal to that function's name. A fictional example
would be
</p>
<pre class="displayed-code all-displayed-code code-font">
<span class="plain-syntax"> </span><span class="function-syntax">@d</span><span class="plain-syntax"> EXPRESS_SURPRISE_KINDS_CALLBACK Emotions::whoa</span>
<span class="plain-syntax"> =</span>
<span class="plain-syntax"> </span><span class="element-syntax">void Emotions:</span><span class="plain-syntax">:</span><span class="string-syntax">whoa(text_stream *OUT) {</span>
<span class="plain-syntax"> WRITE("Great heavens!\n");</span>
<span class="plain-syntax"> }</span>
</pre>
<p class="commentary">The following alphabetical list has references to fuller explanations:
</p>
<ul class="items"><li>&#9679; <span class="extract"><span class="extract-syntax">DETERMINE_SCALE_FACTOR_KINDS_CALLBACK</span></span>, if provided, is called to give
the "scale factor" for a kind. See <a href="../values-module/3-lp.html" class="internal">Literal Patterns (in values)</a> for the
use of this; here, it appears in <a href="2-uk.html#SP17" class="internal">Kinds::Behaviour::scale_factor</a>.
</li><li>&#9679; <span class="extract"><span class="extract-syntax">HIERARCHY_GET_SUPER_KINDS_CALLBACK</span></span> is called to ask what the superkind
of a kind is. See <a href="2-tlok.html#SP6" class="internal">Latticework::super</a>.
</li><li>&#9679; <span class="extract"><span class="extract-syntax">HIERARCHY_ALLOWS_SOMETIMES_MATCH_KINDS_CALLBACK</span></span> is called to ask if q
kind can contain sometimes-matching subkind instances. See
<a href="2-tlok.html#SP13" class="internal">Latticework::order_relation</a>.
</li><li>&#9679; <span class="extract"><span class="extract-syntax">HIERARCHY_MOVE_KINDS_CALLBACK</span></span> is called to ask us to put make one
kind a subkind of another. See <a href="2-knd.html#SP21" class="internal">Kinds::make_subkind</a> and
<a href="2-knd.html#SP20" class="internal">Kinds::new_base</a> &mdash; there are two ways this can happen.
</li><li>&#9679; <span class="extract"><span class="extract-syntax">HIERARCHY_VETO_MOVE_KINDS_CALLBACK</span></span> is called to give the parent tool a
chance to veto any proposed subkind. (Inform uses this, for example, to catch
the case of somebody making "region" a subkind of some other kind of object.)
See <a href="2-knd.html#SP21" class="internal">Kinds::make_subkind</a>.
</li><li>&#9679; <span class="extract"><span class="extract-syntax">NEW_BASE_KINDS_CALLBACK</span></span> is called when a new base kind (properly
speaking, a new arity-0 kind constructor) is made. See <a href="2-knd.html#SP20" class="internal">Kinds::new_base</a>
and <a href="4-nf.html#SP1" class="internal">NeptuneFiles::read_command</a> &mdash; there are two ways this can happen.
</li><li>&#9679; <span class="extract"><span class="extract-syntax">NOTIFY_NATURAL_LANGUAGE_KINDS_CALLBACK</span></span> is called when the kind "natural
language" is created (if it is): see <a href="2-fk.html#SP13" class="internal">FamiliarKinds::notice_new_kind</a>.
</li><li>&#9679; <span class="extract"><span class="extract-syntax">PROBLEM_KINDS_CALLBACK</span></span> is called when a syntax error is found, and can
prevent this from being issued to the terminal as an error message: see
<a href="1-km.html#SP5" class="internal">KindsModule::problem_handler</a>.
</li><li>&#9679; <span class="extract"><span class="extract-syntax">REGISTER_NOUN_KINDS_CALLBACK</span></span>, if provided, can register a common noun
for a new base kind with the lexicon itself. See <a href="2-knd.html#SP20" class="internal">Kinds::new_base</a>.
</li></ul>
<nav role="progress"><div class="progresscontainer">
<ul class="progressbar"><li class="progressprev"><a href="P-wtmd.html">&#10094;</a></li><li class="progresscurrentchapter">P</li><li class="progresssection"><a href="P-wtmd.html">wtmd</a></li><li class="progresscurrent">htitm</li><li class="progresschapter"><a href="1-km.html">1</a></li><li class="progresschapter"><a href="2-knd.html">2</a></li><li class="progresschapter"><a href="3-dmn.html">3</a></li><li class="progresschapter"><a href="4-abgtn.html">4</a></li><li class="progressnext"><a href="1-km.html">&#10095;</a></li></ul></div>
</nav><!--End of weave-->
</main>
</body>
</html>