January 2008 - Boost - lists.preview.boost.org

[log] Boost Logging v2 - new version (v0.13.6)
by John Torjo 09 Jan '08

09 Jan '08

Boost Logging v2 - new version (v0.13.6) The Boost Logging Lib v2 is getting closer and closer to its review (Feb 4). I've just released a new version, lots of new features: * added tags (attributes a logged message can have, like : line & file, function name, time, etc.) * scoped logs * caching messages before logs are initialized * high precision time (as tag as well) * added spacer formatter - you can specify what goes before and after your formatter * new formatter: named_spacer : Allows you to contain multiple formatters. You have a spacer string, and within it, you can escape your contained formatters * new destination : named - like named_spacer, but for destinations All in all, I've added quite a few features - so, take a look! Look forward to your feedback! http://www.torjo.com/log2/ http://torjo.blogspot.com/2008/01/boost-logging-v2-new-version-v0136.html Best, John -- http://John.Torjo.com -- C++ expert ... call me only if you want things done right

2 1

formal review of Switch library ends tomorrow (Wednesday, January 9th) - reviews needed
by Stjepan Rajko 08 Jan '08

08 Jan '08

The formal review of Switch library by Steven Watanabe is scheduled to end tomorrow, January 9th. I have only received one review (privately) so far, and hope that those participating in the discussions about the library (as well as any other interested boosters) would be willing to contribute a few more - a summary of your final thoughts with a vote would be greatly appreciated. If you need a little extra time to finish out the discussions or write the review, please let me know as we can extend the review period for a few days if necessary. Please feel free to submit your reviews to the list, or privately to me. As a reminder, here are some questions you may want to answer in your review: * What is your evaluation of the design? * What is your evaluation of the implementation? * What is your evaluation of the documentation? * What is your evaluation of the potential usefulness of the library? * Did you try to use the library? With what compiler? Did you have any problems? * How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? * Are you knowledgeable about the problem domain? And finally, every review should answer this question: * Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. Thanks again to those that have been participating in the discussions and/or have already submitted a review. Regards, Stjepan

1 0

[bjam] can't build boost (latest version from SVN)
by John Torjo 08 Jan '08

08 Jan '08

Hi all, After getting latest boost from svn (and latest bjam), can't build it. I've attached the error. Command line: bjam toolset=msvc (note: simple 'bjam' generates the same error) Best, John -- http://John.Torjo.com -- C++ expert ... call me only if you want things done right warning: Graph library does not contain optional GraphML reader. note: to enable GraphML support, set EXPAT_INCLUDE and EXPAT_LIBPATH to the note: directories containing the Expat headers and libraries, respectively. warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. WARNING: No python installation configured and autoconfiguration failed. See http://www.boost.org/libs/python/doc/building.html for configuration instructions or pass --without-python to suppress this message and silently skip all Boost.Python targets Building Boost.Regex with the optional Unicode/ICU support disabled. Please refer to the Boost.Regex documentation for more information (don't panic: this is a strictly optional feature). Skipping build of: ./headers <build>no in common properties Skipping build of: ./headers <build>no in common properties Skipping build of: ./headers <build>no in common properties Skipping build of: ./headers <build>no in common properties Skipping build of: libs/python/build/boost_python <build>no in common properties D:/john/code/latest_boost/tools/build/v2/build\virtual-target.jam:423: in _adjust-name from module object(file-target)@1277 error: <tag>@rulename is present but is not the only <tag> feature D:/john/code/latest_boost/tools/build/v2/build\virtual-target.jam:215: in abstract-file-target.__init__ from module object(file-target)@1277 D:/john/code/latest_boost/tools/build/v2/build\virtual-target.jam:531: in object(file-target)(a)1277.__init__ from module object(file-target)@1277 D:/john/code/latest_boost/tools/build/v2/kernel\class.jam:93: in class.new from module class D:/john/code/latest_boost/tools/build/v2/build\generators.jam:449: in generated-targets from module object(C-compiling-generator)@22 D:/john/code/latest_boost/tools/build/v2/build\generators.jam:362: in construct-result from module object(C-compiling-generator)@22 D:/john/code/latest_boost/tools/build/v2/build\generators.jam:328: in run-really from module object(C-compiling-generator)@22 D:/john/code/latest_boost/tools/build/v2/build\generators.jam:299: in object(C-compiling-generator)(a)22.run from module object(C-compiling-generator)@22 D:/john/code/latest_boost/tools/build/v2/build\generators.jam:840: in try-one-generator-really from module generators D:/john/code/latest_boost/tools/build/v2/build\generators.jam:902: in try-one-generator from module generators D:/john/code/latest_boost/tools/build/v2/build\generators.jam:1108: in construct-really from module generators D:/john/code/latest_boost/tools/build/v2/build\generators.jam:1184: in construct from module generators D:/john/code/latest_boost/tools/build/v2/build\generators.jam:914: in generators.construct-types from module generators D:/john/code/latest_boost/tools/build/v2/build\generators.jam:502: in convert-to-consumable-types from module object(linking-generator)@20 D:/john/code/latest_boost/tools/build/v2/build\generators.jam:560: in convert-multiple-sources-to-consumable-types from module object(linking-generator)@20 D:/john/code/latest_boost/tools/build/v2/build\generators.jam:314: in run-really from module object(linking-generator)@20 D:/john/code/latest_boost/tools/build/v2/build\generators.jam:299: in generator.run from module object(linking-generator)@20 D:/john/code/latest_boost/tools/build/v2/tools\builtin.jam:750: in object(linking-generator)(a)20.run from module object(linking-generator)@20 D:/john/code/latest_boost/tools/build/v2/build\generators.jam:840: in try-one-generator-really from module generators D:/john/code/latest_boost/tools/build/v2/build\generators.jam:902: in try-one-generator from module generators D:/john/code/latest_boost/tools/build/v2/build\generators.jam:1108: in construct-really from module generators D:/john/code/latest_boost/tools/build/v2/build\generators.jam:1184: in generators.construct from module generators D:/john/code/latest_boost/tools/build/v2/tools\builtin.jam:494: in object(lib-generator)(a)5.run from module object(lib-generator)@5 D:/john/code/latest_boost/tools/build/v2/build\generators.jam:840: in try-one-generator-really from module generators D:/john/code/latest_boost/tools/build/v2/build\generators.jam:902: in try-one-generator from module generators D:/john/code/latest_boost/tools/build/v2/build\generators.jam:1108: in construct-really from module generators D:/john/code/latest_boost/tools/build/v2/build\generators.jam:1184: in generators.construct from module generators D:/john/code/latest_boost/tools/build/v2/build\targets.jam:1402: in construct from module object(typed-target)@290 D:/john/code/latest_boost/tools/build/v2/build\targets.jam:1231: in object(typed-target)(a)290.generate from module object(typed-target)@290 D:/john/code/latest_boost/tools/build/v2/build\targets.jam:751: in generate-really from module object(main-target)@1258 D:/john/code/latest_boost/tools/build/v2/build\targets.jam:724: in object(main-target)(a)1258.generate from module object(main-target)@1258 D:/john/code/latest_boost/tools/build/v2/build\targets.jam:255: in object(project-target)(a)276.generate from module object(project-target)@276 D:/john/code/latest_boost/tools/build/v2/build\targets.jam:874: in targets.generate-from-reference from module targets D:/john/code/latest_boost/tools/build/v2/build\targets.jam:1149: in generate-dependencies from module object(alias-target-class)@75 D:/john/code/latest_boost/tools/build/v2/build\targets.jam:1203: in object(alias-target-class)(a)75.generate from module object(alias-target-class)@75 D:/john/code/latest_boost/tools/build/v2/build\targets.jam:751: in generate-really from module object(main-target)@355 D:/john/code/latest_boost/tools/build/v2/build\targets.jam:724: in object(main-target)(a)355.generate from module object(main-target)@355 D:/john/code/latest_boost/tools/build/v2/build\targets.jam:255: in object(project-target)(a)31.generate from module object(project-target)@31 D:/john/code/latest_boost/tools/build/v2\build-system.jam:414: in load from module build-system D:\john\code\latest_boost\tools\build\v2/kernel\modules.jam:261: in import from module modules D:\john\code\latest_boost\tools\build\v2/kernel/bootstrap.jam:132: in boost-build from module D:\john\code\latest_boost\boost-build.jam:11: in module scope from module

4 7

thread_specific_ptr<void>
by Edd Dawson 08 Jan '08

08 Jan '08

Hello, Currently one cannot create a thread_specific_ptr<void> as the return type of thread_specific_ptr<void>::operator* would be void&. So is there any technical reason that we cannot do the same trick as with shared_ptr? i.e. have operator* return a thread_specific_ptr_traits<T>::reference, which would be void in the thread_specific_ptr_traits<void> specialisation, allowing client code to compile so long as operator* is not called. I'd be happy to put a patch together (against the SVN trunk, I assume?). Kind regards, Edd

2 5

Re: [boost] upcoming Switch library review Jan 5th - Jan 9th
by Steven Watanabe 08 Jan '08

08 Jan '08

AMDG "Stjepan Rajko" <stipe(a)asu.edu> wrote: > Hi Alexander, > > Thanks for the example and the assembly analysis. Off the top of my > head, it doesn't seem like it would be too difficult to add support > for fall-through directly (e.g., by taking an (optional?) sequence of > MPL bool constants to specify whether a case should fall through or > break/return). Although, the difficult part might be deciding how to > deal with return values in this case. > > Steven, what do you think? > Of course, we can't use the return value of a case that should fall through to the next case... For non-void return types we could make an actual return type of void indicate fallthrough. Hmmm... That seems too error prone. How about creating a fallthrough_t for the return type? In Christ, Steven Watanabe

1 0

Simple script for checking each header file alone for proper inclusions, ...
by Jens Seidel 08 Jan '08

08 Jan '08

Hi, as most of you know I check from time to time public header files in trunk for proper inclusions and other errors. I most of the time use a g++ 4.3 snapshot and strongest compiler warning options to avoid getting errors or warnings in user code once a new version of Boost is released. There are still many bugs pending in Trac and most are ignored since more than 3 months but John asked me to publish my script. It is indeed very simple but finds nervertheless sufficient errors to be useful. It can probably be extended to check for circular dependencies, ... The usage is simple: Just start boost-check from boost/ with option -l followed by the directoy you want to test: $ ../boost-check -l iostreams It outputs each header file it checks together with possible compiler output (warnings and errors). As I start it in a Linux environment I have to skip all win32 related files as these will create errors (missing windows.h, ...). All files to be skipped can be added to a file (I call it "skip") which is respected by the script. Also all files which include skipped files will be skipped. Once an error is found I prefer to open the file in the vim editor so that I can inspect the problem. vim supports the command ":make" which calls a trivial Makefile (in /tmp) and jumps to all errors and warnings (usual :cw, :cn, :cN commands). I currently commented the call to vim out but you can outcomment it at the end of the script again. I doubt that it will currently be useful for others as I tested already all libraries with active maintainer but you maybe want to test current code changes prior to commit with it (so it found e.g. today an error in iostream introduced during the last hours). Jens

3 3

libXXX
by Lars Schouw 08 Jan '08

08 Jan '08

How come my source code that uses boost wants a libXXX in front of the libraries but boost was build without it. Lars ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping

3 2

Re: [boost] Visual Studio 2008
by Lars Schouw 08 Jan '08

08 Jan '08

I seem to have been blind the file was build and is there.. Lars ----- Original Message ---- From: Lars Schouw <schouwla(a)yahoo.com> To: boost(a)lists.boost.org Sent: Tuesday, January 8, 2008 11:23:30 PM Subject: Re: [boost] Visual Studio 2008 John, Thanks that seems to work for me. When I build boost is does not libboost_serialization-vc90-mt-1_35.lib for me but only boost_wserialization-vc90-mt-1_35.dll How can I build libboost_serialization-vc90-mt-1_35.lib ? Lars ----- Original Message ---- From: John Maddock <john(a)johnmaddock.co.uk> To: boost(a)lists.boost.org Sent: Monday, January 7, 2008 7:01:16 PM Subject: Re: [boost] Visual Studio 2008 Lars Schouw wrote: > Lars > > > Does boost build and run the regression tests for Microsoft Visual > Studio 2008? For current Trunk and release branch yes, see: http://beta.boost.org/development/testing.html For Boost-1.34.1 and earlier no: VS2008 wasn't available when that was signed off on. HTH, John. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs

1 0

Re: [boost] Visual Studio 2008
by Lars Schouw 08 Jan '08

08 Jan '08

John, Thanks that seems to work for me. When I build boost is does not libboost_serialization-vc90-mt-1_35.lib for me but only boost_wserialization-vc90-mt-1_35.dll How can I build libboost_serialization-vc90-mt-1_35.lib ? Lars ----- Original Message ---- From: John Maddock <john(a)johnmaddock.co.uk> To: boost(a)lists.boost.org Sent: Monday, January 7, 2008 7:01:16 PM Subject: Re: [boost] Visual Studio 2008 Lars Schouw wrote: > Lars > > > Does boost build and run the regression tests for Microsoft Visual > Studio 2008? For current Trunk and release branch yes, see: http://beta.boost.org/development/testing.html For Boost-1.34.1 and earlier no: VS2008 wasn't available when that was signed off on. HTH, John. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

1 0

[floating point utilities] new version
by Johan Råde 08 Jan '08

08 Jan '08

Hi, I have uploaded version 3 of the floating point utilities library to the vault. The library is in the folder Math - Numerics. The library provides portable and optimized implementations of isnan, fpclassify, signbit etc. It also provides facets for portable handling of infinity and NaN in text streams. If you want text files with floating point numbers to be portable, and if the files may contain infinity or NaN, then you should use this library. This also applies to text serialization archives. Compared with version 2, there are only minor changes: 1. I have removed all use of partial template specialization and I have added BOOST_TYPENAME and BOOST_STATIC_CONSTANT macros. Now the library should work with older compilers, such as MSVC 6.5. 2. I now use the header boost/detail/endian.hpp. (I didn't before, because I didn't trust that header. But I now think it is better to use endian.hpp, and to fix any problems with the header as they show up.) 3. General code clean-up and simplification. 4. More discussion of portability issues in the docs. There are no changes to the interface. If anyone has time to test the library, I would be interested in the results. Thank you, Johan Råde

2 5