<TD ALIGN="LEFT"> </TD>
</TR>
<TR><TD ALIGN="RIGHT">t</TD>
-<TD ALIGN="LEFT">ExtlTab<A NAME="531"></A></TD>
+<TD ALIGN="LEFT">ExtlTab<A NAME="525"></A></TD>
<TD ALIGN="LEFT">Reference to Lua table</TD>
</TR>
<TR><TD ALIGN="RIGHT">f</TD>
-<TD ALIGN="LEFT">ExltFn<A NAME="532"></A></TD>
+<TD ALIGN="LEFT">ExltFn<A NAME="526"></A></TD>
<TD ALIGN="LEFT">Reference to Lua function.</TD>
</TR>
<TR><TD ALIGN="RIGHT">o</TD>
<P>
You've seen the terms level 1 and 2 call handler mentioned above.
-<A NAME="501"></A>
+<A NAME="495"></A>
The Lua support code uses two so called call handlers to convert and check
the types of parameters passed from Lua to C and back to Lua. The first
one of these call handlers is the same for all exported functions and
<P>
The functions
-<TT>extl_call</TT><A NAME="525"></A>,
-<TT>extl_call_named</TT><A NAME="526"></A>,
-<TT>extl_dofile</TT><A NAME="527"></A> and
-<TT>extl_dostring</TT><A NAME="528"></A>
+<TT>extl_call</TT><A NAME="519"></A>,
+<TT>extl_call_named</TT><A NAME="520"></A>,
+<TT>extl_dofile</TT><A NAME="521"></A> and
+<TT>extl_dostring</TT><A NAME="522"></A>
call a referenced function (ExtlFn), named function, execute a
string and a file, respectively. The rest of the parameters for all these
functions are similar. The 'spec' argument is a string of identifier
<P>
Sometimes it is necessary to block calls to all but a limited set of
Ion functions. This can be accomplished with
-<TT>extl_set_safelist</TT><A NAME="529"></A>.
+<TT>extl_set_safelist</TT><A NAME="523"></A>.
The parameter to this function is a NULL-terminated array of strings
and the return value is a similar old safelist.
The call <TT>extl_set_safelist(NULL)</TT> removes any safelist and allows
<P>
Configuration files should be read as before with the function
-<TT>read_config_for</TT><A NAME="530"></A>
+<TT>read_config_for</TT><A NAME="524"></A>
except that the list of known options is no longer present.
<P>