| MG Mud User | 88f1247 | 2016-06-24 23:31:02 +0200 | [diff] [blame] | 1 | NAME |
| 2 | master |
| 3 | |
| 4 | DESCRIPTION |
| 5 | 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"). |
| 10 | |
| 11 | 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. |
| 15 | |
| 16 | Note that the master is loaded first of all objects. Thus you |
| 17 | shouldn't inherit an other object, nor is the compiler able to |
| 18 | search include files (read: they must be specified with full |
| 19 | path). |
| 20 | |
| 21 | Amylaar says: actually, you can inherit, but the file will be |
| 22 | loaded then before the master, which isn't good for most |
| 23 | files. |
| 24 | |
| 25 | Refer to 'master-3.2' and 'master-3.2.1' for the surveys of |
| 26 | the masters internals. |
| 27 | |
| 28 | SEE ALSO |
| 29 | master-3.2(M), master-3.2.1(M) |
| 30 | efun(E), applied(A), concepts(C), driver(D), lpc(LPC) |