July 2007 - Boost-users - lists.boost.org

[iostreams] missing stream_facade
by Cheng Lian 26 Jul '07

26 Jul '07

Hi, all I was playing around with iostreams recently, and I found that some examples of iostreams include the header file: boost/iostreams/stream_facade.hpp But I cannot find this header any where. I noticed that in the 1.34 release, iostreams is entirely outdated, and I waited until 1.34.1, but this mysterious header is still missing. I apologize if the file just stands right there but somehow I managed to miss it. Also, I think there should be a Jamfile to compile and test the examples. The documentation is pretty useful but well organized and offers many code snippet but never a compilable example as a whole. Fortunately the test cases offered many useful use cases :-) Cheers Cheng

1 0

[serialisation]Portable Binary Archives
by Hughes, James 25 Jul '07

25 Jul '07

Hello all, Probably answered before, but I wondered whether there is a standard implementation for portable binary archives available. I have found a reference here (http://programmicon.com/2007/03/07/the-un-fun-stuff/) I noticed some recent posts on the subject, but haven't found out much info googling. Cheers James This message (including any attachments) contains confidential and/or proprietary information intended only for the addressee. Any unauthorized disclosure, copying, distribution or reliance on the contents of this information is strictly prohibited and may constitute a violation of law. If you are not the intended recipient, please notify the sender immediately by responding to this e-mail, and delete the message from your system. If you have any questions about this e-mail please notify the sender immediately.

7 21

[regex] 1.34.1 vc71.mak problem
by Kyle Alons 25 Jul '07

25 Jul '07

The .mak file produces -1_34.lib files, but linking w/ regex expects -1_34_1.lib files. -- --------------------- Kyle Alons http://www.kinook.com

2 1

Re: [Boost-users] [thread] comparison with Intel Threading BuildingBlocks
by Ovanes Markarian 25 Jul '07

25 Jul '07

On Wed, July 25, 2007 16:15, Andrew Holden wrote: > Ovanes Markarian wrote: >> >> Do you mean that TBB is more like a "future" which might be >> added to the upcoming tr2? > > It's possible. According to TBB's FAQ, Intel is working with the C++ > standards group towards this goal. The FAQ entry can be found at > http://softwarecommunity.intel.com/tbbWiki/FAQ/647.htm. The proposal > can be found at > http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n2104.pdf. Thanks for you link, a very interesting one ;) I ment this one in my previous post: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2276.html With Kind Regards, Ovanes Markarian

2 1

[thread] comparison with Intel Threading Building Blocks
by Toon Knapen 25 Jul '07

25 Jul '07

I just received (again) some doc on the Intel Threading Building Blocks (TBB) (http://www.threadingbuildingblocks.org/) I was wondering how the boost.thread developers/supporters would compare TBB with boost.thread (btw: the book of James Reinders on TBB mentions boost.thread) ? thanks in advance, t

2 1

Intel 9.1 compile errors
by Dilian Kupenov 25 Jul '07

25 Jul '07

Hi, I'm relativly new user of Boost and up to this point I haven't any problems. Building and using the library with MSVC 8 hasn't cause any problems to me. Now I'm trying to compile Boost 1.34.1 with the Intel 9.1 compiler but I'm getting very strange compilation errors. I'm using the latest version of the bjam and I have set the toolset like this: using intel-win : 9.1 : "C:/Program Files/Intel/Compiler/C++/9.1/IA32/Bin/icl.exe" ; Usually most of the files in evry sublibrary compile but 2-3 fail. For example: compile-c-c++ bin.v2\libs\test\build\intel-win-9.1\debug\threading-multi\exception_safety.obj Intel(R) C++ Compiler for 32-bit applications, Version 9.1 Build 20060706Z Package ID: W_CC_C_9.1.028 Copyright (C) 1985-2006 Intel Corporation. All rights reserved. icl -Qvc8 "-Qlocation,link,C:\Program Files\Microsoft Visual Studio 8\VC\bin" libs\test\src\exception_safety.cpp -Fobin. v2\libs\test\build\intel-win-9.1\debug\threading-multi\exception_safety.obj -TP /Z7 /Od /Ob0 /W3 /GR /MDd /Zc:forScope / Zc:wchar_t /GB /Op /Qwn5 /Qwd985 -Qoption,c,--arg_dep_lookup /Zc:forScope /Qansi_alias /Zc:wchar_t -D_NATIVE_WCHAR_T_DEF INED -Qoption,cpp,--arg_dep_lookup /wd4675 /EHs -c -DBOOST_ALL_NO_LIB=1 -DBOOST_TEST_DYN_LINK=1 -I. exception_safety.cpp .\boost/test/impl/exception_safety.ipp(453): error: namespace "std" has no member "isprint" if( std::isprint( c ) ) ^ detected during instantiation of "void boost::itest::<unnamed>::format_execution_path(boost::wrap_stringstream &, ExecPathIt, ExecPathIt, unsigned int) [with ExecPathIt=boost::itest::execution_path_point *]" compilation aborted for libs\test\src\exception_safety.cpp (code 2) call "C:/Program Files/Intel/Compiler/C++/9.1/IA32/Bin//iclvars.bat" > nul icl @"bin.v2\libs\test\build\intel-win-9.1\debug\threading-multi\exception_safety.obj.rsp" ...failed compile-c-c++ bin.v2\libs\test\build\intel-win-9.1\debug\threading-multi\exception_safety.obj... I'll be very thankful for any suggestions and comments. Regards Dido ----------------------------------------------------------------- С бензин в кръвта! http://auto-motor-und-sport.bg/

1 0

[asio] best strategy for creating lots of timers
by Yuval Ronen 25 Jul '07

25 Jul '07

Hi. I'm writing an application that uses many timers in many places. I'd like to use asio::deadline_timer for this purpose, and an asio::deadline_timer requires an instance of asio::io_service to function. The easy way to do it is to create an asio::io_service along side with each instance of deadline_timer. However, I fear that this is may be wasteful in terms of OS resources. So my first question is whether this is true. If that's true, then I'm not creating an io_service for each deadline_timer, so I must be sharing a single io_service by several timers. The problem with such a solution is that the io_service doesn't know about the timers using it, and especially, it doesn't know how many such timer there are at any given point in time, and if there are any. If the number of timers is zero, then there is no work to be done by the io_service, and the thread calling io_service::run() will be released. This is bad, because when a new timer will be created, it will require that there will be a thread calling io_service::run(). So what's the best solution? One possible way is to accompany each io_service with a dummy deadline_timer that will never expire (expires_from_now(infinity)). This will cause the io_service to not release its thread, until that dummy timer is cancel()ed. Another way is to wrap the call to io_service::run() with a loop that checks a whether it should call run() or wait until some new timer is added (using a boost::condition). There might be other options in addition to these two. What do you think? Yuval

2 2

Compile error using boost::variant
by Eric.Zuur＠shell.com 25 Jul '07

25 Jul '07

Hello, We have the following problem with compiling a piece of code using the Intel 9.1 compiler. The compiler can map the constructor of type_v2 on more than one overloaded constructor of the boost::variant, while in our opinion it should not even concider to use the one that first creates a temporary object (see compiler output). The VC7.1 compiler and the GCC compiler both compile this code correctly. Can someone help us out with this problem? Or does someone has a workaround for this? This is a simplified version of the code: #include <boost/variant.hpp> int main(int argc, char**argv) { typedef boost::variant<int, double> type_v1; typedef boost::variant<char, int, type_v1*> type_v2; type_v1 var1( 10 ); type_v2 var2( &var1 ); return 0; } This is the compiler output: D:\3rdParty\boost\boost/variant/variant.hpp(1342): (col. 9)error: more than one instance of overloaded function "boost::variant<T0_, T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19>::convert_construct [with T0_=char, T1=int, T2=boost::variant<int, double, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_> *, T3=boost::detail::variant::void_, T4=boost::detail::variant::void_, T5=boost::detail::variant::void_, T6=boost::detail::variant::void_, T7=boost::detail::variant::void_, T8=boost::detail::variant::void_, T9=boost::detail::variant::void_, T10=boost::detail::variant::void_, T11=boost::detail::variant::void_, T12=boost::detail::variant::void_, T13=boost::detail::variant::void_, T14=boost::detail::variant::void_, T15=boost::detail::variant::void_, T16=boost::detail::variant::void_, T17=boost::detail::variant::void_, T18=boost::detail::variant::void_, T19=boost::detail::variant::void_]" matches the argument list: function template "void boost::variant<T0_, T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19>::convert_construct(T &, int, boost::mpl::false_) [with T0_=char, T1=int, T2=boost::variant<int, double, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::varian t::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_> *, T3=boost::detail::variant::void_, T4=boost::detail::variant::void_, T5=boost::detail::variant::void_, T6=boost::detail::variant::void_, T7=boost::detail::variant::void_, T8=boost::detail::variant::void_, T9=boost::detail::variant::void_, T10=boost::detail::variant::void_, T11=boost::detail::variant::void_, T12=boost::detail::variant::void_, T13=boost::detail::variant::void_, T14=boost::detail::variant::void_, T15=boost::detail::variant::void_, T16=boost::detail::variant::void_, T17=boost::detail::variant::void_, T18=boost::detail::variant::void_, T19=boost::detail::variant::void_]" function template "void boost::variant<T0_, T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19>::convert_construct(const boost::variant<U0, U1, U2, U3, U4, U5, U6, U7, U8, U9, U10, U11, U12, U13, U14, U15, U16, U17, U18, U19> &, long) [with T0_=char, T1=int, T2=boost::variant<int, double, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_> *, T3=boost::detail::variant::void_, T4=boost::detail::variant::void_, T5=boost::detail::variant::void_, T6=boost::detail::variant::void_, T7=boost::detail::variant::void_, T8=boost::detail::variant::void_, T9=boost::detail::variant::void_, T10=boost::detail::variant::void_, T11=boost::detail::variant::void_, T12=boost::detail::varia t::void_, T13=boost::detail::variant::void_, T14=boost::detail::variant::void_, T15=boost::detail::variant::void_, T16=boost::detail::variant::void_, T17=boost::detail::variant::void_, T18=boost::detail::variant::void_, T19=boost::detail::variant::void_]" argument types are: (boost::variant<int, double, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_> *const, long) detected during instantiation of "boost::variant<T0_, T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19>::variant(const T &) [with T0_=char, T1=int, T2=boost::variant<int, double, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_> *, T3=boost::detail::variant::void_, T4=boost::detail::variant::void_, T5=boost::detail::variant::void_, T6=boost::detail::variant::void_, T7=boost::detail::variant::void_, T8=boost::detail::variant::void_, T9=boost::detail::variant::void_, T10=boost::detail::variant::void_, T11=boost::detail::variant::void_, T12=boost::detail::variant::void_, T13=boost::detail::variant::vo id_, T14=boost::detail::variant::void_, T15=boost::detail::variant::void_, T16=boost::detail::variant::void_, T17=boost::detail::variant::void_, T18=boost::detail::variant::void_, T19=boost::detail::variant::void_, T=boost::variant<int, double, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_, boost::detail::variant::void_> *]" make[1]: *** [obj/Win32_x86_INTEL_Debug/Calculator.obj] Error 2 Regards, Eric Zuur Shell International Exploration and Production B.V. Volmerlaan 8, Postbus 60, 2280 AB Rijswijk, The Netherlands

1 0

Boost 1.34.1 Released
by Thomas Witt 25 Jul '07

25 Jul '07

http://www.boost.org Boost 1.34.1, the latest version of peer-reviewed, portable C++ libraries, has been released. This is a bug fix release addressing many problems with the 1.34.0 release. It is a recommended upgrade for all users of Boost 1.34.0. For a complete list of fixes see the Boost Trac at: http://svn.boost.org/trac/boost/query?status=closed&milestone=Boost +1.34.1 Supported Compilers: New in this release is improved support for the IBM XL C/C++ compiler. Boost is tested on a wide range of compilers and platforms. Since Boost libraries rely on modern C++ features not available in all compilers, not all Boost libraries will work with every compiler. The following compilers and platforms have been extensively tested with Boost, although many other compilers and platforms will work as well. For more information, see the regression test results. * Apple GCC 4.0.1 on Mac OS X. * Borland C++ 5.8.2 on Windows. * GNU C++ o 3.2.x., 3.3.x, 3.4.x, 4.0.x, 4.1.x on Linux o 4.1.x on Solaris o 3.4.x on Windows * HP C++ for Tru64 UNIX 7.1. * HP aC++ A.06.14. * Intel C++ 9.1 on Windows, 9.0 on Linux. * Metrowerks CodeWarrior 9.4 on Windows. * Microsoft Visual C++ 6.0 (sp5, with and without STLport), 7.0, 7.1, 8.0. Note: Boost does not support the non-standard "Safe" C++ Library shipping with Visual C++ 8.0, which may result in many spurious warnings from Boost headers and other standards-conforming C++ code. To suppress these warnings, define the macro _SCL_SECURE_NO_DEPRECATE. * Sun Studio 11 on Solaris. Acknowledgements Thomas Witt managed this release. A great number of people contributed their time and expertise to make this release possible. Special thanks go to Kim Barrett consolidating Boost.Iostreams changes from various branches and Rene Rivera for general build and installation support. -- Thomas Witt witt(a)acm.org

1 0

Sopport for sp_counted_base for HP Itanium aCC compiler
by Baruch Zilber 24 Jul '07

24 Jul '07

Hi, I saw in the official release (1.34.0) that there are couple of implementation for sp_counted_base file according to the compiler and CPU. I notice that there is no implementation for Itanium CPU with aCC compiler. Does someone working of this issue? I implemented a version for this target that use Itanium CPU instruction and I wonder how I can add this to boost Thanks Baruch Zilber This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp

2 1