<HTML>
<HEAD>
<!-- This HTML file has been created by texi2html 1.51
from ProgrammersManual.texinfo on 4 March 1997 -->
<TITLE>LambdaMOO Programmer's Manual - Builtins</TITLE>
</HEAD>
<BODY>
Go to the <A HREF="ProgrammersManual_1.html">first</A>, <A HREF="ProgrammersManual_38.html">previous</A>, <A HREF="ProgrammersManual_40.html">next</A>, <A HREF="ProgrammersManual_77.html">last</A> section, <A HREF="ProgrammersManual_toc.html">table of contents</A>.
<P><HR><P>
<H2><A NAME="SEC39" HREF="ProgrammersManual_toc.html#TOC39">Built-in Functions</A></H2>
<P>
There are a large number of built-in functions available for use by MOO
programmers. Each one is discussed in detail in this section. The
presentation is broken up into subsections by grouping together functions with
similar or related uses.
</P>
<P>
For most functions, the expected types of the arguments are given; if the
actual arguments are not of these types, <CODE>E_TYPE</CODE> is raised. Some
arguments can be of any type at all; in such cases, no type specification is
given for the argument. Also, for most functions, the type of the result of
the function is given. Some functions do not return a useful result; in such
cases, the specification <SAMP>`none'</SAMP> is used. A few functions can potentially
return any type of value at all; in such cases, the specification <SAMP>`value'</SAMP>
is used.
</P>
<P>
Most functions take a certain fixed number of required arguments and, in some
cases, one or two optional arguments. If a function is called with too many or
too few arguments, <CODE>E_ARGS</CODE> is raised.
</P>
<P>
Functions are always called by the program for some verb; that program is
running with the permissions of some player, usually the owner of the verb in
question (it is not always the owner, though; wizards can use
<CODE>set_task_perms()</CODE> to change the permissions `on the fly'). In the
function descriptions below, we refer to the player whose permissions are being
used as the <STRONG>programmer</STRONG>.
</P>
<P>
Many built-in functions are described below as raising <CODE>E_PERM</CODE> unless
the programmer meets certain specified criteria. It is possible to restrict
use of any function, however, so that only wizards can use it; see the chapter
on server assumptions about the database for details.
</P>
<UL>
<LI><A HREF="ProgrammersManual_40.html#SEC40">Passing</A>: Object-Oriented Programming
<LI><A HREF="ProgrammersManual_41.html#SEC41">Manipulating Values</A>: Manipulating MOO Values
<LI><A HREF="ProgrammersManual_46.html#SEC46">Manipulating Objects</A>: Manipulating Objects
<LI><A HREF="ProgrammersManual_52.html#SEC52">Manipulating Connections</A>: Operations on Network Connections
<LI><A HREF="ProgrammersManual_53.html#SEC53">Time</A>: Operations Involving Times and Dates
<LI><A HREF="ProgrammersManual_54.html#SEC54">Evaluation and Tasks</A>: MOO-Code Evaluation and Task Manipulation
<LI><A HREF="ProgrammersManual_55.html#SEC55">Administrative</A>: Administrative Operations
</UL>
<P><HR><P>
Go to the <A HREF="ProgrammersManual_1.html">first</A>, <A HREF="ProgrammersManual_38.html">previous</A>, <A HREF="ProgrammersManual_40.html">next</A>, <A HREF="ProgrammersManual_77.html">last</A> section, <A HREF="ProgrammersManual_toc.html">table of contents</A>.
</BODY>
</HTML>