| MG Mud User | 88f1247 | 2016-06-24 23:31:02 +0200 | [diff] [blame^] | 1 | SYNOPSIS |
| 2 | void runtime_warning( string msg, string curobj, string prog, int line |
| 3 | , int inside_catch) |
| 4 | |
| 5 | DESCRIPTION |
| 6 | This function is called to let the mudlib handle a runtime warning, |
| 7 | e.g. by logging it into a database. |
| 8 | |
| 9 | <msg> is the warning message. |
| 10 | <curobj> is the name of the current object which caused the message |
| 11 | (the object itself might already be destructed), or 0 if there |
| 12 | is none. |
| 13 | <prog>, <line> determine the name of the program and the line where |
| 14 | the error occured if the current object exists, otherwise |
| 15 | they are 0. |
| 16 | <inside_catch> : != 0 if the warning occurs inside a catch(). |
| 17 | |
| 18 | The driver is limited to three nested warnings, to prevent |
| 19 | an endless recursion in case runtime_warning() itself causes |
| 20 | warnings. |
| 21 | |
| 22 | HISTORY |
| 23 | Introduced in LDMud 3.3.551. |
| 24 | LDMud 3.3.705 added the <inside_catch> argument. |
| 25 | |
| 26 | SEE ALSO |
| 27 | runtime_error(M) |