Windows logger code#

WRITELOG(logger, framework::Diagnostics::LogLevel::Info, _T('Program starting')) LogMainUI.AddOutputStream(os, true, framework::Diagnostics::LogLevel::Info) Logger.AddOutputStream(os, true, framework::Diagnostics::LogLevel::Info) Tostream *os = new std::wofstream('c:\temp\myapp.log')

Windows logger code#

I have tried to use your code as follows::Д¬Logger logger(LogLevel::Info, _T('APP')) Д¬Logger logMainUI(LogLevel::Info, _T('MAIN')) I have a question on the wostream - do you see any contention issues when using multiple logging instances writing(sharing) a single output stream? Thank you for this simple and clean logging utility. Thanks to my wife Meena for always being there and my son Neel for showing how simple it is to have a happy life. Log 4 C++ inspired the overall design of this class. The use of templated classes for performing thread synchronization is based on the concept of policy-classes (refer to 'Modern C++ Design' by 'Andrei Alexander). LOGINFOP(loggerPtr, _T( ' Program Ending')) WRITELOG(logger, framework::Diagnostics::LogLevel::Error, _T( ' Something did go wrong')) Д¬Logger * loggerPtr = &logger // An easy way to use pointer to a logger object WRITELOG(logger, framework::Diagnostics::LogLevel::Warn, _T WRITELOG(logger, framework::Diagnostics::LogLevel::Info, _T( ' Program starting')) True, framework::Diagnostics::LogLevel::Info) Logger.AddOutputStream( new std::wofstream( ' c:\temp\myapp.log'), Logger.AddOutputStream( std::wcout, false, LogLevel::Error) UsageД¬opy Code #include ' threading.h' #include ' Logger.h' #include using namespace framework::Diagnostics Д¬Logger logger(LogLevel::Info, _T( ' MyApp')) Finally to log something, use the WRITELOG macro. Once the CLogger instance is created, we need to add ostream derived objects which perform the actual task of writing something somewhere. When creating an instance of the logger, you need to supply at least one of these or any other class which provides semantically correct Lock() and Unlock() functionality. If you are not sharing a logger object across threads, use the CNoLock class. Use this if you are sharing an instance of CLogger across multiple threads in the same process. As of now, there are two classes which help with this and both are present under the framework::Threading namespace. CLogger takes the help of another class for thread-synchronization functions. It is present in the ' framework:: Diagnostics' namespace. The main class which we need to be concerned about is the CLogger class. The sample code compiled in Visual Studio 2012. However, it should be relatively easy to get the code to work with the older specification for example, replace ' enum class' with just ' enum'.

Please note, the code uses some of the C++ 11 features. h file and is easily understandable and can therefore be easily modified to suit one's needs.

Most logging frameworks provide a plethora of tweaks and formatting options which this little class here does not, and this is precisely why I find using it very easy.

This logging class which I present here is based on ideas from Log 4 C++ in that the usage pattern is similar to Log 4 C++. I wasn't so much as looking for using or even copy pasting available code than I was looking for approaches to logging. There are a lot of good frameworks out there. Recently, I have been on the lookout for a relatively easy to use logging feature for my C++ applications.