<Term> <Option>-finline-phase</Option>:</Term>
<ListItem>
<Para> See <XRef LinkEnd="rewrite-rules">.
-Only relevant if you also use <Option>-fglasgow-exts</Option>.
+Only relevant if you also use <Option>-fglasgow-exts</Option>.</para>
</ListItem> </VarListEntry>
<VarListEntry>
</ListItem> </VarListEntry>
</VariableList>
+ </sect1>
<Sect1 id="primitives">
<Title>Unboxed types and primitive operations
</Para>
<Para>
-The <Literal>IO</Literal> and <Literal>ST</Literal> monads use unboxed tuples to avoid unnecessary
-allocation during sequences of operations.
+The <Literal>IO</Literal> and <Literal>ST</Literal> monads use unboxed
+tuples to avoid unnecessary allocation during sequences of operations.
</Para>
</Sect2>
<Sect2>
<Title>Character and numeric types</Title>
-<Para>
<IndexTerm><Primary>character types, primitive</Primary></IndexTerm>
<IndexTerm><Primary>numeric types, primitive</Primary></IndexTerm>
<IndexTerm><Primary>integer types, primitive</Primary></IndexTerm>
<IndexTerm><Primary>floating point types, primitive</Primary></IndexTerm>
+<Para>
There are the following obvious primitive types:
</Para>
-<Para>
-
<ProgramListing>
type Char#
type Int#
<IndexTerm><Primary><literal>Double#</literal></Primary></IndexTerm>
<IndexTerm><Primary><literal>Int64#</literal></Primary></IndexTerm>
<IndexTerm><Primary><literal>Word64#</literal></Primary></IndexTerm>
-</Para>
<Para>
If you really want to know their exact equivalents in C, see
or be empty) applied to the appropriate integer value. You can
have multiple <literal>#enum</literal> definitions with the same
<literal>type</literal>; this construct does not emit the type
- definition itself.
+ definition itself.</para>
</listitem>
</varlistentry>
</variablelist>
macro whose expansion uses other <literal>#let</literal> macros.
Plain <literal>#let</literal> prepends <literal>hsc_</literal>
to the macro name and wraps the defininition in a
- <literal>printf</literal> call.
+ <literal>printf</literal> call.</para>
</sect2>