[log] Most recent version
Hi, We're going to update boost.log sources in our code base. Could you please recommend what version to use? The code is taken from: https://boost-log.svn.sourceforge.net/svnroot/boost-log/. And currently I consider 3 options: branches/v1 branches/bleeding-edge trunk Thanks in advance. Regards
On December 7, 2012 8:41:57 PM Alexander Arhipenko <arhipjan@gmail.com> wrote:
Hi,
We're going to update boost.log sources in our code base. Could you please recommend what version to use?
The code is taken from: https://boost-log.svn.sourceforge.net/svnroot/boost-log/. And currently I consider 3 options: branches/v1
This is the most recent version 1.x of Boost.Log. It is no longer developed but is is the most stable version.
branches/bleeding-edge
This is the work in progress for v2 of the library. This is the closest thing to what v2 will eventually be and to what will be included to Boost. Currently, the code compiles and shaped more or less. However, it may not compile at times and barely tested as this is where development is going on.
trunk
This is some intermediate v2 that is more stable than bleeding-edge. It is slightly outdated now, I'm planning to merge bleeding-edge to trunk some time soon. The all three versions have source-incompatible differences but in the long run the bleeding-edge interface is what you should be aimed for if you plan to update to newer versions of the library. If you only want some stable version for one time use, you can use the current trunk or v1.
On Sat, Dec 8, 2012 at 11:11 AM, Andrey Semashev <andrey.semashev@gmail.com> wrote:
[snip] ...
The code is taken from: https://boost-log.svn.sourceforge.net/svnroot/boost-log/. And currently I consider 3 options: branches/v1
This is the most recent version 1.x of Boost.Log. It is no longer developed but is is the most stable version.
branches/bleeding-edge
This is the work in progress for v2 of the library. This is the closest thing to what v2 will eventually be and to what will be included to Boost. Currently, the code compiles and shaped more or less. However, it may not compile at times and barely tested as this is where development is going on.
trunk
This is some intermediate v2 that is more stable than bleeding-edge. It is slightly outdated now, I'm planning to merge bleeding-edge to trunk some time soon.
The all three versions have source-incompatible differences but in the long run the bleeding-edge interface is what you should be aimed for if you plan to update to newer versions of the library. If you only want some stable version for one time use, you can use the current trunk or v1.
Hi Andrey, Thanks for clarification. I think we'll stick with v1 and update to the v2 after inclusion into Boost. Could you please point to up-to-date documentation? I've found this one: http://boost-log.sourceforge.net/libs/log/doc/html/index.html. But code samples found on a page: http://boost-log.sourceforge.net/libs/log/doc/html/log/detailed/sources.html seems to be out of date, e.g. statement lg.strm()<<"message" fails to compile. Regards
We've been using the v2 log for over two years now. We're currently working with r738. We're using it with wstrings (Windows), time stamps, scopes, tags, file rollover, multi-thread and levels. I highly recommend it. If you have issues, you'll find Andrey both responsive and helpful. Charles Wilson Senior Software Development Engineer Dell | Enterprise Solutions Group
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost- bounces@lists.boost.org] On Behalf Of Alexander Arhipenko Sent: Saturday, December 08, 2012 5:45 AM To: boost@lists.boost.org Subject: Re: [boost] [log] Most recent version
On Sat, Dec 8, 2012 at 11:11 AM, Andrey Semashev <andrey.semashev@gmail.com> wrote:
[snip] ...
The code is taken from: https://boost-log.svn.sourceforge.net/svnroot/boost-log/. And currently I consider 3 options: branches/v1
This is the most recent version 1.x of Boost.Log. It is no longer developed but is is the most stable version.
branches/bleeding-edge
This is the work in progress for v2 of the library. This is the closest thing to what v2 will eventually be and to what will be included to Boost. Currently, the code compiles and shaped more or less. However, it may not compile at times and barely tested as this is where development is going on.
trunk
This is some intermediate v2 that is more stable than bleeding-edge. It is slightly outdated now, I'm planning to merge bleeding-edge to trunk some time soon.
The all three versions have source-incompatible differences but in the long run the bleeding-edge interface is what you should be aimed for if you plan to update to newer versions of the library. If you only want some stable version for one time use, you can use the current trunk or v1.
Hi Andrey,
Thanks for clarification. I think we'll stick with v1 and update to the v2 after inclusion into Boost.
Could you please point to up-to-date documentation? I've found this one: http://boost-log.sourceforge.net/libs/log/doc/html/index.html. But code samples found on a page: http://boost- log.sourceforge.net/libs/log/doc/html/log/detailed/sources.html seems to be out of date, e.g. statement lg.strm()<<"message" fails to compile.
Regards
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On Mon, Dec 31, 2012 at 6:27 PM, <Charles_J_Wilson@dell.com> wrote:
We've been using the v2 log for over two years now.
We're currently working with r738. We're using it with wstrings (Windows), time stamps, scopes, tags, file rollover, multi-thread and levels.
I highly recommend it.
If you have issues, you'll find Andrey both responsive and helpful.
I've been using it for 6 months now and I can confirm that. Joel Lamotte
on Tue Jan 01 2013, Klaim - Joël Lamotte <mjklaim-AT-gmail.com> wrote:
On Mon, Dec 31, 2012 at 6:27 PM, <Charles_J_Wilson@dell.com> wrote:
We've been using the v2 log for over two years now.
We're currently working with r738. We're using it with wstrings (Windows), time stamps, scopes, tags, file rollover, multi-thread and levels.
I highly recommend it.
If you have issues, you'll find Andrey both responsive and helpful.
I've been using it for 6 months now and I can confirm that.
Can we get the final mini-review on the schedule yet or are there still critical issues that need to be dealt with per http://lists.boost.org/boost-announce/2010/03/0256.php? -- Dave Abrahams BoostPro Computing Software Development Training http://www.boostpro.com Clang/LLVM/EDG Compilers C++ Boost
On Wednesday 02 January 2013 07:18:17 Dave Abrahams wrote:
on Tue Jan 01 2013, Klaim - Joël Lamotte <mjklaim-AT-gmail.com> wrote:
On Mon, Dec 31, 2012 at 6:27 PM, <Charles_J_Wilson@dell.com> wrote:
We've been using the v2 log for over two years now.
We're currently working with r738. We're using it with wstrings (Windows), time stamps, scopes, tags, file rollover, multi-thread and levels.
I highly recommend it.
If you have issues, you'll find Andrey both responsive and helpful.
I've been using it for 6 months now and I can confirm that.
Can we get the final mini-review on the schedule yet or are there still critical issues that need to be dealt with per http://lists.boost.org/boost-announce/2010/03/0256.php?
With regard to code, the issues are fixed and it's ready for review. I'm currently updating the docs. The tutorial is updated but the rest is mostly compliant with v1 and not v2. I can prepare what's ready at this moment and request for a review in a separate topic, if needed. I think, if people are ok with reviewing the code and examples, an early review would be benefical if new requirements arise. Should I do so? In any case, in the meanwhile I will continue updating the docs and hope to have something more consistent by the end of holidays.
On Tue, Jan 1, 2013 at 1:30 PM, Klaim - Joël Lamotte <mjklaim@gmail.com> wrote:
On Mon, Dec 31, 2012 at 6:27 PM, <Charles_J_Wilson@dell.com> wrote:
We've been using the v2 log for over two years now.
We're currently working with r738. We're using it with wstrings (Windows), time stamps, scopes, tags, file rollover, multi-thread and levels.
I highly recommend it.
If you have issues, you'll find Andrey both responsive and helpful.
I've been using it for 6 months now and I can confirm that.
Joel Lamotte
Hi, If you've started praising the library, here is my input ): We are using boost.log in production environment starting from January 2009. Recently upgraded to v1. The upgrade was quite painless. This library really just works. The only issue - it's not in the official release yet. Hope this will change soon. Regards
participants (5)
-
Alexander Arhipenko -
Andrey Semashev -
Charles_J_Wilson＠Dell.com -
Dave Abrahams -
Klaim - Joël Lamotte