5 Aug
2015
5 Aug
'15
2:30 p.m.
I find the simplest things the most frustrating to accomplish in Boost.Log. I know that some compilers have predefined preprocessor macros to provide information. MSVC for example has __LINE__, __FILE__, etc. I need Boost.Log to print line, file, and function information for me in a platform agnostic way. The documentation is not easy to navigate through and find the information I need. Also examples on this are sparse. I've seen some people calling BOOST_LOG_NAMED_SCOPE manually prior to each log statement. This seems unintuitive. How can I simply print this contextual information with each log line in an automated way? Can't Boost.Log piggy-back on compiler features available to it?