/
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/
.\"log errors intelligently
.TH LOG_ERROR 4

.SH NAME
log_error \- log errors intelligently

.SH SYNOPSIS
void log_error(string file, string message)

.SH DESCRIPTION
Whenever an error occurs during compilation, the function log_error in
the master object is called with the filename that the error occurred
in and the error message itself.  Then, log_error is free to do
whatever it thinks it should do with that information.  Usually this
is deciding based on the filename where the error message should be
logged, and then writing it to that file.

.SH AUTHOR
Wayfarer@Portals