Logging ------- :Author: John Torjo
:Review Manager: Need Volunteer
:Download: http://torjo.com/log2/
:Description: Used properly, logging is a very powerful tool. Besides aiding debugging/testing, it can also show you how your application is used. The Boost Logging Library allows just for that, supporting a lot of scenarios, ranging from very simple (dumping all to one destination), to very complex (multiple logs, some enabled/some not, levels, etc). It features a very simple and flexible interface, efficient filtering of messages, thread-safety, formatters and destinations, easy manipulation of logs, finding the best logger/filter classes based on your application's needs, you can define your own macros and much more!
I have a question. I'm currently working on my own logging implementation (you may remember I've written about this work earlier) that I supposed to propose to Boost in the end, and I can see the enormous effort John have put into his implementation. Although my work
Thanks :) But it was certainly a blast ;)
is at the alpha stage, I intend to continue it regardless of the results of John's library review.
This makes sense. You put a lot of effort in your lib, and if you're like me, you'll certainly want to finish it - no matter what ;)
My question is, will my library be needed in Boost if it accepts John's implementation? Would it be reasonable to bother everyone with yet another logging solution if Boost already has one? Are there any regulations or considerations on this?
On this part - I don't know.
And another question. If my library goes on its own, is it possible to release it under the Boost license?
I certainly think so. Check out: http://cdiggins.com/profiler/ Best, John http://John.Torjo.com -- C++ expert ... call me only if you want things done right