ldmud-3.2.9/doc/
ldmud-3.2.9/doc/efun/
ldmud-3.2.9/mud/
ldmud-3.2.9/mud/heaven7/
ldmud-3.2.9/mud/heaven7/lib/
ldmud-3.2.9/mud/lp-245/
ldmud-3.2.9/mud/lp-245/banish/
ldmud-3.2.9/mud/lp-245/doc/
ldmud-3.2.9/mud/lp-245/doc/examples/
ldmud-3.2.9/mud/lp-245/doc/sefun/
ldmud-3.2.9/mud/lp-245/log/
ldmud-3.2.9/mud/lp-245/obj/Go/
ldmud-3.2.9/mud/lp-245/players/lars/
ldmud-3.2.9/mud/lp-245/room/death/
ldmud-3.2.9/mud/lp-245/room/maze1/
ldmud-3.2.9/mud/lp-245/room/sub/
ldmud-3.2.9/mud/lp-245/secure/
ldmud-3.2.9/mud/morgengrauen/
ldmud-3.2.9/mud/morgengrauen/lib/
ldmud-3.2.9/mud/sticklib/
ldmud-3.2.9/mud/sticklib/src/
ldmud-3.2.9/mudlib/uni-crasher/
ldmud-3.2.9/pkg/
ldmud-3.2.9/pkg/debugger/
ldmud-3.2.9/pkg/diff/
ldmud-3.2.9/pkg/misc/
ldmud-3.2.9/src/autoconf/
ldmud-3.2.9/src/bugs/
ldmud-3.2.9/src/bugs/MudCompress/
ldmud-3.2.9/src/bugs/b-020916-files/
ldmud-3.2.9/src/bugs/doomdark/
ldmud-3.2.9/src/bugs/ferrycode/ferry/
ldmud-3.2.9/src/bugs/ferrycode/obj/
ldmud-3.2.9/src/bugs/psql/
ldmud-3.2.9/src/done/
ldmud-3.2.9/src/done/order_alist/
ldmud-3.2.9/src/done/order_alist/obj/
ldmud-3.2.9/src/done/order_alist/room/
ldmud-3.2.9/src/gcc/
ldmud-3.2.9/src/gcc/2.7.0/
ldmud-3.2.9/src/gcc/2.7.1/
ldmud-3.2.9/src/hosts/
ldmud-3.2.9/src/hosts/GnuWin32/
ldmud-3.2.9/src/hosts/amiga/NetIncl/
ldmud-3.2.9/src/hosts/amiga/NetIncl/netinet/
ldmud-3.2.9/src/hosts/amiga/NetIncl/sys/
ldmud-3.2.9/src/hosts/i386/
ldmud-3.2.9/src/hosts/msdos/byacc/
ldmud-3.2.9/src/hosts/msdos/doc/
ldmud-3.2.9/src/hosts/os2/
ldmud-3.2.9/src/hosts/win32/
ldmud-3.2.9/src/util/
ldmud-3.2.9/src/util/erq/
ldmud-3.2.9/src/util/indent/hosts/next/
ldmud-3.2.9/src/util/xerq/
ldmud-3.2.9/src/util/xerq/lpc/
ldmud-3.2.9/src/util/xerq/lpc/www/
<PRE>

MudOS has a variable type named 'function'.  Variables of this type may

be used to point to a wide variety of functions.  You are probably already

familiar with the idea of passing a function to certain efuns.  Take, for

example, the filter efun.  It takes an array, and returns an array containing

the elements for which a certain function returns non-zero.  Traditionally,

this was done by passing an object and a function name.  Now, it can also

be done by passing an expression of type 'function' which merely contains

information about a function, which can be evaluated later.


Function pointers can be created and assigned to variables:


function f = (: local_func :);


Passed to other routines or efuns, just like normal values:


foo(f);  map_array( ({ 1, 2 }), f);


Or evaluated at a later time:


x = evaluate(f, "hi");


When the last line is run, the function that f points to is called, and "hi"

is passed to it.  This will create the same effect as if you had done:


x = local_func("hi");


The advantage of using a function pointer is that if you later want to

use a different function, you can just change the value of the variable.


Note that if evaluate() is passed a value that is not a function, it just

returns the value.  So you can do something like:


void set_short(mixed x) { short = x; }

mixed query_short() { return evaluate(short); }


This way, simple objects can simply do: set_short("Whatever"), while objects

that want their shorts to change can do: set_short( (: short_func :) ); 




Available kinds of function pointers:

-------------------------------------


The simplest function pointers are the ones shown above.  These simply

point to a local function in the same object, and are made using 

(: function_name :).  Arguments can also be included; for example:


string foo(string a, string b) {
   return "(" + a "," + b + ")";

}


void create() {
    function f = (: foo, "left" :);

    printf( "%s %s\n", evaluate(f), evaluate(f, "right") );

}


will return an array of all the objects in the game which are clones.

Arguments can also be used:


void create() {
    int i;
    function f = (: write, "Hello, world!\n" :);

    for (i=0; i&lt;3; i++) { evaluate(f); }

}


Will print:

Hello, world!

Hello, world!

Hello, world!


Note that simul_efuns work exactly like efuns with respect to function

pointers.




The third type is the call_other function pointer, which is similar to the

type of function pointer MudOS used to support.  The form is 

(: object, function :).  If arguments are to be used, the should be added

to an array along with the function name.  Here are some examples:


void create()

{
     string *ret;
     function f = (: this_player(), "query" :);    

     ret = map( ({ "name", "short", "long" }), f );     
     write(implode(ret, "\n"));

}


This would print the results of this_player()->query("name"), 

this_player()->query("short"), and this_player()->query("long").

To make a function pointer that calls query("short") directly, use:


f = (: this_player(), ({ "query", "short" }) :)


For reference, here are some other ways of doing the same thing:


f = (: call_other, this_player(), "query", "short" :)  // a efun pointer using
                                                       // the call_other efun

f = (: this_player()->query("short") :) // an expression functional; see
                                        // below.




The fourth type is the expression function pointer.  It is made using

(: expression :).  Within an expression function pointer, the arguments

to it can be refered to as $1, $2, $3 ..., for example:


evaluate( (: $1 + $2 :), 3, 4)  // returns 7.

        int y;

        switch(x) {
        case 1: y = 3;
        case 2: y = 5;
        }
        return y - 2;
    };

    printf("%i %i %i\n", (*f)(1), (*f)(2), (*f)(3));

}


would print: 1 3 -2


Note that (*f)(...) is the same as evaluate(f, ...) and is retained for

backwards compatibility.  Anything that is legal in a normal function is

legal in an anonymous function.



When are things evaluated?

--------------------------


The rule is that arguments included in the creation of efun, local function,

and simul_efun function pointers are evaluated when the function pointer is

made.  For expression and functional function pointers, nothing is evaluated

until the function pointer is actually used:


(: destruct, this_player() :)  // When it is *evaluated*, it will destruct
                               // whoever "this_player()" was when it 
                               // was *made*

(: destruct(this_player()) :)  // destructs whoever is "this_player()"
                               // when the function is *evaluated*


For this reason, it is illegal to use a local variable in an expression

pointer, since the local variable may no longer exist when the function

pointer is evaluated.  However, there is a way around it:


(: destruct( $(this_player) ) :) // Same as the first example above


$(whatever) means 'evaluate whatever, and hold it's value, inserting it

when the function is evaluated'.  It also can be used to make things more

efficient:


map_array(listeners, 
          (: tell_object($1, $(this_player()-&gt;query_name()) + " bows.\n") :) );


only does one call_other, instead of one for every message.  The string

addition could also be done before hand:


map_array(listeners, 
          (: tell_object($1, $(this_player()-&gt;query_name() + " bows.\n")) :) );


Notice, in this case we could also do:


map_array(listeners, 
          (: tell_object, this_player()-&gt;query_name() + " bows.\n" :) );
</PRE>
</BODY>
</HTML>