Message Logging

In general, once they get beyond a basic debugging stage, modules in their default instance should perform their job quietly, reporting only severe error conditions. The level of reporting should be controlled via the SetVerbosity() member function of the module, with higher values corresponding to more detailed messages or less severe errors. Error logging is provided through the module context, providing a consistent message management for all modules sharing a context. Within the module, the error logging proceeds via a call to the ErrorLog() function, which returns on ostream to which messages are written:

ErrLog() << "No TPhEventHeader!" << endl;

At this point this is just a front-end to which a more powerful logging engine will be added as soon as possible.