- Boost-users - lists.preview.boost.org

astar using namespace
by bringiton bringiton 26 Jul '07

26 Jul '07

I've removed the using namespace boost from the astar graph cities example. (I prefer to define namespaces explicitly). //using namespace boost; I've added boost:: to all the type names and it all compiles fine. However, some functions compile without the namespace. ie the following line: WeightMap weightmap = get(boost::edge_weight, g); Can someone please explain why I dont need a boost:: infront of the get?

4 3

[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

[boost][program options] Reading an INI file
by Baranowski, Daniel 24 Jul '07

24 Jul '07

Hello All! Is it possible to parse an INI file with the program options without specifying what is in the INI file first (using options_descriptions)? I already use the program_options library to handle command line and config file based options, but what I'm looking for now is a more traditional ini file interaction. By that I mean where you simply read in the ini file and then can access the category/entry value with something like: INIFile iniFile("MyINIFile.ini"); int myInt = iniFile["Category"]["EntryName"].get<int>(3); // 3 is the default if entry not found In my case, these are options that the user does not need to know about and can only be specified through the configuration file. Therefore, much of the data that is in the options_description is redundant. I've been looking around, and it seems that the parse_config_file() is the standard function to call to parse an INI file, however, that takes an options_description object as the second parameter. I did see in boost/program_options/detail/config_file.hpp where it talks about being able to read standard ini files and how the sections and entries are accessed. Unfortunately, that's buried in the "details" and I don't see any part of the public interface that would allow me to access the ini file. I did read a little about the property_tree library, but that is only available in CVS and I would prefer to stick with one library to handle the program's configuration. Similarly, I have seen plenty of other config libraries out there, but I would prefer to stick with program_options if it can do the job. Thanks for any help! Regards, Daniel ********************************************************************************************** Disclaimer - This email and any files transmitted with it are proprietary and may contain privileged or copyright information. You must not present this message to another party without gaining permission from the sender. If you are not the intended recipient you must not copy, distribute or use this email or the information contained in it for any purpose other than to notify us. If you have received this message in error, please notify the sender immediately, and delete this email from your system. We do not guarantee that this material is free from viruses or any other defects although due care has been taken to minimize the risk. eSafe scanned this email for viruses, vandals and malicious contentAny views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of LSI. **********************************************************************************************

1 0

[serialization] Possible problem using BOOST_CLASS_IMPLEMENTATION and BOOST_CLASS_TRACKING inside another namespace
by Hughes, James 24 Jul '07

24 Jul '07

Hello all, I have tried to use these macros inside my own namespace, but get a raft load of errors, all seemingly to do with being in the wrong namespace. Moving the macros outside my namespace and all works fine (took a while to figure out!). Is this a known issue? Should it be mentioned in the docs if that just the way it has to work. 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.

1 0

[serialization] Is it possible to change the name of pair output in XML
by Hughes, James 24 Jul '07

24 Jul '07

Hi all, I am serialising a map<pair<MyKey,MyValue> > and in the XML is names the sections 'first' and 'second'. Is it possible to tell serialisation to save a particular pair type such that, in the preceding semi-example, it using my text (i.e. "MyKey" and "MyValue") instead of "first" and "second"? 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.

1 0

unable to find a functional version of interprocess
by Robert Schulz 24 Jul '07

24 Jul '07

Hi! I fail to use any yet tried example of the interprocess here comes a log trying to compile doc_vectorstream.cpp from the HEAD revision of the cvs ( fetched using cvs -z3 -d:pserver:anonymous@boost.cvs.sourceforge.net:/cvsroot/boost co -P boost/ ) there seem to miss a Type 'create_only' !? the definition of the former enum boost::interprocess::detail::create_enum_t ha vanished in cvs from 1.7 to 1.8 in detail/utilities.hpp ? This header is not listed in the documentation on http://igaztanaga.drivehq.com/interprocess/index.html :( Can i somewhere get a working snapshot of the headers? I missed tagging in the boost cvs? Many thanks for any help!!! Robert robert@sandra-laptop:~/opt$ g++ --version g++ (GCC) 4.1.2 (Ubuntu 4.1.2-0ubuntu4) **** Build of configuration Debug for project shmem **** make LANG=C all Building file: ../atest/doc_vectorstream.cpp Invoking: GCC C++ Compiler g++ -I"/home/robert/opt/boost/boost" -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MF"atest/doc_vectorstream.d" -MT"atest/doc_vectorstream.d" -o"atest/doc_vectorstream.o" "../atest/doc_vectorstream.cpp" In file included from /home/robert/opt/boost/boost/boost/interprocess/managed_shared_memory.hpp:21, from ../atest/doc_vectorstream.cpp:16: /home/robert/opt/boost/boost/boost/interprocess/detail/managed_memory_impl.hpp:25:48: warning: boost/interprocess/creation_tags.hpp: No such file or directory /home/robert/opt/boost/boost/boost/interprocess/detail/managed_memory_impl.hpp:691: error: 'boost::interprocess::detail::create_enum_t' has not been declared /home/robert/opt/boost/boost/boost/interprocess/detail/managed_memory_impl.hpp:708: error: 'create_enum_t' in namespace 'boost::interprocess::detail' does not name a type /home/robert/opt/boost/boost/boost/interprocess/detail/managed_memory_impl.hpp: In constructor 'boost::interprocess::detail::create_open_func<BasicManagedMemoryImpl>::create_open_func(BasicManagedMemoryImpl*, int)': /home/robert/opt/boost/boost/boost/interprocess/detail/managed_memory_impl.hpp:692: error: class 'boost::interprocess::detail::create_open_func<BasicManagedMemoryImpl>' does not have any field named 'm_type' /home/robert/opt/boost/boost/boost/interprocess/detail/managed_memory_impl.hpp: In member function 'bool boost::interprocess::detail::create_open_func<BasicManagedMemoryImpl>::operator()(void*, size_t, bool) const': /home/robert/opt/boost/boost/boost/interprocess/detail/managed_memory_impl.hpp:696: error: 'm_type' was not declared in this scope /home/robert/opt/boost/boost/boost/interprocess/detail/managed_memory_impl.hpp:696: error: 'DoOpen' is not a member of 'boost::interprocess::detail' /home/robert/opt/boost/boost/boost/interprocess/detail/managed_memory_impl.hpp:697: error: 'DoCreate' is not a member of 'boost::interprocess::detail' /home/robert/opt/boost/boost/boost/interprocess/detail/managed_open_or_create_impl.hpp: At global scope: /home/robert/opt/boost/boost/boost/interprocess/detail/managed_open_or_create_impl.hpp:55: error: expected `)' before ',' token /home/robert/opt/boost/boost/boost/interprocess/detail/managed_open_or_create_impl.hpp:70: error: expected `)' before ',' token /home/robert/opt/boost/boost/boost/interprocess/detail/managed_open_or_create_impl.hpp:85: error: expected `)' before ',' token /home/robert/opt/boost/boost/boost/interprocess/detail/managed_open_or_create_impl.hpp:101: error: expected `)' before ',' token /home/robert/opt/boost/boost/boost/interprocess/detail/managed_open_or_create_impl.hpp:118: error: expected `)' before ',' token /home/robert/opt/boost/boost/boost/interprocess/detail/managed_open_or_create_impl.hpp:134: error: expected `)' before ',' token /home/robert/opt/boost/boost/boost/interprocess/detail/managed_open_or_create_impl.hpp:261: error: 'create_enum_t' is not a member of 'boost::interprocess::detail' /home/robert/opt/boost/boost/boost/interprocess/detail/managed_open_or_create_impl.hpp:261: error: expected primary-expression before 'size' /home/robert/opt/boost/boost/boost/interprocess/detail/managed_open_or_create_impl.hpp:262: error: expected primary-expression before 'mode' /home/robert/opt/boost/boost/boost/interprocess/detail/managed_open_or_create_impl.hpp:262: error: expected primary-expression before 'const' /home/robert/opt/boost/boost/boost/interprocess/detail/managed_open_or_create_impl.hpp:263: error: expected primary-expression before 'construct_func' /home/robert/opt/boost/boost/boost/interprocess/detail/managed_open_or_create_impl.hpp:263: error: variable or field 'priv_open_or_create' declared void /home/robert/opt/boost/boost/boost/interprocess/detail/managed_open_or_create_impl.hpp:263: error: ISO C++ forbids initialization of member 'priv_open_or_create' /home/robert/opt/boost/boost/boost/interprocess/detail/managed_open_or_create_impl.hpp:263: error: making 'priv_open_or_create' static /home/robert/opt/boost/boost/boost/interprocess/detail/managed_open_or_create_impl.hpp:263: error: ISO C++ forbids in-class initialization of non-const static member 'priv_open_or_create' /home/robert/opt/boost/boost/boost/interprocess/detail/managed_open_or_create_impl.hpp:263: error: 'priv_open_or_create' declared as an 'inline' field /home/robert/opt/boost/boost/boost/interprocess/detail/managed_open_or_create_impl.hpp:263: error: template declaration of 'int boost::interprocess::detail::priv_open_or_create' /home/robert/opt/boost/boost/boost/interprocess/detail/managed_open_or_create_impl.hpp: In static member function 'static void boost::interprocess::detail::managed_open_or_create_impl<DeviceAbstraction, FileBased>::create_device(DeviceAbstraction&, const char*, size_t, boost::interprocess::detail::false_)': /home/robert/opt/boost/boost/boost/interprocess/detail/managed_open_or_create_impl.hpp:248: error: 'create_only' was not declared in this scope /home/robert/opt/boost/boost/boost/interprocess/detail/managed_open_or_create_impl.hpp: In static member function 'static void boost::interprocess::detail::managed_open_or_create_impl<DeviceAbstraction, FileBased>::create_device(DeviceAbstraction&, const char*, size_t, boost::interprocess::detail::true_)': /home/robert/opt/boost/boost/boost/interprocess/detail/managed_open_or_create_impl.hpp:255: error: 'create_only' was not declared in this scope /home/robert/opt/boost/boost/boost/interprocess/shared_memory_object.hpp: At global scope: /home/robert/opt/boost/boost/boost/interprocess/shared_memory_object.hpp:59: error: expected `)' before ',' token /home/robert/opt/boost/boost/boost/interprocess/shared_memory_object.hpp:65: error: expected `)' before ',' token /home/robert/opt/boost/boost/boost/interprocess/shared_memory_object.hpp:70: error: expected `)' before ',' token /home/robert/opt/boost/boost/boost/interprocess/shared_memory_object.hpp:135: error: 'boost::interprocess::detail::create_enum_t' has not been declared /home/robert/opt/boost/boost/boost/interprocess/shared_memory_object.hpp:273: error: 'boost::interprocess::shared_memory_object::priv_open_or_create' declared as an 'inline' variable /home/robert/opt/boost/boost/boost/interprocess/shared_memory_object.hpp:273: error: 'bool boost::interprocess::shared_memory_object::priv_open_or_create' is not a static member of 'class boost::interprocess::shared_memory_object' /home/robert/opt/boost/boost/boost/interprocess/shared_memory_object.hpp:273: error: 'create_enum_t' is not a member of 'boost::interprocess::detail' /home/robert/opt/boost/boost/boost/interprocess/shared_memory_object.hpp:274: error: expected primary-expression before 'const' /home/robert/opt/boost/boost/boost/interprocess/shared_memory_object.hpp:275: error: expected primary-expression before 'mode' /home/robert/opt/boost/boost/boost/interprocess/shared_memory_object.hpp:275: error: initializer expression list treated as compound expression /home/robert/opt/boost/boost/boost/interprocess/shared_memory_object.hpp:276: error: expected ',' or ';' before '{' token /home/robert/opt/boost/boost/boost/interprocess/managed_shared_memory.hpp:68: error: expected `)' before 'create_only' /home/robert/opt/boost/boost/boost/interprocess/managed_shared_memory.hpp:79: error: expected `)' before 'open_or_create' /home/robert/opt/boost/boost/boost/interprocess/managed_shared_memory.hpp:90: error: expected `)' before 'open_only' ../atest/doc_vectorstream.cpp: In function 'int main()': ../atest/doc_vectorstream.cpp:37: error: 'create_only' was not declared in this scope make: *** [atest/doc_vectorstream.o] Fehler 1

2 1

Re: [Boost-users] [iostreams] compilation error with wstring
by Chad Walters 24 Jul '07

24 Jul '07

> Date: Tue, 24 Jul 2007 15:48:52 +0200 > From: Pipoun <pipoun(a)gmail.com> > > I'm trying to use the iostream libs using wstring, but I'm struggling > with wstring. > <snip> This might be related to a bug I filed a little while ago -- a simple copy-paste bug as far as I can tell: http://svn.boost.org/trac/boost/ticket/1003 Try applying my patch and see if it fixes it. Chad Walters

2 1

[iostreams] compilation error with wstring
by Pipoun 24 Jul '07

24 Jul '07

Hello, I'm trying to use the iostream libs using wstring, but I'm struggling with wstring. Her is my little piece of code: using namespace std; using namespace boost; struct Formatter { std::wstring operator() ( const match_results<const wchar_t*>& _Match ) { //TODO return wstring(); } }; int main(int argc, char** argv) { wstring File; //skipped steps to put data in wregex Regx(L"bla"); iostreams::wregex_filter Filter( Regx, Formatter() ); iostreams::filtering_wostream Out; Out.push( Filter ); Out.push( iostreams::wfile_sink("FilenameFormatted.txt") ); Out << File; } I'm using boost 1_34. If I compile this code vith vc80 express, I get an error: boost/iostreams/filter/aggregate.hpp(97) : error C2664: 'void boost::iostreams::aggregate_filter<Ch,Alloc>::do_write<Sink>(Sink &,const char *,std::streamsize)' : cannot convert parameter 2 from 'wchar_t *' to 'const char *' I'm a little lost :( Am I doing something wrong? Thank you very much for your help! pipoun

1 0

[foreach] boost_foreach_is_lightweight_proxy doesn't work
by Raider 24 Jul '07

24 Jul '07

Hi, i'm trying to modify rvalue container using Boost.ForEach: #include <string> #include <vector> #include <boost/foreach.hpp> typedef std::vector<std::string> vec; inline boost::mpl::true_ * boost_foreach_is_lightweight_proxy(vec *&, boost::foreach::tag) { return 0; } vec GetVector() { vec v; v.push_back("hello"); v.push_back("world"); return v; } int main() { // compiles ok GetVector().push_back("oh god, it's writable!"); // next line gives "unable to convert `const string' to `string&'" BOOST_FOREACH(std::string& String, GetVector()) String.clear(); return 0; } It doen't compiles (MCVC 8.0) - it looks like boost_foreach_is_lightweight_proxy is ignored. What's wrong?

2 7

Boost.signals has no shared_connection
by gast128 24 Jul '07

24 Jul '07

Dear all, I was playing with Boost.Signals and stumbles across a problem which required something like the equivalent of a shared_connenction, i.e. the last reference to it will finally disconnent. This can of course be simulated with a boost::shared_ptr<scoped_connection>, but native support for it is always preferable. The use is that some change manager returns a connection which goes through several application layers. The time the connection finally arives at destination, it has felt multiple ctor's and dtors: View::View(Doc* p) : m_con(p->Register(&OnUpdate) { } shared_connection Doc::Register(void (View::* pmf)(), View* p) { return m_pCm->Register(pmf, p) } etc.. Or did I not read the documentation properly? Wkr, me

1 0

[statechart]LNK2001 Error on VC 8.0
by Jiang Miao 24 Jul '07

24 Jul '07

Here is a tutorial. I compile succeeded at DEBUG mode, but failed at RELEASE mode. And I got LNK2001 Error. #include <boost/statechart/event.hpp> #include <boost/statechart/state_machine.hpp> #include <boost/statechart/simple_state.hpp> #include <boost/statechart/transition.hpp> namespace sc = boost::statechart; struct EvStartStop : sc::event< EvStartStop > {}; struct EvReset : sc::event< EvReset > {}; struct Active; struct StopWatch : sc::state_machine< StopWatch, Active > {}; struct Stopped; struct Active : sc::simple_state< Active, StopWatch, Stopped > { typedef sc::transition< EvReset, Active > reactions; }; struct Running : sc::simple_state< Running, Active > { typedef sc::transition< EvStartStop, Stopped > reactions; }; struct Stopped : sc::simple_state< Stopped, Active > { typedef sc::transition< EvStartStop, Running > reactions; }; // A state can define an arbitrary number of reactions. That's // why we have to put them into an mpl::list<> as soon as there // is more than one of them // (see Specifying multiple reactions for a state). int main() { StopWatch myWatch; myWatch.initiate(); myWatch.process_event( EvStartStop() ); myWatch.process_event ( EvStartStop() ); myWatch.process_event( EvStartStop() ); myWatch.process_event( EvReset() ); return 0; } //Output Linking... statechart.obj : error LNK2001: unresolved external symbol "public: void __thiscall boost::statechart::detail::no_context<struct EvReset>::no_function(struct EvReset const &)" (?no_function@?$no_context@UEvReset@@@ detail@statechart @boost@@QAEXABUEvReset@@@Z) statechart.obj : error LNK2001: unresolved external symbol "public: void __thiscall boost::statechart::detail::no_context<struct EvStartStop>::no_function(struct EvStartStop const &)" (?no_function@?$no_context@UEvStartStop@@@ detail@statechart @boost@@QAEXABUEvStartStop@@@Z) i:\programme\test\statechart\Release\statechart.exe : fatal error LNK1120: 2 unresolved externals How can I solve the problem? Thank you.

3 2

[statechart] context<>() assert failed in destructor function in VC8.0
by Jiang Miao 24 Jul '07

24 Jul '07

I wrote a simple code. source file: #include <boost/statechart/event.hpp> #include <boost/statechart/transition.hpp> #include <boost/statechart/simple_state.hpp> #include <boost/statechart/state.hpp> #include <boost/statechart/state_machine.hpp> #include <boost/statechart/custom_reaction.hpp> #include <boost/shared_ptr.hpp> #include <boost/weak_ptr.hpp> #include <boost/mpl/list.hpp> #include <iostream> #include <string> using namespace std; namespace sc=boost::statechart; namespace mpl=boost::mpl; struct EvtEat:sc::event<EvtEat>{}; struct EvtStop:sc::event<EvtStop>{}; struct Eating; struct Idle; class Human:public sc::state_machine< Human, Idle > { public: void show(void) { cout<<__FUNCTION__<<endl; } }; struct Idle:sc::state< Idle, Human > { Idle(my_context ctx):my_base(ctx) { context<Human>().show(); //ok }; ~Idle(void) { context<Human>().show(); //assert failed }; }; struct Eating:sc::state< Eating, Human > { Eating(my_context ctx):my_base(ctx) { }; ~Eating(void) { context<Human>(); } }; int main(int argc, char* argv[]) { Human human; human.initiate(); return 0; } /* In debug mode.It output Human::show Assertion failed: dynamic_cast<Target>(x) == x, file p:\programme\libs\boost\include\boost-1_35\boost\cast.hpp, line 97 */ Why does it assert failed and how to modify the source? Thank you.

3 2

Re: [Boost-users] [Serialization] is_serializable trait?
by Roman Perepelitsa 24 Jul '07

24 Jul '07

> Re: [Serialization] is_serializable trait? (Chris Fairles) > > I also took a stab at making a boostified version: > > #include <iostream> > #include <boost/type_traits/config.hpp> > #include <boost/utility/enable_if.hpp> > #include <boost/type_traits/is_fundamental.hpp> > #include <boost/type_traits/detail/yes_no_type.hpp> > #include <boost/type_traits/detail/bool_trait_def.hpp> > > namespace boost { > namespace detail { > > template <class T> > struct has_serialize_mem_fun { > typedef void (T::*SerializationFun)(int &, unsigned); > > template <SerializationFun> > struct A {}; > > template <class Q> > static ::boost::type_traits::yes_type > has_serialize_mem_fun_tester(A<&Q::serialize>*); > > template <class Q> > static ::boost::type_traits::no_type has_serialize_mem_fun_tester(...); > > BOOST_STATIC_CONSTANT(bool, value = > (sizeof(has_serialize_mem_fun_tester<T>(0)) == > sizeof(::boost::type_traits::yes_type))); > > }; > template <typename T, typename IsFundamental = void> > struct is_serializable_impl > { > BOOST_STATIC_CONSTANT(bool, value = has_serialize_mem_fun<T>::value); > }; > > template <typename T> > struct is_serializable_impl<T, typename ::boost::enable_if< > ::boost::is_fundamental<T> >::type> > { > BOOST_STATIC_CONSTANT(bool, value = true); > }; > } > > BOOST_TT_AUX_BOOL_TRAIT_DEF1(is_serializable,T,::boost::detail::is_serializable_impl<T>::value) > > } > > struct A { > template <class Stream> > void serialize(Stream & strm, unsigned version) {} > }; > > struct B {}; > > struct C { void serialize() {} }; > > int main() > { > using namespace std; > cout > << boolalpha > << boost::is_serializable<A>::value << '\n' // true > << boost::is_serializable<int>::value << '\n' // true > << boost::is_serializable<float>::value << '\n' // true > << boost::is_serializable<double>::value << '\n' // true > << boost::is_serializable<char>::value << '\n' // true > << boost::is_serializable<B>::value << '\n' // false > << boost::is_serializable<C>::value << '\n' // false > << boost::is_serializable<string>::value << endl; //false but > should be true > } > > Needs specializations for standard containers as well but this suits > my needs currently. Thoughts? I tried to implement is_non_intrusively_serializable metafunction, but found no general solution. Although I've impelented it for all types which are instances of some class template. For example, it works correctly for vector<int>, some_class<double, string>, etc. Note that it is possible to create metafunction which determines whether type is instance of class template or not. So, we have the following: - is_intrusivelly_serializable metafunction. - is_class_template_instance metafunction. - is_non_intrusively_serializable metafunction, which currently works only for class template instances. Probably someone can implement the last missing case? That is we need is_non_intrusively_serializable implementation for types, which are not class template instances (int, some_nontemplate_class, etc). Here is is_non_intrusively_serializable restricted to class templates. #include <boost/serialization/serialization.hpp> #include <boost/type_traits/remove_cv.hpp> #include <boost/type_traits/detail/yes_no_type.hpp> #include <boost/preprocessor.hpp> #include <boost/static_assert.hpp> #include <boost/serialization/vector.hpp> namespace detail { struct tag {}; using boost::serialization::serialize; #define BOOST_PP_LOCAL_LIMITS (1, 10) #define BOOST_PP_LOCAL_MACRO(N) \ template < \ class Archive, \ template <BOOST_PP_ENUM_PARAMS(N, class I)> class T, \ BOOST_PP_ENUM_PARAMS(N, class T) \ > \ tag serialize( \ Archive & ar, \ T<BOOST_PP_ENUM_PARAMS(N, T)> &, \ const unsigned \ ); #include BOOST_PP_LOCAL_ITERATE() tag operator,(tag, int); boost::type_traits::no_type check(tag); template <class T> boost::type_traits::yes_type check(T const&); template <class T> struct impl { static typename boost::remove_cv<T>::type & x; static const int & archive; static const unsigned version; static const bool value = sizeof(check((serialize(archive, x, version), 0))) == sizeof(boost::type_traits::yes_type); }; } template <class T> struct is_non_intrusively_serializable : detail::impl<T> {}; template <class T> struct A {}; int main() { BOOST_STATIC_ASSERT( is_non_intrusively_serializable<std::vector<int> >::value); BOOST_STATIC_ASSERT( !is_non_intrusively_serializable<A<int> >::value); } Regards, Roman Perepelitsa Deutsche Bank Moscow +7 (495) 660-74-08 --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

1 0

Detecting Valid Expressions for a Type at Compile-Time
by Martin Ecker 24 Jul '07

24 Jul '07

Hi, Is there a way, using SFINAE tricks and potentially the techniques used in the Boost Concept Check Library, to detect at compile-time if a type T supports a certain expression? In my case, I'm interested if T supports operator ==. So I'm basically looking for a compile-time predicate so that this compiles: struct my_struct { int i; }; struct my_struct2 { int i; }; bool operator == (my_struct2 const&, my_struct2 const&) const; BOOST_STATIC_ASSERT((supports_comparison_operator<int>::value)); BOOST_STATIC_ASSERT((!supports_comparison_operator<my_struct>::value)); BOOST_STATIC_ASSERT((supports_comparison_operator<my_struct2>::value)); Thanks, Martin

3 4

Serialization
by Alejandro Rubinos Carbajal 23 Jul '07

23 Jul '07

How can i serialize an object of the class tm that belongs to time.h, and also i will like to serialize a char * object. Thanks

1 0

[intrusive][interprocess] Online documentation site changed
by Ion Gaztañaga 23 Jul '07

23 Jul '07

Hi to all, Due to recent problems with the automatically generated Boost documentation in Boost CVS and some other problems with my old website, I've just uploaded up-to-date (CVS HEAD documentation) Boost.Intrusive and Boost.Interprocess documentation to these sites: http://igaztanaga.drivehq.com/intrusive http://igaztanaga.drivehq.com/interprocess These sites have no ads, so I expect better user experience. I've requested the cancellation of the old site (www.prohosting.com) so I hope this helps Intrusive and Interprocess user experience until Boost 1.35 is released. Regards, Ion

1 0