104 |
@end deftypefn |
@end deftypefn |
105 |
</pre></td></tr></table> |
</pre></td></tr></table> |
106 |
|
|
107 |
<p>(where the text before the "…", shown above as two lines, would |
<p>(where the text before the “…”, shown above as two lines, would |
108 |
actually be a single line in a real Texinfo file) produces the following |
actually be a single line in a real Texinfo file) produces the following |
109 |
in Info: |
in Info: |
110 |
</p> |
</p> |
111 |
<table><tr><td> </td><td><pre class="smallexample">-- Library Function: int foobar (int FOO, float BAR) |
<table><tr><td> </td><td><pre class="smallexample">-- Library Function: int foobar (int FOO, float BAR) |
112 |
… |
… |
113 |
</pre></td></tr></table> |
</pre></td></tr></table> |
114 |
<p>This means that <code>foobar</code> is a "library function" that returns an |
<p>This means that <code>foobar</code> is a “library function” that returns an |
115 |
<code>int</code>, and its arguments are <var>foo</var> (an <code>int</code>) and |
<code>int</code>, and its arguments are <var>foo</var> (an <code>int</code>) and |
116 |
<var>bar</var> (a <code>float</code>). |
<var>bar</var> (a <code>float</code>). |
117 |
</p> |
</p> |
118 |
<p>The argument names that you write in <code>@deftypefn</code> are not subject |
<p>The argument names that you write in <code>@deftypefn</code> are not subject |
119 |
to an implicit <code>@var</code>--since the actual names of the arguments in |
to an implicit <code>@var</code>—since the actual names of the arguments in |
120 |
<code>@deftypefn</code> are typically scattered among data type names and |
<code>@deftypefn</code> are typically scattered among data type names and |
121 |
keywords, Texinfo cannot find them without help. Instead, you must write |
keywords, Texinfo cannot find them without help. Instead, you must write |
122 |
<code>@var</code> explicitly around the argument names. In the example |
<code>@var</code> explicitly around the argument names. In the example |