Warning, /FWCore/MessageLogger/doc/TODO is written in an unsupported language. File is not indexed.
0001 TODO list
0002 ---------
0003 Before Phase 1 Initial Release
0004 ------------------------------
0005
0006
0007 <ALL DONE!>
0008
0009
0010 To Complete Phase 1
0011 -------------------
0012
0013 <ALL DONE!>
0014
0015
0016 Known for Phase 2
0017 -----------------
0018
0019 statistics destination(s)
0020
0021 Destination connecting to log4cplus - set up the basics involving
0022 EventFilter package dependency and so forth.
0023
0024 Destination connecting to log4cplus - polish
0025
0026 Information order (is time etc first or last...)
0027
0028 Default behaviour (particularly destination) if none provided.
0029
0030 Deal with case of ofstream failing to construct.
0031
0032 Multiple types in a message ID (note - this requires ErrorLogger work) -
0033 we need first to discuss the meaning of this, both in filtering and in
0034 statistics.
0035
0036 Vet the Guide to Issuing CMS MessageLogger Messages
0037
0038 If no destinations attached, re-enable cerr (may already be done)
0039
0040 Add string name for debug's severity of DEBUG to map (may already be done)
0041
0042 Figure out how CMS wants to specify which directory the log files should go to
0043
0044 other filtering options
0045
0046 context
0047
0048 endl support
0049
0050 multi-statement message building
0051
0052 logger control after configuration - first decide if this is to be done at all
0053
0054 Recommended options
0055 -------------------
0056
0057 Way to incorporate Module name
0058
0059
0060 ErrorLogger has a scheme for establishing debug verbosity levels and
0061 discriminating about whether a given message will be rapidly discarded
0062 based on the level assigned. The LogDebug mechanism should be able to
0063 exploit that scheme.
0064
0065
0066 Plausible options
0067 -----------------