/
MudOS_0.9.18/bin/
MudOS_0.9.18/doc/concepts/
MudOS_0.9.18/doc/driver/
MudOS_0.9.18/doc/efuns/bitstrings/
MudOS_0.9.18/doc/efuns/communication/
MudOS_0.9.18/doc/efuns/core/
MudOS_0.9.18/doc/efuns/mappings/
MudOS_0.9.18/doc/efuns/math/
MudOS_0.9.18/doc/efuns/security/
MudOS_0.9.18/doc/lpc/constructs/
MudOS_0.9.18/doc/lpc/types/
MudOS_0.9.18/doc/platforms/
MudOS_0.9.18/etc/
MudOS_0.9.18/mudlib/
MudOS_0.9.18/mudlib/lil/
MudOS_0.9.18/mudlib/lil/clone/
MudOS_0.9.18/mudlib/lil/command/
MudOS_0.9.18/mudlib/lil/data/
MudOS_0.9.18/mudlib/lil/etc/
MudOS_0.9.18/mudlib/lil/include/
MudOS_0.9.18/mudlib/lil/inherit/
MudOS_0.9.18/mudlib/lil/inherit/master/
MudOS_0.9.18/mudlib/lil/log/
MudOS_0.9.18/mudlib/lil/single/
MudOS_0.9.18/mudlib/lil/u/
MudOS_0.9.18/src/amiga/src/amiga/
.\"switches a player (interactive) connection from one object to another
.TH exec 3

.SH NAME
exec() - switches a player (interactive) connection from one object to another

.SH SYNOPSIS
int exec(object to, object from);

.SH DESCRIPTION
This efunction allows the interactite link to a given object to be
migrated to another object.  That is, after a successful exec(to, from)
call, interactive(to) will return 1 and interactive(from) will return 0.
The player that was controlling 'from' will begin controlling 'to' following
the exec() call.  Note that this is a powerful function and its use must
be restricted if you wish to attempt to have a secure mud.  The proper
way to restrict the use of exec() is to make a simul_efun of the same name
and then use valid_override(4) to restrict the use of a simul_efun override
(i.e. efun::exec()).  The exec() function returns 1 if the switch is
successful (and 0 otherwise).

.SH SEE ALSO
interactive(3), valid_override(4)