[Owasp-esapi-c++] Logging library
Kevin W. Wall
kevin.w.wall at gmail.com
Thu Apr 8 15:29:16 EDT 2004
+1 for log4cpp
On Sun, Aug 21, 2011 at 11:38 PM, David Anderson
<david.anderson at aspectsecurity.com> wrote:
> I researched a bunch of C++ logging libraries, and I did some POC coding
> with log4cpp and Boost:Log. My recommendation is to go with the former.
> The primary reason is that log4cpp is designed to be close to a straight
> port of log4j, which makes our job easier. I should be able to check in a
> log4cpp-based reference implementation this week. It would take a bit
> longer with Boost:Log.
> Both look like good choices to me. Boost:Log is intended to be more
> extensible than log4j, and it is more actively maintained. Boost:Log is
> also quite a bit bigger than log4cpp. It's design is not so close to
> log4j. Also, both are designed to support multi-threaded use, with single
> or multiple loggers as desired. Oh, and Boost:Log urges the use of its
> lovely macros, while log4cpp does not provide a macro layer.
> Any objections to me proceeding with log4cpp?
> Owasp-esapi-c++ mailing list
> Owasp-esapi-c++ at lists.owasp.org
"The most likely way for the world to be destroyed, most experts agree,
is by accident. That's where we come in; we're computer professionals.
We *cause* accidents." -- Nathaniel Borenstein
More information about the Owasp-esapi-c++