Every subclass of Logger has to call this constructor from their constructor. It sets the LogLevel, and creates a fatal handler. The fatal handler will throw an Error if a log call is made with level LogLevel.fatal.
This template provides the log functions for the Logger class with the LogLevel encoded in the function name.
Signals that the message has been written and no more calls to logMsgPart follow.
This method allows forwarding log entries from one logger to another.
This method logs data with the LogLevel of the used Logger.
This function logs data to the used Logger with a specific LogLevel.
This function logs data to the used Logger depending on a explicitly passed condition with the LogLevel of the used Logger.
This function logs data to the used Logger with the LogLevel of the used Logger.
Logs a part of the log message.
This function logs data to the used Logger with a specific LogLevel and depending on a condition in a printf-style manner.
This function logs data to the used Logger with a specific LogLevel in a printf-style manner.
This function logs data to the used Logger depending on a condition with the LogLevel of the used Logger in a printf-style manner.
This method logs data to the used Logger with the LogLevel of the this Logger in a printf-style manner.
A custom logger must implement this method in order to work in a MultiLogger and ArrayLogger.
This delegate is called in case a log message with LogLevel.fatal gets logged.
The LogLevel determines if the log call are processed or dropped by the Logger. In order for the log call to be processed the LogLevel of the log call must be greater or equal to the LogLevel of the logger.
LogEntry is a aggregation combining all information associated with a log message. This aggregation will be passed to the method writeLogMsg.
This template provides the log functions for the Logger class with the LogLevel encoded in the function name.
This class is the base of every logger. In order to create a new kind of logger a deriving class needs to implement the writeLogMsg method. By default this is not thread-safe.
It is also possible to override the three methods beginLogMsg, logMsgPart and finishLogMsg together, this option gives more flexibility.