blob: f94f1f7c69524dba5e51639c8f6baaea8836885b [file] [log] [blame]
MG Mud User88f12472016-06-24 23:31:02 +02001NAME
Zesstra7ea4a032019-11-26 20:11:40 +01002 master
MG Mud User88f12472016-06-24 23:31:02 +02003
4DESCRIPTION
Zesstra7ea4a032019-11-26 20:11:40 +01005 This directory contains descriptions for the functions that
6 Amylaar's version of the LPC parser, expects to find in the
7 master object (similar to lfuns, but for the master object
8 only). The name of the master object is hardcoded in the
9 parser (to "secure/master").
MG Mud User88f12472016-06-24 23:31:02 +020010
Zesstra7ea4a032019-11-26 20:11:40 +010011 The master is the gateway between the interpreter and the
12 mudlib to perform actions with mudlib specific effects. Calls
13 to the master by the interpreter have an automatic catch() in
14 effect. Functions to be called by the driver can be public
15 or static, but not private.
MG Mud User88f12472016-06-24 23:31:02 +020016
Zesstra7ea4a032019-11-26 20:11:40 +010017 Note that the master is loaded first of all objects. Thus you
18 shouldn't inherit an other object, nor is the compiler able to
19 search include files (read: they must be specified with full
20 path).
MG Mud User88f12472016-06-24 23:31:02 +020021
Zesstra7ea4a032019-11-26 20:11:40 +010022 Amylaar says: actually, you can inherit, but the file will be
23 loaded then before the master, which isn't good for most
24 files.
MG Mud User88f12472016-06-24 23:31:02 +020025
Zesstra7ea4a032019-11-26 20:11:40 +010026 Refer to 'master-all' for the survey of the masters internals.
MG Mud User88f12472016-06-24 23:31:02 +020027
28SEE ALSO
Zesstra7ea4a032019-11-26 20:11:40 +010029 master-all(M)
30 efun(E), applied(A), concepts(C), driver(D), lpc(LPC)