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

MultiArrays of Std::Lists: why const iterators?
by Joshua Schpok 12 Nov '05

12 Nov '05

I want to make a 3D array of std::lists: boost::multi_array<std::list<CSomething>,3> listbin; Then I'd like to actually use those lists: /// Walk through list at x,y,z for(std::list<CSomething>::iterator iter = listbin[x][y][z].begin(); reti != iter[x][y][z].end(); iter++) { iter->m_foo += 42; } But multi_array is giving me back *const* list iterators, producing the error: error: conversion from `std::_List_const_iterator<CSomething>' to non-scalar type `std::_List_iterator<CSomething>' requested Why is this so? I can trick the compiler by doing a cast like: std::list<CSomething>::iterator iter = ((std::list<CSomething>)listbin[x][y][z]).begin(); but this seems to poop out at runtime. Is there a proper way to do this? Joshua Schpok

3 2

[bind]How to bind to a template class member function?
by Wang Yun 12 Nov '05

12 Nov '05

Hi, I tried to bind to a class member function template, but can't pass compile, what's the correct syntax or this is impossible? class A { public: void test() { function<void()> func; func = boost::bind( &A::ttt<int>, this ); } template<typename T> T ttt() { return 1; } }; int _tmain(int argc, _TCHAR* argv[]) { return 0; } Thanks, Wang Yun

2 2

[serialization] Incorrect assertion in basic_binary_oprimitive?
by Austin Bingham 12 Nov '05

12 Nov '05

I've run into a situation where I'm triggering an assertion at basic_binary_oprimitive::save_binary(). This is on basic_binary_oprimitive.hpp, line 115 in version 1.32. This assertion seems to be claiming that an output stream will always be in a "good" state after a call to write(). On it's face, I think there's no way to safely make that claim, especially about a stream whose type is a template parameter. In fact, as I understand it, good()'s whole purpose is to let you know that the stream is busted. Am I misunderstanding something, or should that assert be changed to an exception? I'm trying to get an example program that demonstrates this problem. Currently, the code that exercises it is big and hairy, and I haven't pared down the precise conditions that cause it to happen. I can provide a stack trace, however, which may be of some use. -- Austin Bingham "If I were creating the world I wouldn't mess about with butterflies and daffodils. I would have started with lasers, eight o'clock, Day One!" Evil

2 2

When FSM library is released
by Oliver.Kowalke＠infineon.com 11 Nov '05

11 Nov '05

Hello, could you tell me please when the next release of boost with fsm (finite state machine) library will be released? thx, Oliver

3 2

Namespaces for Intrusive Serialization?
by Merrill Cornish 11 Nov '05

11 Nov '05

In the Serialization tutorial, and example is given of the "intrusive" method that looks like this: private: friend class boost::serialization::access; template<class Archive> void serialize(Archive& ar, const unsigned int version) { ar& var1; ar& var2; ar& var3; } There is full namespace qualification on "access" but nothing on "serialize()". It appears that serialize() would be in whatever the prevailing application namespace is (which might not be std). Later in the tutorial there is an example of the "non-intrusive" method that looks like this" namespace boost { namespace serialization { template<class Archive> void serialize(Archive& ar, const unsigned int version) { ar& var1; ar& var2; ar& var3; } }//serialization }//boost which implies that serialize() *DOES* need to be namespace qualified. So, what's really needed? Merrill

3 2

Deploying Boost App: Best Practices?
by Merrill Cornish 11 Nov '05

11 Nov '05

I am building an open source C++ application using various Boost libraries. I am using the libraries as-is without any tweaks, additions, or wrappers to the source or headers. What is the accepted way (if there is one) of deploying a Boost application when the application includes the source under an open source license? Should I distribute only *my* source along with instructions to users who want to compile it to download the Boost libraries? Or, should I include a boost/ subdirectory in my source tree with the Boost headers and libraries my app uses? Merrill

3 2

filesystem::equivalent does not work for UNC paths on Windows
by Daniel Krügler 11 Nov '05

11 Nov '05

Hello! Its seems as if the Windows implementation of filesystem::equivalent can't handle UNC paths. While Windows is usually quite tolerant concerning the path separator / versus \, CreateFile* seems not to understand an UNC path containing // instead of \\. My proposal to fix that is to replace the call of the string() member function by the native_file_string() member function. What do you think? Greetings from Bremen, Daniel

1 1

[filesystem] path::native_file_string() heap issue and
by Brendon Costa 11 Nov '05

11 Nov '05

Hi all, I have been using the boost filesystem library for a little while under NetBSD and all is fine however I have just been porting our application over to windows and have come across a problem with the boost filesystem library (Boost 1.33.0). I am compiling with MinGW (g++ 3.4.2) on a Windows XP system. When debugging our application in gdb i get a SIGTRAP with an Invalid Address specified to RtlFreeHeap. This is when using the path::native_file_string() method. I also have another problem where a SEGFAULT ocurrs when using the boost::filesystem::exists() method, however i think that may be linked to the native_file_string() error. I wrote a small test program as shown below to reproduce the error when using path::native_file_string() #include <iostream> #include <boost/filesystem/operations.hpp> int main() { std::string filename = "test.dat"; boost::filesystem::path boost_filename(filename); std::cout << "Filename: " << filename << std::endl; std::cout << "Boost string(): " << boost_filename.string() << std::endl; std::cout << "Boost native_file_string(): " << boost_filename.native_file_string() << std::endl; return 0; } This compiles fine, and it also will run fine outside of GDB. However if i run it inside GDB i get errors on the line that uses boost_native_file_string() that are shown below: Starting program: X:\msys\Utils_test/./a.exe Program received signal SIGTRAP, Trace/breakpoint trap. 0x7c901231 in _libkernel32_a_iname () (gdb) warning: HEAP[a.exe]: warning: Invalid Address specified to RtlFreeHeap( 003D0000, 003D5138 ) bt #0 0x7c901231 in _libkernel32_a_iname () #1 0x7c96c943 in _libkernel32_a_iname () #2 0x7c96cd80 in _libkernel32_a_iname () #3 0x7c96df66 in _libkernel32_a_iname () #4 0x7c94a5d0 in _libkernel32_a_iname () #5 0x7c9268ad in _libkernel32_a_iname () #6 0x77c2c2de in _libkernel32_a_iname () #7 0x00409855 in operator delete(void*) () at boost_test.cpp:59 #8 0x0042e2dc in std::string::_Rep::_M_destroy(std::allocator<char> const&) () at c:/Boost/include/boost-1_33/boost/filesystem/path.hpp:57 #9 0x00430d68 in std::string::~string() () at c:/Boost/include/boost-1_33/boost/filesystem/path.hpp:57 #10 0x004015d6 in main () at boost_test.cpp:12 (gdb) I also have a larger program where part of its code uses the boost filesystem library that looks like: static std::string GetUnusedFileName(const char* suggestion = "test_file") { int count = 0; std::string base = suggestion; std::string filename(base + ".dat"); while(boost::filesystem::exists(boost::filesystem::path(filename))) { std::ostringstream stream; stream << base << "_" << count << ".dat"; filename = stream.str(); count++; } return filename; } This will usually cause a seg fault when calling the filesystem::exists() method. I currently do not have a stack trace for that and was unable to reproduce one but i think the two errors may be linked. Am i using the system correctly? The code works fine in NetBSD so i assume so. Has this bug been identified in the past and possibly fixed for the 1_33_1_beta release? I started compiling that but there are a few changes i need to make to the build system to go to 1_33_1 that may be time consuming for a problem that may not yet have been addressed anyway. Thanks for any help in advance, Brendon Costa.

1 0

[BGL] Edge descriptors for parallel edges
by Slava 11 Nov '05

11 Nov '05

Say, i have the following structure for edge bundle properties struct EdgeProperty { int edge_type; } and i can add parallel edges, that is between vertices u and v cab be several edges with bundle property EdgeProperty with different edge_types. the first question how can i use edge(u,v,graph) function if it returns std::pair <edge_descriptor,bool>, only one descriptor? but i have several descriptors between two vertices. second, how to change the edge_type provided that i got edge_descriptor from edge(u,v,graph) Thanks.

2 1

[Review] The review of the Boost.Logging library starts November 7th
by Hartmut Kaiser 10 Nov '05

10 Nov '05

Hi all, today starts the review of the Boost.Logging library written by John Torjo. It will end on November 16th. --------------------------------------------------- About the library: As applications are becoming more and more complex, logging is more and more of a must, in nowadays software. The Boost Logging Library is a library that: * makes it very easy to declare/define logs * allows you very simple access to logs * allows you to easily use/manipulate log levels (like, dbg/err/info/etc.) * allows for log hierarchies, and for manipulating log hierarchies * is thread-safe To get you started, here's some basic usage: BOOST_LOGL(app,dbg) << "debugging: " << i << '-' << j << std::endl; BOOST_LOG(app) << "I just wanted to tell you something...."; BOOST_LOGL(app,err) << "this is an error!"; The latest version of the lib can be found here: http://torjo.com/code/logging.zip --------------------------------------------------- Please always state in your review, whether you think the library should be accepted as a Boost library! Additionally please consider giving feedback on the following general topics: - 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? Regards Hartmut Review Manager

1 0

Serialized as what?
by Merrill Cornish 10 Nov '05

10 Nov '05

What external file format does the Boost Serialization Library use? The introduction to the library states the requirement that serialization written by one machine must be readable by a different machine. And, elsewhere, it mentions that and XML intermediate file is on possibility; but I can't seem to find what the format being used is. Merrill

4 3

bidirectional file_descriptor
by Johannes Balle 10 Nov '05

10 Nov '05

Hello, I am currently trying to use the iostreams lib with standard BSD socket() file descriptors. If I understand correctly, I need a "bidirectional" stream buffer, so I tried overriding the mode like this: stream_buffer<file_descriptor, std::char_traits<file_descriptor::char_type>, std::allocator<file_descriptor::char_type>, boost::iostreams::bidirectional> But I cannot instantiate this because a static assertion fails. I assume this happens because the file_descriptor class is defined to be seekable (which a TCP socket is not), so what is the best way to do this? Thanks for your help ... Johannes Ballé Philips Applied Technologies Building SFJ 4.50 Glaslaan 2 5616 LW Eindhoven Tel: +31 40 2734194 E-mail: johannes.balle(a)philips.com

1 0

[program_options] how to use case_insensitive
by Lawry, Brian 10 Nov '05

10 Nov '05

I am using Boost 1.33.0 and MS Visual Studio .NET 2003 (13.10.3077) and having trouble developing a simple Win32 console application that accepts case-insensitive command-line options. -- output ---------------------------------- ..\>app -n 2 BOOST_PROGRAM_OPTIONS_VERSION=2 count set to 2 ..\>app -N 2 BOOST_PROGRAM_OPTIONS_VERSION=2 Exception caught: unknown option -N -------------------------------------------- -- code ------------------------------------ #include <boost/program_options.hpp> int _tmain(int argc, _TCHAR* argv[]) { using std::cout; using std::endl; namespace po = boost::program_options; namespace cls = boost::program_options::command_line_style; int count = 0; cout << "BOOST_PROGRAM_OPTIONS_VERSION=" << BOOST_PROGRAM_OPTIONS_VERSION << endl; try { po::options_description desc("Usage"); desc.add_options() ("help,h", "produce help message") ("count,n", po::value<int>(&count), "repeat count") ; po::variables_map vm; int cl_style = 0; cl_style |= cls::allow_short; cl_style |= cls::allow_dash_for_short; cl_style |= cls::short_allow_next; cl_style |= cls::case_insensitive; po::store(po::command_line_parser(argc, argv).options(desc).style(cl_style).run(), vm); po::notify(vm); if (vm.count("count")) cout << "count set to " << count << endl; else cout << "count not set" << endl; } catch( exception &e ) { cout << "Exception caught:\t" << e.what() << endl; } catch(...) { cout << "Unhandled exception caught!" << endl; } } -------------------------------------------- The line "cl_style |= cls::case_insensitive;" seems to have no effect. The other options in that section do seem to work as I can create other errors by omitting others. I tried for a minimal set of styles. Any ideas what I'm doing wrong? Thanks. Brian Lawry Mfg Software Engineer Compressor Controls Corp blawry<insert@here>cccglobal.com

3 2

Compilation problems on VC7 of code uses boost 1.31.0
by Miko Nahum 10 Nov '05

10 Nov '05

Hi I need your example in compilation errors on code uses boost under Windows VC7 and HP-UX 11.11 aCC 3.55 in 64 bit mode. We have the boost 1.31.0 successfully installed and used in our products, in SunOS using Forte 6.5.3 CC, HP 11.11 using aCC 3.33, Windows (W2k, XP) using VC6. While porting our code to 64 bit, we have upgraded the development env` to Forte 8.5.5 CC on Sun, aCC 3.55 on HP and VC7 on Windows. Compilation of boost itself had no problem. However, compilation of our products that using it has been failed on HP and Windows. 1. Problems on Windows: We have the following piece of code that uses boost (copy/paste): #include "boost/regex.h" #include "boost/regex.hpp" using namespace boost; using namespace std; typedef boost::reg_expression<char> re_type; typedef re_type::allocator_type allocator_type; long example_func(long pos, const std::string& regE, long& reslen, long max) { long res; boost::match_results <PData::iterator, allocator_type> m; allocator_type (a); re_type e (a); e.set_expression (regE, regbase::normal); if (regex_search (begin (), end (), m, e, match_not_dot_newline | match_not_dot_null)) <-- line 4790 { res = pos + m.position(); reslen = m.length(); return res; } . . . Compiling the above produce the following error: parser.cpp z:\n2_3rd_party_components\boost\delivery\include\boost\regex\v4\perl_ma tcher_common.hpp(208) : error C2228: left of '.second' must have class/struct/union type type is 'const std::allocator<_Ty>::value_type' with [ _Ty=char ] z:\n2_3rd_party_components\boost\delivery\include\boost\regex\v4\basic_r egex.hpp(243) : while compiling class-template member function 'bool boost::re_detail::perl_matcher<BidiIterator,Allocator,traits,Allocator2> ::find_imp(void)' with [ BidiIterator=PData::iterator, Allocator=allocator_type, traits=boost::regex_traits<char>, Allocator2=std::allocator<char> ] c:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\xlocmon(190) : while compiling class-template member function 'boost::re_detail::perl_matcher<BidiIterator,Allocator,traits,Allocator2 >::perl_matcher(BidiIterator,BidiIterator,boost::match_results<BidiItera tor,Allocator> &,const boost::reg_expression<charT> &,boost::regex_constants::match_flag_type)' with [ BidiIterator=PData::iterator, Allocator=allocator_type, traits=boost::regex_traits<char>, Allocator2=std::allocator<char>, charT=char ] z:\n2_3rd_party_components\boost\delivery\include\boost\regex\v4\regex_s earch.hpp(38) : see reference to class template instantiation 'boost::re_detail::perl_matcher<BidiIterator,Allocator,traits,Allocator2 >' being compiled with [ BidiIterator=PData::iterator, Allocator=allocator_type, traits=boost::regex_traits<char>, Allocator2=std::allocator<char> ] z:\med2\dev\ParserLib\parser.cpp(4790) : see reference to function template instantiation 'bool boost::regex_search<PData::iterator,allocator_type,char,boost::regex_tra its<charT>,std::allocator<_Ty>>(BidiIterator,BidiIterator,boost::match_r esults<BidiIterator,Allocator> &,const boost::reg_expression<charT> &,boost::regex_constants::match_flag_type)' being compiled with [ charT=char, _Ty=char, BidiIterator=PData::iterator, Allocator=allocator_type ] "z:\med2\dev\ParserLib\parser.cpp(4790)" is marked above with red. "z:\n2_3rd_party_components\boost\delivery\include\boost\regex\v4\regex_ search.hpp(38)" is listed below: template <class BidiIterator, class Allocator, class charT, class traits, class Allocator2> bool regex_search(BidiIterator first, BidiIterator last, match_results<BidiIterator, Allocator>& m, const reg_expression<charT, traits, Allocator2>& e, match_flag_type flags = match_default) { if(e.flags() & regex_constants::failbit) return false; re_detail::perl_matcher<BidiIterator, Allocator, traits, Allocator2> matcher(first, last, m, e, flags); <-- line 38 return matcher.find(); } "z:\n2_3rd_party_components\boost\delivery\include\boost\regex\v4\perl_m atcher_common.hpp(208)" is part of the following function: template <class BidiIterator, class Allocator, class traits, class Allocator2> bool perl_matcher<BidiIterator, Allocator, traits, Allocator2>::find_imp() and the line (208) is listed below: // start again: search_base = position = m_result[0].second; <-- line 208 // If last match was null and match_not_null was not set then increment // our start position, otherwise we go into an infinite loop: Searching Google for this problem did not help very much, so I was wondering if you have encounter it and put more light on it and the solution? 2. Problems on HP: 2.1. Error 24: "/VOBS/netrac2_3rd_party/boost/delivery/include/boost/regex/v4/regbase.h pp", line 53 # '<identifier>' expected instead of 'collate'. perlex = collate << 1, // perl extensions ^^^^^^^ Error 164: "/VOBS/netrac2_3rd_party/boost/delivery/include/boost/regex/v4/regbase.h pp", line 53 # Integral type expected for operator '<<'; types found were '<no type>' and 'int'. perlex = collate << 1, // perl extensions ^^^^ We do not understand why the error occurs, can you help with that? from some reason, HP's aCC doesn't like the "collate". Again, same as with problem #1, google it did not produce any useful information. We have workaround this problem as follow: changed: collate = icase << 1, // use locale specific collation perlex = collate << 1, // perl extensions to: collate = icase << 1, // use locale specific collation _collate = icase << 1, perlex = _collate << 1, // perl extensions What do you think about this solution? 2.2. Fixing above problem have exposed a problem similar to the Windows problem. Btw, both problems #1 and #2.2 were solved when set #define BOOST_NO_STD_ALLOCATOR Regards, Miko Nahum

1 0

MSVC Afx Libs incompatibility ?
by joel 10 Nov '05

10 Nov '05

I have just "demo_xml" serialisation test with "StdAfx.h" precompilated header. VC7.1 reply : nafxcwd.lib(afxmem.obj) : error LNK2005: "void * __cdecl operator new(unsigned int)" (??2@YAPAXI@Z) déjà défini(e) dans libcpmtd.lib(newop.obj) It seems that boost libs is defining new operator as nafxcwd.lib from microsoft. Does anyone succeed to use boost libs with "stdafx" libs ? Joel.

4 3

Re: [Boost-users] boost::python and Python 2.4
by Nat Goodspeed 09 Nov '05

09 Nov '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org [mailto:boost-users- > bounces(a)lists.boost.org] On Behalf Of Noel Yap > Sent: Monday, November 07, 2005 6:34 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] boost::python and Python 2.4 > > What did you have to do to get it to work with Python 2.4? Is all > that's necessary to modify all references to python2.2 to python2.4? [Nat] ? Not sure what references you mean. I just changed the environment variable we use for the Python base directory from c:\Python23 to c:\Python24, thus pointing to all new header files and libraries, and ta daa!

3 2

boost::python and Python 2.4
by Noel Yap 09 Nov '05

09 Nov '05

Is there any work being done to get boost::python to work with Python 2.4? Does anyone see any reasons it won't work (assuming the build is able to work)? Thanks, Noel

3 2

boost1.33.0 on IA64 thread problem
by Andreas Unterkircher 09 Nov '05

09 Nov '05

I'm working on porting a large project to IA64. Therefore I'd like to use the boost thread package on IA64 using gcc 3.2.3 (standard compiler on the SL 3 Linux distribution). There are some problems which I describe below and at the end of the mail I pose my questions. Thanks for any comments ! To test I use the following code: #include <stdlib.h> #include <boost/thread/mutex.hpp> int main() { boost::mutex mut; return 0; } I downloaded boost 1.33.0 & build & install it. When I try to compile it with g++ -g -O2 -pthread -I/opt/boostTest/include/boost-1_33 -L/opt/boostTest/lib -lboost_filesystem-gcc-mt -lboost_thread-gcc-mt -lpthread -lboost_regex-gcc-mt prog.c I get In file included from /opt/boostTest/include/boost-1_33/boost/thread/detail/config.hpp:18, from /opt/boostTest/include/boost-1_33/boost/thread/mutex.hpp:15, from prog.c:2: /opt/boostTest/include/boost-1_33/boost/config/requires_threads.hpp:47:5: #error "Compiler threading support is not turned on. Please set the correct command line options for threading: -pthread (Linux), -pthreads (Solaris) or -mthreads (Mingw32)" [many more "not declared" messages] Now I use "-DBOOST_HAS_THREADS", but this also does not help : g++ -g -O2 -pthread -DBOOST_HAS_THREADS -I/op/boostTest/include/boost-1_33 -L/opt/boostTest/lib -lboost_filesystem-gcc-mt -lboost_thread-gcc-mt -lpthread -lboost_regex-gcc-mt prog.c /usr/bin/ld: cannot find -lboost_thread-gcc-mt collect2: ld returned 1 exit status In the boost mailing list archive I found an IA64 patch posted by Ben Hutchings. Applying this patch and recompiling boost I get: g++ -g -O2 -pthread -I/opt/boostTest/include/boost-1_33 -L/opt/boostTest/lib -lboost_filesystem-gcc-mt -lboost_thread-gcc-mt -lpthread -lboost_regex-gcc-mt prog.c In file included from /opt/boostTest/include/boost-1_33/boost/thread/detail/config.hpp:18, from /opt/boostTest/include/boost-1_33/boost/thread/mutex.hpp:15, from prog.c:2: /opt/boostTest/include/boost-1_33/boost/config/requires_threads.hpp:47:5: #error "Compiler threading support is not turned on. Please set the correct command line options for threading: -pthread (Linux), -pthreads (Solaris) or -mthreads (Mingw32)" But when I use "-DBOOST_HAS_THREADS" everything works fine: g++ -g -O2 -pthread -DBOOST_HAS_THREADS -I/op/boostTest/include/boost-1_33 -L/opt/boostTest/lib -lboost_filesystem-gcc-mt -lboost_thread-gcc-mt -lpthread -lboost_regex-gcc-mt prog.c Here are my questions: Boost 1.33.0 contains the file boost/detail/sp_counted_base_gcc_ia64.hpp, nevertheless thread support seems not to work with gcc3.2.3. Thread support works by applying the patch and using "-DBOOST_HAS_THREADS". What is the status of boost 1.33.0 concerning IA64 ? I guess the patch has not been incorporated into the boost distribution ? On IA32 I can compile and use boost 1.33.0 threads using gcc3.2.3 without using "-DBOOST_HAS_THREADS". Why is this the case ? Ideally I would like to use the same compiler flags to compile a project using boost on IA32 and IA64. For some reasons I'd prefer to use boost 1.32.0 on IA64 but I could not get the thread package to work. Does boost 1.32.0 threads work on IA64/gcc3.2.3 ? Or is it only with boost 1.33.0 + patch that I can use them on IA64 ? Best regards, Andreas

2 3

Boost 1.33.1 Beta released
by Douglas Gregor 09 Nov '05

09 Nov '05

Boost 1.33.1 Beta ----------------- Boost 1.33.1 Beta is now available at http://www.boost.org. This is a bug fix release to 1.33.0, containing updates to existing libraries and additional computer support. Updated Libraries * Any Library: Cast to reference types introduced in 1.33.0 is now documented on any_cast documentation page. * Config Library: Don't undef BOOST_LIB_TOOLSET after use. * Boost.Python: o The build now assumes Python 2.4 by default, rather than 2.2 o Support Python that's built without Unicode support o Support for wrapping classes with overloaded address-of (&) operators * Smart Pointer Library: Fixed problems under Metrowerks CodeWarrior on PowerPC (Mac OS X) with inlining on, GNU GCC on PowerPC 64. * Regex Library: Fixed the supplied makefiles, and other small compiler specific changes. Refer to the regex history page for more information on these and other small changes. * Iostreams Library: Improved the interface for accessing a chain's components, added is_open members to the file and file descriptor devices, fixed memory-mapped files on Windows, and made minor changes to the documentation. * Functional/Hash Library: Fixed the points example. * Multi-index Containers Library: Fixed a problem with multithreaded code, and other minor changes. Refer to the library release notes for further details. * Graph Library: Fixed a problem with the relaxed heap on x86 Linux. Fixed problems with cuthill_mckee_ordering and king_ordering producing no results. * Signals Library: Fixed problems with the use of Signals across shared library boundaries. * Thread library: read_write_mutex has been removed due to problems with deadlocks. Supported Compilers 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. New for this release: Support for building with the newest STLport-5.0 was added. The support includes building with MinGW Runtime 3.8 plus STLport-5.0 improved to support wide character operations. Apple GCC 4.0, HP Tru64 C++, and Microsoft Visual C++ 8.0 are supported platforms. We have added an experimental autoconf-like configure script for Unix-like systems: run configure --help for more information. * Apple GCC 3.3, 4.0 on Mac OS X. * Borland C++ 5.6.4 on Windows. * GNU C++ 2.95.3 (with and without STLport), 3.2.x., 3.3.x, 3.4.x, 4.0.x on Windows, Linux and Solaris. * HP C++ for Tru64 UNIX 7.1. * Intel C++ 8.1, 9.0 on Windows, Linux. * Metrowerks CodeWarrior 8.3, 9.4, 9.5 on Mac OS X and 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. Acknowledgements Douglas Gregor managed this release. A great number of people contributed their time and expertise to make this release possible. Special thanks go to Aleksey Gurtovoy and Misha Bergal, who managed to keep the regression testing system working throughout the release process; David Abrahams, Beman Dawes, Aleksey Gurtovoy, Bronek Kozicki, Rene Rivera and Jonathan Turkanis for greatly improving the quality of this release; Rene Rivera for the new Boost web page design; and Zoltan "cad" Juhasz for the new Boost logo.

1 0

program_options library and mingw
by Thomas Porschberg 09 Nov '05

09 Nov '05

Hi, I try to use the program_options library in a cygwin environment by compiling my application with the -mno-cygwin -mwindows compiler flag. This flag should lead to a pure windows application. I have boost libraries version 1.33 installed(via http://cygwin.com/) I link my application against libboost_program_options-gcc-mt-s which is sufficient under Linux. However under cygwin I get an undefined reference to `_environ' linker error. I did nm /usr/lib/libc.a | grep _environ and got 00000004 B _environ 00000000 I __imp____cygwin_environ 00000000 I __nm____cygwin_environ (but my build environment[GNU Builds tools] seems to ignore the -lc flag at the linker option line) Has someone experience with this library under cygwin/mingw ? Thomas --

1 0

[BGL] adjacency_list with hash_setS: bug ?
by Johan Oudinet 09 Nov '05

09 Nov '05

Is there any example using an adjacency_list with hash_setS for EdgeList ? I think there is a mistake in adjacency_list.hpp:21: // ====================== #if !defined BOOST_NO_HASH #include <hash_set> // instead of <ext/hash_set> ? #endif // ====================== I'm using gcc 4.0.2 with boost 1.33.0 and I can't compile a simple example using adjacency_list with hash_setS: // ====================== # if defined __cplusplus # if defined __GNUC__ && __GNUC__ >= 3 # include <ext/hash_set> # include <ext/hash_map> # if __GNUC__ >= 4 || __GNUC_MINOR__ >= 2 namespace std { using ::__gnu_cxx::hash; using ::__gnu_cxx::hash_set; using ::__gnu_cxx::hash_map; } # endif # else # include <hash_set> # include <hash_map> # endif /* defined __GNUC__ and __GNUC__ == 3 */ # endif /* defined __cplusplus */ #define BOOST_HAS_HASH 1 // for boost::hash_setS #include <boost/config.hpp> #include <boost/graph/adjacency_list.hpp> using namespace boost; int main() { typedef adjacency_list<hash_setS, vecS, bidirectionalS> Graph; Graph g; } // ========================== -- Johan

2 2

Re: [Boost-users] boost::python and Python 2.4
by Nat Goodspeed 09 Nov '05

09 Nov '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org [mailto:boost-users- > bounces(a)lists.boost.org] On Behalf Of Noel Yap > Sent: Tuesday, November 08, 2005 9:14 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] boost::python and Python 2.4 > > I see the problem. Since the location of pyconfig.h depends upon > which compiler was used, it's not located in the same directory as the > rest of the Python header files. [Nat] ? Sorry, I don't understand you at all. On my Windows system I installed Python 2.3 into the default directory, c:\Python23. Likewise Python 2.4 is installed in c:\Python24. The only pyconfig.h files on my system are in 'include' subdirectories of those two directories. They don't seem to be in compiler-dependent locations, and those 'include' subdirs ARE where 300+ other Python header files live. It's worth noting that we build the Boost libraries we use as MSVC 7.1 projects. Those projects (and others) look for a PYTHONDIR environment variable whose value used to be c:\Python23 and is now c:\Python24. > I've tried passing a ':'-separated path as PYTHON_INCLUDES, but that > doesn't work. Anyone have any thoughts on this? I suppose I /could/ > hack around this by using symlinks, but I'd rather find a less hacky > solution. [Nat] So, maybe the reason I don't understand the problem you're having is because you're on a different system with a different compiler.

2 2

[BGL] a.k.a. [Graph] -- bundled properties not compiling for me under MS Dev
by Goldman, Jon 08 Nov '05

08 Nov '05

Hello, I am using Microsoft Development Environment 2002. I am trying to compile a Graph and use bundled properties. The error I am getting: \src\vtkSNL\Applications\RouteViz\rtrGraph.cxx(37) : error C2676: binary '[' : 'SimpleGraph' does not define this operator or a conversion to a type acceptable to the predefined operator \src\vtkSNL\Applications\RouteViz\rtrGraph.cxx(37) : error C2228: left of '.i' must have class/struct/union type The code snippet below exhibits the problem: struct nodeProp { int i; }; struct edgeProp { int i; }; typedef adjacency_list<boost::listS, boost::vecS, boost::bidirectionalS, nodeProp, edgeProp> SimpleGraph; void someFunc() { SimpleGraph someGraph(3); Graph::vertex_descriptor v = *vertices(someGraph).first; someGraph[v].i = 7; // This line is where the error is occuring } Anybody familiar with this problem? Thanks for looking this over, -Jon

2 1

What is the way to sort graph vertices?
by Slava 08 Nov '05

08 Nov '05

Hi, I need to find Maxumum Common Subgraph (between two graphs). For that task i need to get all the vertices of the 2 graphs sorted with some property (like vertex label or id). regular std::sort seems not working with vertex iterators (vertices(graph)). What is the way to accomplish this? Thanks

2 1

Re: [Boost-users] [Boost][serialization] Serialization and DLLs
by Topi Mäenpää 08 Nov '05

08 Nov '05

>>> Could this be related to the fact that the low-level type_info pointer >>> for the classes is different in the dll and the exe? > > That sounds like it could explain this. > > >>> (This is also the >>> reason why dynamic_cast doesn't work across dynamic library >>> boundaries.) > > I've never heard of this before. If this is true it would be key indicator > that > something's wrong. Is this a known MSVC bug? That would be very > interesting to know. I'm not a pro on this matter, but at least gcc (and its Windows version, mingw) have similar "feature". I still need to double-check if I have forgotten to include rtti support somewhere, but I have seen a couple of different my::dynamic_cast implementations that try to work around this. The most well known one might be Qt:s qobject_cast. As far as I know, compilers use pointer equivalence to compare type_infos. It seems that the type_info pointer isn't exported from dynamically loaded modules, which makes dynamic type casting (and also certain exceptions) impossible across dll boundaries. I don't know the reason, but I have verified this with three different compilers, on Linux and Windows. > Is it possible to use the non-rtti versions with MSVC > >>> 7.1? > > > I have implemented non-rtti version which is documented and tested - > test_non_rtti. > The test verifies that types which are identified with different runtime > typing systems > can inter-operate. The library includes extended_type_info_no_rtti.cpp (a > mis-nomer > I see now). This runtime typing system uses the BOOST_CLASS_EXPORT key > as the type identifier. So to use this you'll have to fix the > "type_info_implementation" > trait for this type and besure its exported. This hasn't really been used > except in the > testing (as far as I know). As far as using it a derived class defined in a > DLL where > the base class is in some other library? Too bad I found the reason this late. You already had the feature there! > I reviewed the relevant code and have verified that the serialization system > presumes > that type_info returns the same value regardless of whether the type is > implemented > within a an executable, standard library or dll. I can't imagine why it > would be any > other way. I also don't have any other reports of this. Of course, this is > not > a common usage so that probably doesn't mean much. Double check that that > there aren't any differences in things like _cdecl etc. Maybe that might > explain > why the run-time type signatures vary depending up where the type is > implemented. > > I've started written my own test of this situation but its kind of hung up > in some > in trying to get it worked into bjam. So I haven't finished it. > > I'll do what I can. Thanks for a thorough inspection of the matter. I finally managed to work out a temporary hack that does the thing. Here is how: Change tkmap/ktmap multisets to sets. Modify extended_type_info so that it always compares keys literally. Re-export base classes from wherever subclasses are exported. This ensures that the correct key is recorded to extended_type_info even though there are multiple distinct instances. The downside is that one now always needs a key, but I'm assuming it is the only possible way of dealing with shared libs anyway. Phew! I like the design of the library and the ease of use a lot. Good luck this is (at least partially) resolved now, because it would have been a show stopper to me. I hope my findings have some use in developing an even better version of it :) Best regards, Topi (not so frustrated any more, I'm gonna meet the deadline ;)

1 0

Pyste question--how to exclude a constructor?
by Drumheller, Michael 08 Nov '05

08 Nov '05

I would like to be able to exclude a constructor. My situation is precisely analogous to this: http://mail.python.org/pipermail/c++-sig/2004-March/006952.html But the above thread did not seem to terminate with a solution. Does anyone know how to do this? Thanks, MD

1 0

Re: [Boost-users] [Boost][serialization] Serialization and DLLs
by Topi Mäenpää 08 Nov '05

08 Nov '05

> I have a suggestion, please comment. The problem _could_ be in that >> guid_initializer isn't exported. If I register my base class in a >> DLL, the DLL interface does not expose the >> guid_initializer::instance I have created. Since my exe now doesn't >> know about it, it creates a new definition. The same applies to >> other DLLs. (This would also explain why the same code works on >> Linux: all symbols are automatically exported.) What if we exposed >> the guid_initializer struct to the DLL interface? Would it help? At >> least it shouldn't do any harm to export it from the exe. > That might explain the behavior. We'll look into it. I'm having > problems making test which uses a dynamically loaded DLL that I can > run under bjam. No, it didn't work... I also exported the extended_type_info subclasses (_0 and _1) from my DLL, but I still encounter the same problems. The code lacks comments, and I find it difficult to study some some of the constructs. It seems that whenever I register a class, its superclasses get registered as well. The extended_type_info pointer for my common superclase is however different for each instantiation. The exe crashes due to an unhandled unregistered_cast exception thrown at oserializer.hpp:408. Thus, it seems that downcasting cannot succeed. I even modified the extended_type_info so that it always compares keys literally instead of pointers, but this has no effect. Furthermore, I changed the tkmap and ktmap multisets to sets. I assumed this could prevent multiple registrations, but it does not. Could someone point me out a way to work around this? Any temporary solution will do until the problem has been identified and fixed. Best regards, Topi

2 3

Re: [Boost-users] linker problem with regex library - resolved
by Oliver.Kowalke＠infineon.com 08 Nov '05

08 Nov '05

Hello, I could get the boost libraries linked against my application if I compile the boost libraries with -fpic (bjam "-sBUILD=release debug <cxxflags>-fpic" "-sTOOLS=gcc" install). I think you should use -fpic as default parameter in the boost build for gcc on (at least) HP/UX PA RISC 11.11. The -fPIC choice always works, but may produce larger code than -fpic. Using -fpic option usually generates smaller and faster code, but will have platform-dependent limitations, such as the number of globally visible symbols or the size of the code. The linker will tell you whether it fits when you create the shared library. When in doubt, I choose -fPIC, because it always works. @John: would this be possible? With regards, Oliver >> I get the linker error (see below) if I try to compile my test app. >> What is the problem? >> >> /usr/ccs/bin/ld: Invalid loader fixup in text space needed in output >> file for symbol "__gxx_personality_sj0" in input file >> "/opt/boost/lib/libboost_regex-gcc. > >No idea, I did a quick google for this error message and it seems to be a >common error when people are building shared libraries, but with one of the >components not built with -fPIC. So for example if you tried to link a >static regex build into a shared lib. Does this sound familiar? > >John. > >_______________________________________________ >Boost-users mailing list >Boost-users(a)lists.boost.org >http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Re: [Boost-users] boost::python and Python 2.4
by Nat Goodspeed 07 Nov '05

07 Nov '05

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org [mailto:boost-users- > bounces(a)lists.boost.org] On Behalf Of Noel Yap > Sent: Monday, November 07, 2005 3:47 PM > To: boost-users(a)lists.boost.org > Subject: [Boost-users] boost::python and Python 2.4 > > Is there any work being done to get boost::python to work with Python > 2.4? Does anyone see any reasons it won't work (assuming the build is > able to work)? [Nat] I hope nobody sees any reasons it wouldn't work: we're using Python 2.4 now. But we're also using Boost 1.31. I tried to convert to 1.32 a couple months ago and ran into failures I didn't understand with other parts of Boost. I haven't yet charged with lowered spear at 1.33.

2 1

[Wave] extracting preprocessing grammar and comments from sourcefile
by Andreas Sæbjørnsen 07 Nov '05

07 Nov '05

After looking at the documentation of Wave I believe it can be used to extract the preprocessor grammar and I am therefore looking for some tips on how to get started on my problem. I want to adapt wave into a mechanism for exptracting all preprocessor grammar from a source file without modifying the library itself, and I will try to explain what I want to use wave for. What I want to do is to *extracting the position and value of preprocessor tokens like #ifdef's, #defines, #warning etc. *evaluate the preprocessor conditionals *after evaluating the preprocessor conditional, extract the portion which was evaluated as false as a string #define positive #ifdef int positive #endif /*Extract this false part as string*/ int x; #endif *I am also interested in the value and position of unexpanded macros *extracting the C/C++ statement or expression that the unexpanded macro (and expanded) is a part of. *extract the value and position of all C and C++ comments Which work should I bace my work upon and which data structures should I reimplement and for what? I have looked at the documentation and the code, and it seems easy to do some parts but other are not obvious to me at this point. Thanks, Andreas Saebjoernsen

2 9

LNK2019: unresolved external symbol
by Hiba Tabbara 07 Nov '05

07 Nov '05

1 0

Compile problem with shared_ptr on unusual platform
by Allen Gooch 07 Nov '05

07 Nov '05

I'm trying to use shared_ptr<> from boost 1.33.0 on the Metrowerks CodeWarrior for PSP 1.2 (that's Playstation Portable) and am running into a problem, which I believe may be related to the boost config system and it not being prepared for my admittedly unusual toolchain. I have successfully used this on many other platforms in the past, and have thoroughly enjoyed the boost in productivity and safety through its use. Here's my problem, a simple "hello world" app using boost::shared_ptr< std::string > using the top-level <boost/shared_ptr.hpp> include yields the following link error: Link Error : Undefined : "boost::throw_exception(const std::exception&)" Referenced from "boost::detail::shared_count::!<std::basic_string<char, std::char_traits<char>, std::allocator<char>>>(std::basic_string<char, std::char_traits<char>, std::allocator<char>>*)" in main.cpp Link failed. Any insight into this problem, or the configuration system and how I might adapt it to this compiler, are greatly appreciated. -allen

4 3

Missing Files in Boost 1.33.0 Download
by Merrill Cornish 07 Nov '05

07 Nov '05

Bug? As nearly as I can tell, boost_1_33_0/doc/html/thread created by running the boost_1_33_0.exe download is supposed to contain the same files as http://www.boost.org/doc/html/thread.html, which you get to from libraries | documentation on the home page. However, in my download (and for 1.32.0 also) there are only the acknowledgements, build, and configuration HTML files. Could someone check to see if the other files are being dropped in the download packaging step? Merrill

1 0

Problem with dll and BOOST_STATIC_ASSERT
by Frank 07 Nov '05

07 Nov '05

I have the following code ( very simplified but compilable) // =========== start snip =============================== /// ======= in hpp ============ #include <boost/static_assert.hpp> template <typename T, unsigned short DIM=3> class Vector { public: Vector(void) {/*init code omitted*/} Vector(const Vector& v) {/* ctor code omitted */} //===================================================== // some ctors for small DIM's // will cause compile time errors if DIM != # of args //===================================================== #ifdef enable_small_dim_ctor explicit Vector( T x ) { BOOST_STATIC_ASSERT(DIM==1); data_[0]=x; } Vector( T x, T y ) { BOOST_STATIC_ASSERT(DIM==2); data_[0]=x; data_[1]=y; } Vector( T x, T y, T z ) { BOOST_STATIC_ASSERT(DIM==3); data_[0]=x; data_[1]=y; data_[2]=z; } #endif private: T data_[DIM]; }; template <typename T> class Vector3 : public Vector<T,3> { public: Vector3(){}; Vector3 Normal() const; }; //==================== in cpp ================= // provide implementation of Normal template <typename T> Vector3<T> Vector3<T>::Normal() const { Vector3 n; return n; } // explicit instantiation of the normal method #ifdef try_export // causes error STATIC_ASSERTION_FAILURE template class __declspec(dllexport) Vector3<double> Vector3<double>::Normal() const; #else //OK template class Vector3<double> Vector3<double>::Normal() const; #endif // ============== end snip =============================== I 'm trying to put the implementation into a dll and mark the explicit instantiation of Normal as exported with the following results: 1) With the small_dim_ctor's enabled I get the static assertion when marked for export 2) With the small_dim_ctor's enabled everything is ok when not marked for export 3) With the small_dim_ctor's disabled everything is ok regardless of export marking 4) If I comment out the BOOST_STATIC_ASSERT and build my app with export enabled I can use the resulting dll without any problems I'm thinking that marking for export is somewhow generating an implicit conversion somewhere but I don't know how. Using VStudio .Net 2003. Any help is appreciated. Thanks Frank

3 8

[iostreams] problem with gzip_compressor
by Tiago de Paula Peixoto 07 Nov '05

07 Nov '05

Hello. I've been experiencing the following problem with the gzip_compressor filter: It always writes data down the stream, regardless if any data has been written to the filtering_stream. Consider the following program: -------------------------------------------------------- #include <iostream> #include <fstream> #include <boost/iostreams/filtering_stream.hpp> #include <boost/iostreams/filter/gzip.hpp> using namespace std; using namespace boost; int main() { ofstream file; file.open("hello.gz", ios_base::out | ios_base::app | ios_base::binary); iostreams::filtering_stream<boost::iostreams::output> stream; stream.push(iostreams::gzip_compressor()); stream.push(file); return 0; } -------------------------------------------------------- If compiled as "test", the following behavior is observed: $ ./test; ls -l hello.gz -rw-r--r-- 1 count0 users 8 2005-10-30 19:51 hello.gz $ ./test; ls -l hello.gz -rw-r--r-- 1 count0 users 16 2005-10-30 19:51 hello.gz $ ./test; ls -l hello.gz -rw-r--r-- 1 count0 users 24 2005-10-30 19:51 hello.gz That is, it always adds 8 bytes to the file, despite the fact that nothing was written to the stream. To top things off, the data inside the file isn't even recognizable by gzip: $ gunzip hello.gz gunzip: hello.gz: not in gzip format When bzip2_compressor is used, this strange behavior doesn't happen, and the file remains with 0 bytes. I guess this is a bug, right? I'm using boost 1.33.0 with GCC 4.0.1 in a GNU/Linux system. Thanks for any help. -- Tiago de Paula Peixoto <tiago(a)forked.de>

2 6

linker problem with regex library
by Oliver.Kowalke＠infineon.com 07 Nov '05

07 Nov '05

Hello, I get the linker error (see below) if I try to compile my test app. What is the problem? /usr/ccs/bin/ld: Invalid loader fixup in text space needed in output file for symbol "__gxx_personality_sj0" in input file "/opt/boost/lib/libboost_regex-gcc. Best regards, Oliver

2 1

Re: [Boost-users] linker problem with regex library
by Oliver.Kowalke＠infineon.com 07 Nov '05

07 Nov '05

Sorry - I forget: os. HP/UX 11.11, gcc 3.4.2 >Hello, >I get the linker error (see below) if I try to compile my test app. >What is the problem? > >/usr/ccs/bin/ld: Invalid loader fixup in text space needed in output >file for symbol "__gxx_personality_sj0" in input file >"/opt/boost/lib/libboost_regex-gcc. > >Best regards, >Oliver > >_______________________________________________ >Boost-users mailing list >Boost-users(a)lists.boost.org >http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Can't Compile store() in Program Options
by Merrill Cornish 07 Nov '05

07 Nov '05

I am trying to use the Boost 1.32.0 program_options library for the first time with MGWin. Since what I need is identical to what is in the Getting Started section of the program_options Tutorial, I copied that. Here is the code from the tutorial: po::options_description desc("Allowed options"); desc.add_options() ("help", "produce help message") ("compression", po::value<int>(), "set compression level") ; po::variables_map vm; po::store(po::parse_command_line(ac, av, desc), vm); po::notify(vm); The problem occurs in the store() function. The compiler says it doesn't have a store() to match that call and suggests two possibilities. Examining the .hpp files, it appears that the two argument version of store() defaults to using wchar_t, which doesn't seem right. So, I tried po::store(po::parse_command_line(ac, av, desc), vm, true); to get UTF8 (simple char). The next complaint is apparently about the parse_command_line() call as the first argument. If I pull parse_command_line() out into a separate assignment statement to an intermediate variable, then put its results into store(), that could/would work except there now seems to be a conflict between the template types of char versus const char. I can get the assignment of parse_command_line() to an intermediate result to compile, but store() fails because of mismatched type problems. Or, I can get store() to compile, but the assignment fails for mismatched type problems. I apologize for not having the specific error messages here since the machine I'm compiling on is not available right now. Merrill P.S. About the Documentation: The program_options library document looks slick and very professional. Furthermore, it obviously took some time to create with all of the examples. However, I've never seen programming library documentation that didn't actually list the methods and functions in the library. As it is, if you are lucky, the method you need to mentioned, in passing, in an example. However, looking in the hpp and cpp files shows there is a lot more there.

2 1

Problem with program_options store()
by Merrill Cornish 07 Nov '05

07 Nov '05

Given this program fragment (based on the Getting Started example) using Boost::program_options compiled with MinGW: options_description desc("Program options"); ... variables_map vm; store(parse_command_line(argc, argv, desc), vm); gave the following error (reformatted for readability): error: no matching function for call to `store(boost::program_options::basic_parsed_options<const char>, boost::program_options::variables_map&)' candidates are: store(const boost::program_options::basic_parsed_options<char>&, boost::program_options::variables_map&, bool) store(const boost::program_options::basic_parsed_options<wchar_t>&, boost::program_options::variables_map&) I can add a "true" as a third argument to store(), but the mismatch still remains in the first argument: <const char> versus <char>&. If I assigned the result of parse_command_line() to an intermediate variable, I can match the &, but the const char versus char still remains. What is the problem way of calling store()? Merrill

2 1

Profiling Boost with gprof
by Dave 07 Nov '05

07 Nov '05

Hello All, I'm trying to profile Boost Graph examples using gprof, but can't get any reasonable results. My system is Mac OS X 10.3.9 and gcc version 3.3. I compile programs with -pg option, but the profile does not seem to contain any useful information. It only shows "no time accumulated", or 100% for main. What am I doing wrong? Thanks for your help! Dave __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

3 2

library planed for expression evaluation?
by Oliver.Kowalke＠infineon.com 07 Nov '05

07 Nov '05

Hello, does some plans for an library for expression evaluation exist? The user should be able to define its own operators (unary and binary with priority/affinity) and operands. The user can then store a sequence of its operators and operands in a vector in infix order. A special function creates from the vector an expression tree and evaluates the tree (calling the implemented action of each operator/operand -> the action can depend of the subsequent/child operators). With regards, Oliver

1 0

Threads - suggestion for producer/consumer pattern - msg_queue (was ThreadPool)
by Oliver.Kowalke＠infineon.com 07 Nov '05

07 Nov '05

Hello, the email with the 'ThreadPool' subject requested an implemention of the synchronization channel between producer and consumer threads. I've a suggestion (adopted from several books) - the only problem is how to tell the consumer threads, that all producer have finished their jobs. You can signal it from outside (deactive member function) or each producer thread has to register on the message_queue (and unregister if it has finished its job). With best regards, Oliver <<test.cpp>> <<message_queue.h>>

1 0

When will boost::socket library issue?
by huangruiguang＠kingnet.biz 07 Nov '05

07 Nov '05

1 0

Translating an absolute path to a path relative to the current directory
by Hermann Rodrigues 06 Nov '05

06 Nov '05

Hi, I am running into the following problem these days: I need to translate an absolute path to a path relative to the current directory on Windows. The translation process need to include all required ".." directory specifiers in the path to make sure it can be accessed from the current directory. The following path samples may clarify the problem. -------------------------------------------------------------------------------- Current Directory: C:\x\y\z Absolute Path: C:\x\y\z\k\w.txt Translated Path: k\w.txt (C:\x\y\z is a common parent) Current Directory: C:\x\y\z Absolute Path: D:\a\b\c\d.txt Translated Path: D:\a\b\c\d.txt (no common parent found) Current Directory: C:\x\y\z Absolute Path: C:\x\k\w.txt Translated Path: ..\..\k\w.txt (C:\x is a common parent) -------------------------------------------------------------------------------- Is there any built-in support in the boost filesystem library to achieve such translation? At first I thought the path::relative_path could solve my problem but it does not seem to take into account the current directory, only the path itself. Any sugestion? Thanks in advance. Hermann

2 2

Re: [Boost-users] [date-time] posix timezone string
by Stering Wolfram 04 Nov '05

04 Nov '05

[I am receiving this list in digested form, so this reply might not be correctly "linked" to its parent, I am afraid.] On Thu, 03 Nov 2005 13:25:07 +0100, Stering Wolfram wrote >> I am implementing a year_based_date-derived date generator to >> calculate the easter sunday for a given year. Now, this is the easy >> part, and it is done already. > Great! >> But I wonder how to generate a meaningful posix timezone string that >> is expected to result from calling the generator's to_string() member. >> >> The documentation at the (not well formatted, b.t.w.) "Description" >> section of class posix_time_zone didn't give any hints for Easter >> Sunday either. >> >> Any ideas? > I'm afraid I need a bit more context -- are you trying to generate a > local_time? In general I wouldn't think you would care about local_time for > Easter? Perhaps a bit of code to show what you want to do? No local_time, just a boost::gregorian::date should be generated, like partial_date for example. So, here we go: What I want to achieve is something like the following: - ----------------------------------------------- // Use the Gauß Formula easter_sunday<date, GregorianEasterSundayGauss> es_gauss; // Use Oudin's Formula easter_sunday<date, GregorianEasterSundayOudin> es_oudin; partial_date pd( 16, Apr ); date d1 = es_gauss.get_date( 2006 ); // 2006-Apr-16 date d2 = es_oudin.get_date( 2006 ); // 2006-Apr-16 date d3 = pd.get_date( 2006 ); // 2006-Apr-16 assert( d1 == d2 ); assert( d1 == d3 ); // But, of course: date d4 = es_gauss.get_date( 2007 ); // 2007-Apr-08 date d5 = pd.get_date( 2007 ); // 2007-Apr-16 assert( d4 != d5 ); - ----------------------------------------------- with easter_sunday<> being defined as follows, modeled after other year based generators (from date_generators.hpp) with the policy defining the algorithm used to actually calculate the easter sunday date for a given year, which differs for the gregorian calendar (catholic, protestants) and the julian calendar (orthodox). The policy could be expected to provide an operator()( year ) which returns an easter_sunday::date_type, for example. - ----------------------------------------------- template <typename date_type, typename policy> easter_sunday : public year_based_generator<date_type> { public: typedef date_type::calendar_type calendar_type; typedef date_type::year_type year_type; easter_sunday() {} // does not require any arguments. virtual ~easter_sunday() {} virtual date_type get_date( year_type y ) const { return _generator_alg( y ); } virtual std::string to_string() const { return "easter_sunday"; /* or what? */ } private: policy _generator_alg; }; - ----------------------------------------------- One remaining glitch is the typedef, as exists for the other generators to pull in the name into the gregorian namespace (gregorian_types.hpp), which is not possible for the policy-based easter_sunday, as a partial template specialization typedef would be required... It would be nice to just say easter_sunday<GregorianEasterSundayGauss> for example, being able to leave out the boost::gregorian::date. A possible modification could be to change the (compile time) policy-based implementation to use a function pointer in the constructor to set the algorithm to be used (kind of Strategy pattern) at run time. Ah, yes, my original question actually was the to_string() which, according to the documentation of year_based_generator, is expected to return a string for use in a POSIX time_zone string. regards, -wolfi -- DI Wolfram Stering (Entwicklung) HALE electronic GmbH., Salzburg, Austria Tel: +43 (662) 439011 550 Fax: +43 (662) 439011 9 Email: wolfram.stering(a)hale.at

2 1

Re: [Boost-users] Threads (Not Mutex) Docs?
by Phil Endecott 04 Nov '05

04 Nov '05

> 1. Start at http://www.boost.org/doc/html > 2. Click on 12. Boost.Threads > 3. Click on Header <boost/thread/thread.hpp> in the contents > 4. Click on the "class thread;" link > > This seems pretty intuitive and perfectly acceptable to me. I replied to Merrill's question because I recognised the difficulty of finding this documentation as something that I had encountered, and continue to encounter from time to time. I suspect that those of you who have been using it for longer have got used to the way that it is organised and do consider it intuitive, but that it not how it has seemed to at least a couple of us "outsiders". Once located the Boost documentation is always good and very often excellent. This makes it a particular shame if it remains hidden. The particular problems that I've encountered are: - The "documentation" link on the front page at boost.org is in a smaller font even than the body text, and is not obviously a link. - The "automatic redirection failed" messages that appear all over the place are disconcerting. - The links to the actual class documentation, e.g. the "class thread;" link in (4) above, are not obviously links. - Links within the documentation often seem to be missing. For example, on the "Chapter 12 Boost.Threads" page, after the "Introduction" heading it looks as if a link is missing before the word "allows". Similarly after the heading "Runtime libraries" something seems to be missing between "using" and "must". Cheers, --Phil.

1 0

Re: [Boost-users] Threads (Not Mutex) Docs?
by Merrill Cornish 04 Nov '05

04 Nov '05

Matt, >>> 1. Start at http://www.boost.org/doc/html >>> 2. Click on 12. Boost.Threads >>> 3. Click on Header <boost/thread/thread.hpp> in the contents >>> 4. Click on the "class thread;" link >>> >>> This seems pretty intuitive and perfectly acceptable to me. I just went back to www.boost.org to double check. I couldn't find any link from the home page to any www.boost.org/doc/* page. This is the case where the first step is the biggest. Now that I know it's there, I can find links to it from a couple of levels down under the documentation link that initially takes you to the lib directory. Also, I had done much of my looking in the various doc directories of the Boost 1.33.0 download tree. Under the top-level doc/html directory there is a threads directory [note the plural] which should be named mutexes, since that's all it covers. There is also a thread directory [note the singular] which, I assume, is supposed to be a copy of what the people who responded to my question referred to on the web site. However, it has only the acknowledgements.html, build.html, and configuration.html files. Merrill

2 1

Re: [Boost-users] Threads (Not Mutex) Docs?
by Merrill Cornish 04 Nov '05

04 Nov '05

Someone needs to go into http://www.boost.org/doc/html and add a link to thread.html. The only thread-related link there now is to threads.html, the mutex treatise. There is no hint there about the other links I've now been given. Thanks, Merrill

2 1

Re: [Boost-users] Threads (Not Mutex) Docs?
by spam_from_boost_users＠chezphil.org 04 Nov '05

04 Nov '05

> Where is the documentation of Boost Threads--not mutexes, threads? http://www.boost.org/doc/html/thread.html

2 1

Re: [Boost-users] boost::condition questions
by Adam M 04 Nov '05

04 Nov '05

Ok, I see now in scoped_lock the following: operator const void*() const { return m_locked ? this : 0; } So, in wait() where they check "if( !lock) {...}", they're actually checking to see if the lock has locked the mutex. However, for the reasons I mentioned in my earlier post, this still seems perilous. Can someone explain? Thanks, Adam

1 0

boost::condition questions
by Adam M 04 Nov '05

04 Nov '05

Hi, I have a couple questions regarding boost::condition. You can view the condition.hpp here: http://www.boost.org/boost/thread/condition.hpp 1) wait() starts out as follows: -------------------------------- void wait(L& lock) { if (!lock) throw lock_error(); ... -------------------------------- This "if (!lock)" seems to be checking if the lock is NULL, not if the mutex is actually locked. In the documentation, it says: "Throws: lock_error if !lock.locked()" However, even this seems to be a bit dubious, because that checks to see if the given lock is the one that locked the mutex, and *not* if the mutex itself is locked. Remember that the scoped_lock constructor can take a second parameter to indicate whether or not to actually lock the mutex. One might use this as an alternative to recursive locking, so that a synchronized function may call another synchronized function and indicate with a flag that the scoped_lock "initially_locked" parameter should be 'false'. If that function then called to wait(), lock.locked() would return 'false', when the mutex is in fact actually locked. Am I wrong? 2) In the boost::condition documentation: http://boost.org/doc/html/condition.html #4 on "condition waiting" is wrong; they left out the boost::xtime parameter. Thanks, Adam

1 0

Re: [Boost-users] [Boost][serialization] Serialization and DLLs
by Topi Mäenpää 04 Nov '05

04 Nov '05

> So the problem is already ratched up to another level of complexity. > > class X can be in a DLL. > class Y can be in an application > > everything is fine so far > > class Z :: public class Y creates a problem in that class Y gets > registered in the application even if its already in the DLL. This will > require some thought to know what the correct way to handle this is. I have a suggestion, please comment. The problem _could_ be in that guid_initializer isn't exported. If I register my base class in a DLL, the DLL interface does not expose the guid_initializer::instance I have created. Since my exe now doesn't know about it, it creates a new definition. The same applies to other DLLs. (This would also explain why the same code works on Linux: all symbols are automatically exported.) What if we exposed the guid_initializer struct to the DLL interface? Would it help? At least it shouldn't do any harm to export it from the exe. -Topi-

2 1

Threads (Not Mutex) Docs?
by Merrill Cornish 04 Nov '05

04 Nov '05

Where is the documentation of Boost Threads--not mutexes, threads? All of the documentation files I can find that say "threads" in the file name are really about mutexes. A lot of different mutexes. Theories and rationales about mutexes. Many, many variations on mutexes, most with a small notation that this variation isn't supported yet. OK, I understand about how to use mutexes to protect access by multiple threads to common variables, but I can't find any documentation--other than reading the source--on how to create, manipulate, and terminate any threads to use mutexes on. While I'm not particularly opposed to reading the source, there are enough subtleties in using threads (see the Boost treatise on mutexes) that I hesitate to go with Boost threads and will probably have to use pthreads-win32. Merrill

1 0

shared_ptr problems
by Filipe Sousa 04 Nov '05

04 Nov '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! I'm trying to create a wrapper around mysql but I have a problem with shared_ptr. Look at the following code: #include <boost/shared_ptr.hpp> #include <iostream> #include <map> struct MYSQL {}; MYSQL* mysql_init() { std::clog << __PRETTY_FUNCTION__ << std::endl; return new MYSQL; } void mysql_close(MYSQL* m) { std::clog << __PRETTY_FUNCTION__ << std::endl; delete m; } class Connection { boost::shared_ptr<MYSQL> m_mysql; public: void connect() { m_mysql.reset(mysql_init(), mysql_close); } bool isConnected() const { return m_mysql.get() != 0; } }; class ConnectionManager { std::map<std::string, Connection> m_connections; public: static ConnectionManager* instance() { static ConnectionManager cm; return &cm; } Connection connection(const std::string& name = "default") { return m_connections[name]; } }; int main() { { Connection c = ConnectionManager::instance()->connection(); std::clog << "isConnected " << c.isConnected() << std::endl; c.connect(); std::clog << "isConnected " << c.isConnected() << std::endl; } Connection c = ConnectionManager::instance()->connection(); std::clog << "isConnected " << c.isConnected() << std::endl; return 0; } And the output is: isConnected 0 MYSQL* mysql_init() isConnected 1 void mysql_close(MYSQL*) isConnected 0 What I don't understand is why shared_ptr calls mysql_close too soon. After all still exists a reference to Connection. I mean, mysql_close should by called when the ConnectionManager singleton is destroyed or am I doing something wrong. - -- Filipe Sousa -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDalOEbQdNYqwwwCwRAsNLAJ43BSZTCuraPQ2ouFqGoW/2+JDPDgCeOoQ7 8ZoF4LDO7vQyrPM/Whtx/O8= =iil3 -----END PGP SIGNATURE-----

4 4

a newbie question
by Tuan A. Tran 04 Nov '05

04 Nov '05

Hi, I am a newbie. I would like to run a simple threaded program using boost. I got a sample file see below and compile with the following command g++ simple.cpp -lthread I got error //// In file included from /usr/include/boost/thread/detail/config.hpp:18, from /usr/include/boost/thread/thread.hpp:15, from /usr/include/boost/thread.hpp:15, from simple.cpp:9: /usr/include/boost/config/requires_threads.hpp:47:5: #error "Compiler threading support is not turned on. Please set the correct command line options for threading: -pthread (Linux), -pthreads (Solaris) or -mthreads (Mingw32)" In file included from /usr/include/boost/thread/thread.hpp:19, from /usr/include/boost/thread.hpp:15, from simple.cpp:9: /usr/include/boost/thread/mutex.hpp:58: error: `cv_state' was not declared in this scope /usr/include/boost/thread/mutex.hpp:58: error: `state' was not declared in this scope /usr/include/boost/thread/mutex.hpp:58: error: invalid data member initialization /usr/include/boost/thread/mutex.hpp:58: error: (use `=' to initialize static data members) /usr/include/boost/thread/mutex.hpp:58: error: variable or field `do_lock' declared void /usr/include/boost/thread/mutex.hpp:58: error: declaration of `int boost::mutex::do_lock' /usr/include/boost/thread/mutex.hpp:56: error: conflicts with previous declaration `void boost::mutex::do_lock()' /usr/include/boost/thread/mutex.hpp:59: error: `cv_state' was not declared in this scope /usr/include/boost/thread/mutex.hpp:59: error: `state' was not declared in this scope /usr/include/boost/thread/mutex.hpp:59: error: invalid data member initialization /usr/include/boost/thread/mutex.hpp:59: error: variable or field `do_unlock' declared void /usr/include/boost/thread/mutex.hpp:59: error: declaration of `int boost::mutex::do_unlock' /usr/include/boost/thread/mutex.hpp:57: error: conflicts with previous declaration `void boost::mutex::do_unlock()' /usr/include/boost/thread/mutex.hpp:100: error: `cv_state' was not declared in this scope /usr/include/boost/thread/mutex.hpp:100: error: `state' was not declared in this scope /usr/include/boost/thread/mutex.hpp:100: error: invalid data member initialization /usr/include/boost/thread/mutex.hpp:100: error: variable or field `do_lock' declared void /usr/include/boost/thread/mutex.hpp:100: error: declaration of `int boost::try_mutex::do_lock' /usr/include/boost/thread/mutex.hpp:97: error: conflicts with previous declaration `void boost::try_mutex::do_lock()' /usr/include/boost/thread/mutex.hpp:101: error: `cv_state' was not declared in this scope /usr/include/boost/thread/mutex.hpp:101: error: `state' was not declared in this scope /usr/include/boost/thread/mutex.hpp:101: error: invalid data member initialization /usr/include/boost/thread/mutex.hpp:101: error: variable or field `do_unlock' declared void /usr/include/boost/thread/mutex.hpp:101: error: declaration of `int boost::try_mutex::do_unlock' /usr/include/boost/thread/mutex.hpp:99: error: conflicts with previous declaration `void boost::try_mutex::do_unlock()' /usr/include/boost/thread/mutex.hpp:144: error: `cv_state' was not declared in this scope /usr/include/boost/thread/mutex.hpp:144: error: `state' was not declared in this scope /usr/include/boost/thread/mutex.hpp:144: error: invalid data member initialization /usr/include/boost/thread/mutex.hpp:144: error: variable or field `do_lock' declared void /usr/include/boost/thread/mutex.hpp:144: error: declaration of `int boost::timed_mutex::do_lock' /usr/include/boost/thread/mutex.hpp:140: error: conflicts with previous declaration `void boost::timed_mutex::do_lock()' /usr/include/boost/thread/mutex.hpp:145: error: `cv_state' was not declared in this scope /usr/include/boost/thread/mutex.hpp:145: error: `state' was not declared in this scope /usr/include/boost/thread/mutex.hpp:145: error: invalid data member initialization /usr/include/boost/thread/mutex.hpp:145: error: variable or field `do_unlock' declared void /usr/include/boost/thread/mutex.hpp:145: error: declaration of `int boost::timed_mutex::do_unlock' /usr/include/boost/thread/mutex.hpp:143: error: conflicts with previous declaration `void boost::timed_mutex::do_unlock()' In file included from /usr/include/boost/thread.hpp:19, from simple.cpp:9: /usr/include/boost/thread/once.hpp:35: error: type specifier omitted for parameter `once_flag' /usr/include/boost/thread/once.hpp:35: error: parse error before `&' token In file included from /usr/include/boost/thread.hpp:20, from simple.cpp:9: /usr/include/boost/thread/recursive_mutex.hpp:55: error: `cv_state' was not declared in this scope /usr/include/boost/thread/recursive_mutex.hpp:55: error: `state' was not declared in this scope /usr/include/boost/thread/recursive_mutex.hpp:55: error: invalid data member initialization /usr/include/boost/thread/recursive_mutex.hpp:55: error: variable or field ` do_lock' declared void /usr/include/boost/thread/recursive_mutex.hpp:55: error: declaration of `int boost::recursive_mutex::do_lock' /usr/include/boost/thread/recursive_mutex.hpp:53: error: conflicts with previous declaration `void boost::recursive_mutex::do_lock()' /usr/include/boost/thread/recursive_mutex.hpp:56: error: `cv_state' was not declared in this scope /usr/include/boost/thread/recursive_mutex.hpp:56: error: `state' was not declared in this scope /usr/include/boost/thread/recursive_mutex.hpp:56: error: invalid data member initialization /usr/include/boost/thread/recursive_mutex.hpp:56: error: variable or field ` do_unlock' declared void /usr/include/boost/thread/recursive_mutex.hpp:56: error: declaration of `int boost::recursive_mutex::do_unlock' /usr/include/boost/thread/recursive_mutex.hpp:54: error: conflicts with previous declaration `void boost::recursive_mutex::do_unlock()' /usr/include/boost/thread/recursive_mutex.hpp:103: error: `cv_state' was not declared in this scope /usr/include/boost/thread/recursive_mutex.hpp:103: error: `state' was not declared in this scope /usr/include/boost/thread/recursive_mutex.hpp:103: error: invalid data member initialization /usr/include/boost/thread/recursive_mutex.hpp:103: error: variable or field ` do_lock' declared void /usr/include/boost/thread/recursive_mutex.hpp:103: error: declaration of `int boost::recursive_try_mutex::do_lock' /usr/include/boost/thread/recursive_mutex.hpp:100: error: conflicts with previous declaration `void boost::recursive_try_mutex::do_lock()' /usr/include/boost/thread/recursive_mutex.hpp:104: error: `cv_state' was not declared in this scope /usr/include/boost/thread/recursive_mutex.hpp:104: error: `state' was not declared in this scope /usr/include/boost/thread/recursive_mutex.hpp:104: error: invalid data member initialization /usr/include/boost/thread/recursive_mutex.hpp:104: error: variable or field ` do_unlock' declared void /usr/include/boost/thread/recursive_mutex.hpp:104: error: declaration of `int boost::recursive_try_mutex::do_unlock' /usr/include/boost/thread/recursive_mutex.hpp:102: error: conflicts with previous declaration `void boost::recursive_try_mutex::do_unlock()' /usr/include/boost/thread/recursive_mutex.hpp:154: error: `cv_state' was not declared in this scope /usr/include/boost/thread/recursive_mutex.hpp:154: error: `state' was not declared in this scope /usr/include/boost/thread/recursive_mutex.hpp:154: error: invalid data member initialization /usr/include/boost/thread/recursive_mutex.hpp:154: error: variable or field ` do_lock' declared void /usr/include/boost/thread/recursive_mutex.hpp:154: error: declaration of `int boost::recursive_timed_mutex::do_lock' /usr/include/boost/thread/recursive_mutex.hpp:150: error: conflicts with previous declaration `void boost::recursive_timed_mutex::do_lock()' /usr/include/boost/thread/recursive_mutex.hpp:155: error: `cv_state' was not declared in this scope /usr/include/boost/thread/recursive_mutex.hpp:155: error: `state' was not declared in this scope /usr/include/boost/thread/recursive_mutex.hpp:155: error: invalid data member initialization /usr/include/boost/thread/recursive_mutex.hpp:155: error: variable or field ` do_unlock' declared void /usr/include/boost/thread/recursive_mutex.hpp:155: error: declaration of `int boost::recursive_timed_mutex::do_unlock' /usr/include/boost/thread/recursive_mutex.hpp:153: error: conflicts with previous declaration `void boost::recursive_timed_mutex::do_unlock()' ///////////////////////// If I use commend g++ simple.cpp -pthread I got error //////// /tmp/cchxK5CW.o(.text+0x66): In function `main': : undefined reference to `boost::thread::thread[in-charge](boost::function0<void, std::allocator<boost::function_base> > const&)' /tmp/cchxK5CW.o(.text+0x9d): In function `main': : undefined reference to `boost::thread::join()' /tmp/cchxK5CW.o(.text+0xa8): In function `main': : undefined reference to `boost::thread::~thread [in-charge]()' /tmp/cchxK5CW.o(.text+0xc2): In function `main': : undefined reference to `boost::thread::~thread [in-charge]()' collect2: ld returned 1 exit status /////////// I do not know what went wrong. Can anyone tell me what I did wrong? How should I correct so that I can compile this example? TIA Tuan ========== #include <boost/thread.hpp> #include <iostream> using namespace std; void ciao() { cout << "Ciao, thread using boost" << endl; } /******** this is the main thread's code */ int main(int argc,char *argv[]) { boost::thread thrd(&ciao); thrd.join(); return(0); }

2 2

serialization binary_oarchive without signature?
by relative＠gmx.net 03 Nov '05

03 Nov '05

i'd like to use boost serialization to serialize > 1 independent objects to a large file through a seekable stream, i.e. > 1 serialization archives in one file. can you turn off the archive signature("serialization::archiv") at the beginning of the output, or do I have to write my own archive class for that? and 2nd, is there a way(except serializing to a std::stringstream) to find out the archive size beforehand, e.g. an archive class which doesn't really serialize things but add up the size in bytes of the binary output? thanks, -- 10 GB Mailbox, 100 FreeSMS/Monat http://www.gmx.net/de/go/topmail +++ GMX - die erste Adresse f�r Mail, Message, More +++

2 1

A question about boost::graph iterators
by Jeffrey Holle 03 Nov '05

03 Nov '05

I'm using gcc 4.0.2 with boost 1.33.0. I'm getting a compiler warning about taking the address of a temporary with the following code: Edge* TransshipmentPivotingRule::enteringEdge(const FeasibleSpanningTree* pFST) { graph_traits<AntiTree>::edge_iterator ei,ei_out; tie(ei,ei_out)=edges(*m_pAntiTree); return (find_if(ei,ei_out, ProfitableEdge(*m_pAntiTree,m_c,m_y,*pFST))!=ei_out) ? &*ei : NULL; } Note the "&*ei". I know that the iterator is tempory, but what the iterator is pointing to isn't. Is this a legit warning that I need to be concerned about? In case it matters, AntiTree is a filtered_graph.

2 2

Thread Pools
by Brian Cox 03 Nov '05

03 Nov '05

Hello, I read a few years ago that Bill Kempf was going to develop a thread pool for Boost.Threads. Does anyone know the status of that? Does anyone have any good examples of a thread pool or worker queue developed using Boost.Threads? Thanks for any info. -Brian-

1 0

[Boost][serialization] link problems with MSVC.NET/no bjam
by Topi Mäenpää 03 Nov '05

03 Nov '05

Hi, I have struggled to get the boost libraries link into my application with no success so far. I was able to compile most of the demo programs with bjam, but it seems that only static linking is used there. I'm using the dynamic versions. The libraries compiled fine with MSVC.NET 7.1. However, whenever I try to link them to an application, every symbol seems to be undefined. I turned on the diagnostics to see that the automatic linking is happening (with the nonstandard preprocessor stuff). I also added the libraries to my project manually without success. The funny (?) thing is that the lib file has a definition for the "missing" functions, except for one minor difference. This is the mangled symbol the linker complains about: __imp_?save@?$xml_oarchive_impl@Vxml_oarchive@archive@boost@@@archive@boost@@QAEXABV?$basic_string@GU?$char_traits@G@std@@V?$allocator@G@2@@std@@@Z (Omitting namespaces this one decrypts to xml_oarchive_impl<xml_oarchive>::save(basic_string& const)) This is what seems to be in the library: __imp_?save@?$xml_oarchive_impl@Vxml_oarchive@archive@boost@@@archive@boost@@QAEXABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z The only difference is that the library symbol contains a "D" and the linker is looking for "G" in a couple of places. I have found no way of going any further. Since the demos are built in debug mode and with static libraries, I found no useful information by inspecting the commands bjam uses in building them. Everything is just like I have in my own project. I have defined BOOST_SERIALIZATION_DYN_LINK, if you happen to think about that. I even managed to link my app with mingw, but got strange run-time errors. Everything works fine with gcc on Linux. Any advice? -Topi-

3 4

[Boost][serialization] Serialization and DLLs
by Topi Mäenpää 03 Nov '05

03 Nov '05

Hi, Some time ago, we had a discussion about serialization of dynamically loaded classes. I got my code work on Linux, but still cannot do the same on Windows. I'd like someone to elaborate the stuff below a bit: Robert Ramey wrote: > Another post has me convinced that the problem is that there are multiple > copies of a base class extended_type_info record which I believe > shouldn't occur. I can confirm that this indeed happens. > If you trap your debugger the serialization.dll (shared_lib) at line 58 of > extened_type_info.cpp you should trap every time an extended_type_info > record is "self_registered". Examination of the stack should reveal > where this is being called from. I expect that the base class is being > self registered from both the DLL as well as the main executable. Whenever I register a class from a DLL, its base classes get registered as well, although they already have been registered. If I load multiple DLLs that all contain derived classes, the base classes are registered many times, but only once for each DLL. > My current thinking is that this behavior should be prohibited and > detected with an exception. Other users have addressed this > by tweaking the code in extended_type_info.cpp to permit > multiple "self registration" of the same extended_type_info type. > This eliminated their symptoms and everything seems to work. > But from my understanding of the library, I believe this just > hides a deeper problem. Can someone point out the details? How should this be done? Any other suggestions? Best regards, Topi

2 1

Newbie help needed
by Ricardo Kirkner 03 Nov '05

03 Nov '05

Hi: I am trying to write python bindings for an already existant c++ library. I started using pyste, because I felt this was the easiest way to do it. However I keep getting errors (mostly I think because of string and vector arguments conversion). I just wanted to ask if I am on the right track here. Maybe someone can give me some pointers on how to make this task easier? (I was tempted to switch to pyrex, swig, etc, but everything seems to have its own problems.) Should I use pyste, or should I rather write boost.python code directly? Thank you, Ricardo

2 1

enable_if, type_traits and Visual C++ 7.0
by Ovanes Markarian 03 Nov '05

03 Nov '05

Hello all, I am trying to get enable if to work with Visual C++ 7.0 and boost 1.33. for the following member function implemenation I get an error: template<> typename boost::enable_if<boost::is_pointer<_ElemFct::result_type>, _ElemFct::result_type>::type operator->() { return get_at(ptr_coll, pos); } template<> typename boost::enable_if<boost::is_reference<_ElemFct::result_type>, boost::add_pointer<_ElemFct::result_type>::type>::type operator->() { return &(get_at(ptr_coll, pos)); } My compiler is in German. I have tried to translate the error messages... error C2504: 'boost::enable_if_does_not_work_on_this_compiler<T>' : Base class undefined with [ T=boost::function2<std::string &,MemberTest *,int,int>::result_type ] see reference to the instance of compiled class template 'boost::enable_if<Cond,T>' with [ Cond=boost::is_pointer<boost::function2<std::string &,MemberTest *,int,int>::result_type>, T=boost::function2<std::string &,MemberTest *,int,int>::result_type ] see reference to the instance of compiled class template 'generic_iterator<_Coll,_Ty,_ElemFct,_LenFct,_Diff,_Ptr,_Ref,_Cat>' with [ _Coll=MemberTest, _Ty=std::string, _ElemFct=element_retrieval, _LenFct=length_retrieval, _Diff=int, _Ptr=std::string *, _Ref=std::string &, _Cat=std::bidirectional_iterator_tag ] error C2039: 'type' : Is not an element of 'boost::enable_if<Cond,T>' with [ Cond=boost::is_pointer<boost::function2<std::string &,MemberTest *,int,int>::result_type>, T=boost::function2<std::string &,MemberTest *,int,int>::result_type ] With Kind Regards, Ovanes Markarian

2 1

[date-time] posix timezone string
by Stering Wolfram 03 Nov '05

03 Nov '05

Hi, I am implementing a year_based_date-derived date generator to calculate the easter sunday for a given year. Now, this is the easy part, and it is done already. But I wonder how to generate a meaningful posix timezone string that is expected to result from calling the generator's to_string() member. The documentation at the (not well formatted, b.t.w.) "Description" section of class posix_time_zone didn't give any hints for Easter Sunday either. Any ideas? regards, -wolfi -- DI Wolfram Stering (Entwicklung) HALE electronic GmbH., Salzburg, Austria Tel: +43 (662) 439011 550 Fax: +43 (662) 439011 9 Email: wolfram.stering(a)hale.at

2 1

How to apply -Winline with Bjam v2
by Jeffrey Holle 03 Nov '05

03 Nov '05

I am using gcc 4.0.2 and Boost.Jam Version 3.1.11. I've been told that the way to determine if an inline method is actually inline by the compiler is to compile with the "-Winline" option. When this is done, a warning is emmitted when a sugguested inline method wasn't inlined. I'm using bjam v.2. I have not found the equivalent to "features.jam" in the v2 documentation, so I tried "<cxxflags>-Wonline", which I got from /tools/build/v1/features.jam. This doesn't work. What is the way to do it in Bjam v2?

1 0

design question for boost::program_options and dynamic options
by boost＠nogga.de 02 Nov '05

02 Nov '05

Hello, I'm new to the boost::program_options library and tried to use it for a command pattern based software. The program is launched with the following commandline: > program command [Options] <Files> The program can use different output formatters with --formatter={XML|binary|text}. Every command and formatter specify their own set of options. I first tried to collect all options form the commands and formatters and parse the command line only once. This lead to the problem, that due to the different positional options information the commandline parser always threw an exception due to wrong command line formatting. Since I couldn't find a way to add mutliple optional option groups to the parser, I moved the parsing code into my command base class and query the derived commands for the different required information, like: class Command { public: vritual options_description GetOptionsDescription (); virtual options_description GetHiddenOptionsDescription (); virtual positional_program_options GetPositionalProgramOptions (); virtual Run (variables_map const & vm) = 0; int Execute (std::vector<std:.string> args) { options_description desc; descr.add (GetOptionsDescription ()).add (GetHiddenOptionsDescription ()); variables_map vm; store(command_line_parser(args) .options(desc). .positional(GetPositionalProgramOptions ()) .run(), vm); notify(vm); Run (vm); } } The execute function is called form the program main after the "command" has been stripped from the commandline and the concrete command was created by the factory. So far so good. This works for the different commands, but not for the formatters. How can I parse the command line dynamically? E.g. if I encounter the "--formatter=xml" argument, a new XMLFormatter is created and the options description from this formatter are added to list of valid options? I know, that there is the notify mechanism, but this only works after the commandline has been successfully parsed. And also the custom parsers do not solve my problem. Any idea how to solve this issue? Best regards Dirk

2 2

Tokenizer: how to eliminate unwanted null tokens?
by CN 02 Nov '05

02 Nov '05

Hi! The following code uses '\0' and ';' as seperators and produces the result: <X><Y><><Z><> string str=string("X;Y\0\0Z\0",7); typedef tokenizer<boost::escaped_list_separator<char> > Tok; escaped_list_separator<char> sep(string(),string("\0;",2),string()); Tok tokens(str, sep); for(Tok::iterator i = tokens.begin();i != tokens.end();++i) cout << "<" << *i << ">"; How to revise it in order to get this result? <X><Y><Z> Thank you in advance! CN -- http://www.fastmail.fm - Does exactly what it says on the tin

2 1

configuring a library to work with multiple versions of boost
by Ross Boylan 01 Nov '05

01 Nov '05

I have a library that uses boost and also uses a pre-release version of the ptr_container (header only) library that eventually made it into boost 1.33 (I think). I would like people to be able to compile my code with various versions of boost. I've had it working with 1.31 and 1.32, and expect to have it working with 1.33 when that reaches my distribution. I have a subdirectory with the pre-release ptr_container library and some supporting code from elsewhere in boost. This is in a "boost" subdirectory of my project, which has included the directory above that unconditionally in my compilations. With 1.33 I think I want to ignore my local stuff completely. I'm using autoconf and libtool. Are there autoconf macros available for detecting the boost libraries? Do people have any suggestions about the best way to proceed? One possibility that occurs to me is to test for the version of the library at configure time, and make the include path depend on the results. Thanks. Ross Boylan

2 2

ptr_map
by Oleg Smolsky 01 Nov '05

01 Nov '05

Hello Thorsten, thanks for the ptr_vector clarifications. I have another question about ptr_map: I can declare a map iterator in the following way: ptr_map<string, SomeClass>::iterator i = m.begin(); Now, I'd expect to be able to compile the following, as with a normal map: string s = i->first; i->second.SomeMethod(); ...assuming SomeClass::SomeMethod() exists and is declared as public. However, "first" and "second" don't seem to exist in ptr_map. Could you shed some light on how I can iterate your map please? Best regards, Oleg.

2 3

[test]
by Paul Giaccone 01 Nov '05

01 Nov '05

Is the use of BOOST_CHECK_EQUAL not permitted in init_unit_test_suite(int argc, char* argv[])? The following code throws an exception and reports the error "Boost.Test internal framework error: unknown reason" boost::unit_test::test_suite* init_unit_test_suite(int argc, char* argv[]) { BOOST_CHECK_EQUAL(foo(argc, argv), 0); boost::unit_test::test_suite* test = BOOST_TEST_SUITE("My test"); test -> add(BOOST_TEST_CASE(&test1)); test -> add(BOOST_TEST_CASE(&test2)); return test; } when the following works without any problems: boost::unit_test::test_suite* init_unit_test_suite(int argc, char* argv[]) { int result = foo(argc, argv); assert(result == 0); boost::unit_test::test_suite* test = BOOST_TEST_SUITE("My test"); test -> add(BOOST_TEST_CASE(&test1)); test -> add(BOOST_TEST_CASE(&test2)); return test; } I have no problem with using the latter code, but I am surprised that I get an exception in the former code and that it is caught by "..." and not by the library. If BOOST_CHECK_EQUAL (and BOOST_CHECK, BOOST_CHECK_CLOSE, etc) is not allowed in init_unit_test_suite(), is this fact documented? Should it generate an exception that can be caught by the library and reported with a useful message? Thanks, Paul

2 2

Re: [Boost-users] [Multi-Index] composite_key problems
by JOAQUIN LOPEZ MU?Z 01 Nov '05

01 Nov '05

----- Mensaje original ----- De: Andreas Volz <lists(a)brachttal.net> Fecha: Martes, Noviembre 1, 2005 0:28 am Asunto: Re: [Boost-users] [Multi-Index] composite_key problems > I got it working! Perhaps I've some more questions, but for now I > couldcontinue my work. Excellent! Good luck with your project. > > Did someone create a SQL language wrapper around multi_index? I think > this could be a very great feature. People that know SQL could really > easy use it without learning too much other stuff. There's currently a very active debate going on with respect to the merits of two libraries which offer a more SQL-friendly interface to handle multi-index data structures (none of them is actually SQL compatible, though.) Google for RML site:boost.org to get some links to the discussion. RML site is http://visula.org/relational/ while RTL stuff can be found at http://boost-consulting.com/vault/index.php? &direction=0&order=&directory=RTL > I thought about > using a lightweight SQL lib (e.g. sqlite) before I found multi_index. > But I don't save my data into a file, so multi_index fits perfect. > You can also save/load multi_index_containers contents to/from a file via Boost.Serialization. Check http://boost.org/libs/multi_index/doc/advanced_topics.html#serializatio n Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

Visual C++ 2005 (8.0) support
by Ovanes Markarian 01 Nov '05

01 Nov '05

Hi all, did someone test boost 1.33 with Visual C++ 2005(8.0)? I am wondering how I can compile the library using jam. Should I use VC++ 7.1 option? Another question. I derived an iterator from the iterator_facade template. As I have recently found out VC++ 8.0 did not support friend template classes, e.g. template<class ....> class my_type { template <class> friend class my_type; ... }; This will not work in VC++ 8.0. Did you know about this issue? Should this be filed as a bug at MS? With Kind Regards, Ovanes Markarian

5 5

Re: [Boost-users] problem with multi_index_container -> find
by JOAQUIN LOPEZ MU?Z 01 Nov '05

01 Nov '05

Hi Oliver, ----- Mensaje original ----- De: Oliver.Kowalke(a)infineon.com Fecha: Martes, Noviembre 1, 2005 10:38 am Asunto: [Boost-users] problem with multi_index_container -> find > Hello, > I don't understand why this code doesn't compile (gcc-3.3.1) '... > id_index.find( id) ...' ? > Regards, > Oliver [...] > phonebook::iterator itr = id_index.find( id); // <<== doesn't id_index.find() returns a phonebook::nth_index_iterator<1>::type. phonebook::iterator is shorthand for phonebook::nth_index_iterator<0>::type, a different type. The following should work phonebook::nth_index_iterator<1>::type itr = id_index.find(id); or alternatively phonebook::nth_index<1>::type::iterator itr = id_index.find(id); Hope this helps, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

How to build Boost for Cygwin (asked the noob)
by Olumide 01 Nov '05

01 Nov '05

Hi - Would someone please give me some (SIMPLE) pointers on how to build Boost for Cygwin. Thanks, - Olumide

2 1

[threads] read_write_mutex and condtion
by Phil Endecott 01 Nov '05

01 Nov '05

Dear All, Is it possible to use a boost::condition in combination with a read_write_mutex? I've tried but failed. This is with 1.32.0. My test code follows. As you can see it can use either a mutex or a read_write_mutex depending on which bits are commented-out. It works as expected with a mutex, but with a read_write_mutex I get a compiler error, shown below. Perhaps I am missing some fundamental reason why conditions can't work with read_write_mutexes. Can someone explain? Thanks, Phil. #include <string> #include <iostream> #include <boost/thread/mutex.hpp> #include <boost/thread/read_write_mutex.hpp> #include <boost/thread/condition.hpp> #include <boost/thread/thread.hpp> #include <boost/bind.hpp> #include <unistd.h> using namespace std; using namespace boost; struct shared_thing { string data; //typedef mutex mx_t; //typedef mutex::scoped_lock read_lock; //typedef mutex::scoped_lock write_lock; typedef read_write_mutex mx_t; typedef read_write_mutex::scoped_read_lock read_lock; typedef read_write_mutex::scoped_write_lock write_lock; mx_t mx; condition cn; shared_thing::shared_thing(void): //mx() mx(read_write_scheduling_policy::writer_priority) {} void writer(void) { while(1) { sleep(1); { write_lock l(mx); data += "."; cn.notify_all(); } } } void reader(void) { while(1) { read_lock l(mx); cn.wait(l); cout << data << endl; } } }; int main(int argc, char* argv[]) { shared_thing t; thread wr_thread(bind(&shared_thing::writer,&t)); t.reader(); } $ g++ -pthread -O -Wall -o condvar condvar.cc -lboost_thread /usr/include/boost/thread/detail/read_write_lock.hpp: In member function `void boost::condition::wait(L&) [with L = boost::detail::thread::scoped_read_lock<boost::read_write_mutex>]': condvar.cc:51: instantiated from here /usr/include/boost/thread/detail/read_write_lock.hpp:297: error: ` boost::read_write_mutex&boost::detail::thread::scoped_read_lock<boost::read_write_mutex>::m_mutex ' is private /usr/include/boost/thread/condition.hpp:92: error: within this context

3 2

problem with multi_index_container -> find
by Oliver.Kowalke＠infineon.com 01 Nov '05

01 Nov '05

Hello, I don't understand why this code doesn't compile (gcc-3.3.1) '... id_index.find( id) ...' ? Regards, Oliver #include <iostream> #include <string> #include <utility> #include <boost/multi_index_container.hpp> #include <boost/multi_index/key_extractors.hpp> #include <boost/multi_index/ordered_index.hpp> #include <boost/tuple/tuple.hpp> namespace mi = boost::multi_index; struct phonebook_entry { int id; std::string family_name; std::string given_name; phonebook_entry( int id_, std::string const& family_name_, std::string const& given_name_) : id( id_), family_name( family_name_), given_name( given_name_) {} }; typedef mi::multi_index_container< phonebook_entry, mi::indexed_by< mi::ordered_non_unique< mi::composite_key< phonebook_entry, mi::member< phonebook_entry, std::string, & phonebook_entry::family_name >, mi::member< phonebook_entry, std::string, & phonebook_entry::given_name > > >, mi::ordered_unique< mi::member< phonebook_entry, int, & phonebook_entry::id > > > > phonebook; void test_multi_index() { phonebook pb; phonebook::nth_index< 0 >::type & name_index = pb.get< 0 >(); std::string family_name("Mann"); std::string given_name("Thomas"); std::pair< phonebook::iterator, phonebook::iterator > p = name_index.equal_range( boost::make_tuple( family_name, given_name) ); while ( p.first != p.second) { std::cout << p.first->family_name << ", " << p.first->given_name << std::endl; ++p.first; } phonebook::nth_index< 1 >::type & id_index = pb.get< 1 >(); int id = 1; phonebook::iterator itr = id_index.find( id); // <<== doesn't // error: conversion from ` boost::multi_index::detail::index_iterator<boost::multi_index::detail::o rdered_index_node<boost::multi_index::detail::index_node_base<phonebook_ entry> > >' to non-scalar type ` // boost::multi_index::detail::index_iterator<boost::multi_index::detail::o rdered_index_node<boost::multi_index::detail::ordered_index_node<boost:: multi_index::detail::index_node_base<phonebook_entry> > > >' //requested phonebook::iterator end = id_index.end(); if ( itr != end) std::cout << itr->family_name << ", " << itr->given_name << std::endl; }

1 0

Re: [Boost-users] [Multi-Index] composite_key problems
by JOAQUIN LOPEZ MU?Z 31 Oct '05

31 Oct '05

----- Mensaje original ----- De: Andreas Volz <lists(a)brachttal.net> Fecha: Lunes, Octubre 31, 2005 7:27 pm Asunto: Re: [Boost-users] [Multi-Index] composite_key problems > The questions seems to by stupic, but how > could I > access the data looked up by B alone? What should I assign to the > left? > > ??? = es.get<1>().find(b); > > An iterator or what else? This returns an iterator, yep. Please notice that es.get<1>() returns a reference to an index, which is, in many respects, entirely similar to a regular std::set. So you have find(), equal_range() etc. just like in the STL case, with equivalent syntax and semantics. You might want to give the Boost.MultiIndex tutorial a further read --anyway, don't hesitate to come back here if things aren't still clearer. Joaquin M Lopez Muñoz Telefonica, Investigacion y Desarrollo

2 1

Re: [Boost-users] Translating an absolute path to a path relative
by Gottlob Frege 31 Oct '05

31 Oct '05

> > Date: Mon, 31 Oct 2005 09:55:57 -0300 > From: Hermann Rodrigues <hermann.rodrigues(a)gmail.com> > Subject: [Boost-users] Translating an absolute path to a path relative > to the current directory > To: boost-users(a)lists.boost.org > Message-ID: > <497dfc460510310455j1bd56615peffd2f6040fe849e(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi, > > I am running into the following problem these days: > > I need to translate an absolute path to a path relative to the current > directory on Windows. The translation process need to include all > required ".." directory specifiers in the path to make sure it can be > accessed from the current directory. > > Have you tried the Windows functions such as PathRelativePathTo, and its compliment PathCombine?

2 1

[BUG] missing references in docs on web site (threads)
by Ross Boylan 31 Oct '05

31 Oct '05

While reading the web pages for the threads library I noticed some missing references. I don't know if they reflect a problem with the documentation source or a problem with the processing converting the source into html (if there was any such processing). I did check the html source of teh web pages to verify that it wasn't a display problem with my browser. http://boost.org/doc/html/threads.html#id1357380 In "Potentially non-thread-safe functions" this appears: "It is possible to write thread-safe implementations of these by using thread specific storage (see boost::thread_specific_ptr), and several C++ compiler vendors do just that. The technique is well-know and is explained in ." The reference at the end is missing. I thought I saw another example like this in the threads doc, but can't find it now. Also, the quote from Brinch Hansen at the end of http://boost.org/doc/html/threads/rationale.html doesn't indicate the source (though one could at least guess the article from the bibliography, though he's co-author of another one in the bibliography).

1 0

Re: [Boost-users] [Multi-Index] composite_key problems
by Andreas Volz 31 Oct '05

31 Oct '05

Am Mon, 31 Oct 2005 18:14:00 +0100 schrieb JOAQUIN LOPEZ MU?Z: > // lookup by (A,B); > > es.find(make_tuple(a,b)); > > // lookup by A alone > > es.find(make_tuple(a)); > > // lookup by B alone > // note get<1> retrieves the second index. > > es.get<1>().find(b); > > Is the issue clearer now? If not, please tell me > so and I'll try to explain myself a bit further. A little clearer, but not at all. I'm really new to Boost, so I doesn't understand all. The questions seems to by stupic, but how could I access the data looked up by B alone? What should I assign to the left? > ??? = es.get<1>().find(b); An iterator or what else? There was a print_out_by_name function in docs that I tried to adopt, but I failed. And the compile errors are not very helpfull. As normal with template programming :-( regards Andreas

1 0

[Boost.filesystem] Support of Unicode OS ?
by Marc Viala 31 Oct '05

31 Oct '05

Hi, I would like to know if there are some implementations of "Boost.filesystem" to support Unicode OS like Windows XP? We are involved in a large project, we use Boost libraries intensively, version 1.33, and we are looking forward for this mandatory feature. Thanks in advance for your reply. Marc Viala www.acticm.com <http://www.acticm.com> mailto:mviala@acticm.com <mailto:mviala@acticm.com>

1 0

C++ Connections question
by Elisha Berns 31 Oct '05

31 Oct '05

Ok, So this isn't a Boost.X question, but I have to ask since Dave Abrahams is giving two talks at the C++ Connections conference next week. The question is since the sessions, any session not just Dave's, are either only 60 or 75 minutes max, how informative and in depth can they possibly be? It would appear they are only to whet one's appetite for learning something, but that is precisely my question. Thanks for offering an appraisal whether this conference is really worth the bother. Elisha Berns e.berns(a)computer.org tel. (310) 556 - 8332 fax (310) 556 - 2839

2 1

Re: [Boost-users] downcasting shared pointer
by Bjorn.Karlsson＠readsoft.com 31 Oct '05

31 Oct '05

Hello Faheem, > From: Faheem Mitha [mailto:faheem@email.unc.edu] > > It would be nice if there was some method to downcast the shared_ptr > itself. See http://www.boost.org/libs/smart_ptr/shared_ptr.htm#static_pointer_cast for details on how to do just that. Regards, Bjorn Karlsson

2 1

Implementing lock/unlock with boost::thread
by Johan Torp 31 Oct '05

31 Oct '05

I'm trying to implement a class having a lock and an unlock-method. If several different threads call scoped_lock::lock, what is the effect? class AntiRAII{ public: AntiRAII() : mLock(mMutex, false) {} void Lock() {mLock.lock(); } void Unlock() {mLock.unlock();} private: boost::mutex mMutex; boost::mutex::scoped_lock mLock; }; I cannot find any documentation on the behaviour. The usual usage of scoped_lock is one per thread, which is why I'm sceptical to this approach. How can this be implemented? Is it better to expose the mutex? Regards, Johan Torp

3 2

Re: [Boost-users] [Multi-Index] composite_key problems
by JOAQUIN LOPEZ MU?Z 31 Oct '05

31 Oct '05

----- Mensaje original ----- De: Andreas Volz <lists(a)brachttal.net> Fecha: Domingo, Octubre 30, 2005 8:15 pm Asunto: [Boost-users] [Multi-Index] composite_key problems > Hi, > > I like to build a data structure and like to access it with different > keys, so I try multi_index for this. [...] > I hacked the basic example to get this working. My example compiles, > but if I execute it, I get only warnings: > > probe: /usr/include/boost/multi_index/detail/index_iterator.hpp:107: > typename Node::value_type& > boost::multi_index::detail::index_iterator<Node, > Container>::operator*() const [with Node = > Container>boost::multi_index::detail::ordered_index_node<boost:: > multi_index::detail::index_node_base<learnedMeasure> > Container>>, Container = > Container>>boost::multi_index::detail::ordered_index<boost:: > multi_index::composite_key<learnedMeasure, > Container>>boost::multi_index::member<learnedMeasure, std::string, > Container>>&learnedMeasure::measu > .... more warnings > > I put my example code online. Perhaps someone could take a look in it > and help me to find this problem. > > http://cpp.sourceforge.net/?show=9550 > Hello Andreas, I can't compile your source right now, but from the looks of it I cannot see anything wrong. What compiler are you using? If MSVC++ 6.0 or 7.0, take into account they have non-conformances you must take into account when using Boost.MultiIndex, see http://boost.org/libs/multi_index/doc/compiler_specifics.html Your particular code won't work on either of these compilers due to problems with member<> and composite_key that are addresses in the aforementioned page. Is this the problem? If not, I'll try to get back to you in a couple of days. Best, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

regexp: New problem with trailing - in character class
by Greg Ferrar 31 Oct '05

31 Oct '05

Hi, I've been using Boost regexp library forever, and it's great. But I just grabbed 1.33.0 (trying to get it to compile on 64-bit Windows), and I'm getting an error I never got before: it refuses to allow this regular expression: [a-z-] which is supposed to mean "a lower case letter or a dash". Previous versions of Boost regexp allowed this, and grep allows it, and version 1.33.0 does allow this one: [-a-z] Is this a deliberate restriction? It's causing me lots of problems, because my application has a lot of existing regular expressions which use this syntax. This occurs both on x64 with VC8, and on a pretty standard (and old) 32-bit Linux system. I've hacked around it horribly for now by adding this to the top of regcompA (I use the A posix interface exclusively): // HACK by GMF to fix problem that [a-z-] is not accepted as valid, but [-a-z] is. Fix it by moving the dash. char *p = (char*) ptr; while (*p) { printf("p: %c\n", *p); if (*p == '\\') p++; else if (*p == '[') { char *q = p+1; while (*q && (*q != ']')) { printf("*q: %c\n", *q); q++; } if (*q == ']') { q--; if (*q == '-') { memmove(p+2, p+1, (q-p)-1); *(p+1) = '-'; p = q; } } } p++; } but that's very nasty, and probably doesn't work properly anyway, and I'd sure like to get that out of my production code. Help! Greg

2 1

Using iterator_facade from base class with sub classes
by Daniel Lidström 31 Oct '05

31 Oct '05

Hello! I have implemented the iterator_facade for a base class called DataObject. So now I am able to write things like this: boost::shared_ptr<PxyFileData> file(...); const DataObject& points = file->GetPoints(); int num_points = std::distance(points.begin(), points.end()); //! random access iterator A DataObject acts like a tree structure. Each DataObject holds a vector of pointers to children, which are also DataObjects. Now to my problem: A PxyPoint is a sub class to DataObject, and PxyFileData::GetPoints() returns a DataObject where all the children are PxyPoint's. Now I would like to call a member function, PxyPoint::PutSpCode(const char*), on each of the children, like this: void put_sp_code(DataObject&, const char*); void test() { shared_ptr<PxyFileData> file(...); DataObject& points = file->GetPoints(); put_sp_code(points, "spcode"); } void put_sp_code(DataObject& points, const char* code) { std::for_each(points.begin(), points.end(), std::bind2nd(std::mem_fun(&PxyPoint::PutSpCode), code)); } This does not compile (VC 7.1): c:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\algorithm(21): error C2664: 'binder2nd<_Fn2>::result_type binder2nd<_Fn2>::operator ()(binder2nd<_Fn2>::argument_type & ) const': cannot convert parameter 1 from 'DataObject' to 'binder2nd<_Fn2>::argument_type & ' with [ _Fn2=mem_fun1_t<void,TPunkt,const char *> ] and [ _Fn2=mem_fun1_t<void,TPunkt,const char *> ] A reference that is not to 'const' cannot be bound to a non-lvalue c:\projects\GEOW\V12\Test\GeoTest\Model Test\ModelTest.cpp(48): see reference to function template instantiation '_Fn1 for_each<iter,binder2nd<_Fn2> >(_InIt,_InIt,_Fn1)' being compiled with [ _Fn1=binder2nd<mem_fun1_t<void,TPunkt,const char *> >, _Fn2=mem_fun1_t<void,TPunkt,const char *>, _InIt=iter ] (error message formatted with STLTask) Is this possible with our design? I would like to be able to do this without having to create a PxyPointList, that derives from DataObject and only stores PxyPoint's (my guess is that something like that would work with this code). Thanks in advance! Regards, Daniel

3 2

Re: [Boost-users] [multi_index] non-intrusive keys
by JOAQUIN LOPEZ MU?Z 31 Oct '05

31 Oct '05

----- Mensaje original ----- De: Adi Shavit <adish(a)gentech.co.il> Fecha: Viernes, Octubre 28, 2005 4:11 pm Asunto: [Boost-users] [multi_index] non-intrusive keys > Hi, > > In my application I used a multi_map of multi_maps as a data > structure to provide indexing with 2 keys, say long strings. Access > is > logarithmic on both keys and the keys are not part of the stored > object, > thus are potentially only stored once. > > I'd like to use multi_index as a more elegant replacement. > However, I'm not clear about where the keys are stored. > > In my app, the keys are stored separately from the data, as the > keys to > maps, as part of the map data structure. > It seems that in multi_index the keys have to be inside the stored > data.In this case, 10 objects with the same key(s) will all have to > hold > copies of the keys (as members). > > Is there a way to avoid this? > I don't think you can avoid duplication of keys --if the keys are really expensive to duplicate, you might consider holding shared_ptrs to them, but this is AFAICS the furthest you can get. Take into acount that a multi_index_container with two keys is not a map of maps. These are different beasts, serving different purposes, * a map of maps applies two concatenated lookups to get to a "terminal" object, * a multi-index container with two indices applies either one of two poosible lookups to get to the object, so you might want to ask yourself whether it makes sense to try to replace your current code with Boost.MultiIndex. What are the advantages / use cases you envision? Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

Problems comping Boost.Iostreams on Windows with zlib support
by Adam M 31 Oct '05

31 Oct '05

Hi all, I am trying to compile Boost on my Windows 2000 box, but I need to enable the zlib support in Boost.Iostreams for the project I'm working on. I read through the "Getting Started" guide and the Boost.Iostreams docs, and I have done what it says to have zlib support installed, but it's not working. I downloaded the zlib DLL from their website and extracted it to C:/zlib Here's my bjam command line: bjam "-sNO_COMPRESSION=0 -sTOOLS=vc-7_1 -sNO_ZLIB=0 -sZLIB_BINARY=zdll -sZLIB_INCLUDE=C:/zlib/include -sZLIB_LIBPATH=C:/zlib/lib" install When I do that, bjam says: "Building Boost.Iostreams with zlib and gzip support disabled. To enable zlib and gzip, consult the Boost.Iostreams documentation." I thought maybe it was a red herring, so I let the compile finish anyway. However, there's no "libboost_zlib-*" in my Boost/lib folder. Can someone enlighten me as to what I've done wrong here? I'm stumped. Thanks, Adam

2 1

Templates Question
by Surya Kiran Gullapalli 31 Oct '05

31 Oct '05

Hi, I'm writing a templated class, and i dont want to use the class otherthan for some predetermined types, say, int, double etc. This class has no meaning for typenames other than those few. ========================= template <class T> myClass {....} ; myClass<int> intClass ; myClass<float> floatClass ; myClass<char> charClass ; ========================= The compiler should not complain for the first 2 instantiations, but should bail out at the 3rd instantiation (charClass). Is there any way i can achieve this, using standard c++ or boost. I've tried explicit template instantiation, (by passing a flag to my compiler), but in that case, i've to do that for every class suppose i try to invoke std::vector <someOtherClass> someVector; I've to instantiate this also explicitly. (which is a problem for me, because, I use a lot of standard library, and its a pain for me to instantiate every time. Also, if i do the above, i can always instantiate myClass also like this. template class myClass <someOtherClass> ; and which i want to avoid this.. to summarize my question, is there any way i can restrict the compiler to accept only few type names for my templated class (i.e., using standard c++ or boost) Thanks, Surya

4 5

Using a set with kruskal_minimum_spanning_tree
by Jeffrey Holle 30 Oct '05

30 Oct '05

I've sucessfully created an program that uses kruskal_minimum_spanning_tree. I presently give a vector container to this algorithm, which it populates in providing its answer. Now I want to optimize my program by switching to set. For vector, I use "back_inserter(m_spanningTreeEdges)". For set, I've attempted to use "inserter(m_spanningTreeEdges,m_spanningTreeEdges.end())", but this doesn't work. Can somebody tell me the correct way to code this, or tell me that it isn't possible?

1 1

downcasting shared pointer
by Faheem Mitha 30 Oct '05

30 Oct '05

Hi, I was wondering what the recommended way was to downcast shared pointers. I have a a base class, Base, and a derived class Derived. I have a Base shared pointer which points to a Derived object. shared_ptr<Base> d; As part of a unit test, I'm trying to extract the Derived object from it. *static_cast<Derived *>(d.get()); Here I'm extracting the raw pointer, downcasting it to Derived, and then taking the value. It would be nice if there was some method to downcast the shared_ptr itself. Thanks in advance. Please CC me on any reply. Faheem.

1 0

[Multi-Index] composite_key problems
by Andreas Volz 30 Oct '05

30 Oct '05

Hi, I like to build a data structure and like to access it with different keys, so I try multi_index for this. My data structure looks like this: struct learnedMeasure { // target_name + measure_name together is the composite key std::string target_name; std::string measure_name; float negative; float positive; float zero; } I like to access this data structure like this in SQL: SELECT measure, Negative, Positive, Zero from tabelle WHERE target_name='xxx' SELECT Target_name, Negative, Positive, Zero from tabelle WHERE measure_name='xxx' SELECT Negative,Positive,Zero from tabelle WHERE measure_name='xxx' AND Target_name='yyy' I hacked the basic example to get this working. My example compiles, but if I execute it, I get only warnings: probe: /usr/include/boost/multi_index/detail/index_iterator.hpp:107: typename Node::value_type& boost::multi_index::detail::index_iterator<Node, Container>::operator*() const [with Node = Container>boost::multi_index::detail::ordered_index_node<boost:: multi_index::detail::index_node_base<learnedMeasure> Container>>, Container = Container>>boost::multi_index::detail::ordered_index<boost:: multi_index::composite_key<learnedMeasure, Container>>boost::multi_index::member<learnedMeasure, std::string, Container>>&learnedMeasure::measu .... more warnings I put my example code online. Perhaps someone could take a look in it and help me to find this problem. http://cpp.sourceforge.net/?show=9550 regards Andreas

1 0

Problem compiling date_time in Boost 1.33 with STLport 1.4.6 & VC7.1 - log.txt [1/1]
by Didier Malenfant 30 Oct '05

30 Oct '05

I've attached the error log to this message. I've tried searching through the list archive for related problems but came back empty handed (although some posts seem to blame the widechar support?) Any help appreciated. -D x86\bjam.exe "-sTOOLS=vc-7_1-stlport" "-sSTLPORT_PATH=.." "-sPYTHON_ROOT=c:\Python24" ************************************************upport disabled. ECHO To enable bzip2, consul********************************************** ******************************************lib and gzip support disabled. To enable zlientation ****************************************************** Building Boost.Regex wite\build\boost_date_time.dll\vc-7_1-stlport\de of type 'boost::date_time::date_names_put<Co::operator >><Target>(InputStreamable &)' bei Target=boost::date_time::date_names_put<ource=NewSource, InputStreamable=boost::date_time::date_names_put<boost::greg_t>>>::string_type ] C:\wor.hpp(175) : see reference to function templat [ Target=boost::date_time::date_names_put<boost::gregorian::greg_facype, Config=boost::gregorian::greg_facet_config, charT=wchar_t, OutputIterator=_STL::ostreambuf_ Source=const wchar_t * class-template member function 'void boost::type &,const charT *const ) const' wt_1_33_0\libs\date_time\build\../src\gregorian\greg_month.cpp(147) : see reference to clasll_date_names_put<Config,charT>' being compilSTLport-4.6.2\stlport\stdexcept(149) : see re::basic_string<_CharT,_Traits,_Alloc>' being _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(149) : see reference ttring<_CharT,_Traits,_Alloc>' being compiled char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(149) : see reference to class tarT,_Traits,_Alloc>' being compiled _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(149) : see reference to class template i [ _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(149) _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(149) : see re::basic_string<_CharT,_Traits,_Alloc>' being _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(141) : see reference ttring<_CharT,_Traits,_Alloc>' being compiled char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(141) : see reference to class tarT,_Traits,_Alloc>' being compiled _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(141) : see reference to class template i [ _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(141) _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(141) : see re::basic_string<_CharT,_Traits,_Alloc>' being _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(141) : see reference ttring<_CharT,_Traits,_Alloc>' being compiled char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(133) : see reference to class tarT,_Traits,_Alloc>' being compiled _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(133) : see reference to class template i [ _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(133) _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(133) : see re::basic_string<_CharT,_Traits,_Alloc>' being _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(133) : see reference ttring<_CharT,_Traits,_Alloc>' being compiled char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(133) : see reference to class tarT,_Traits,_Alloc>' being compiled _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(125) : see reference to class template i [ _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(125) _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(125) : see re::basic_string<_CharT,_Traits,_Alloc>' being _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(125) : see reference ttring<_CharT,_Traits,_Alloc>' being compiled char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(125) : see reference to class tarT,_Traits,_Alloc>' being compiled _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(125) : see reference to class template i [ _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(117) _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(117) : see re::basic_string<_CharT,_Traits,_Alloc>' being _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(117) : see reference ttring<_CharT,_Traits,_Alloc>' being compiled char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(117) : see reference to class tarT,_Traits,_Alloc>' being compiled _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(117) : see reference to class template i [ _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(117) _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(109) : see re::basic_string<_CharT,_Traits,_Alloc>' being _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(109) : see reference ttring<_CharT,_Traits,_Alloc>' being compiled char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(109) : see reference to class tarT,_Traits,_Alloc>' being compiled _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(109) : see reference to class template i [ _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(109) _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(109) : see re::basic_string<_CharT,_Traits,_Alloc>' being _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(101) : see reference ttring<_CharT,_Traits,_Alloc>' being compiled char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(101) : see reference to class tarT,_Traits,_Alloc>' being compiled _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(101) : see reference to class template i [ _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(101) _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(101) : see re::basic_string<_CharT,_Traits,_Alloc>' being _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(101) : see reference ttring<_CharT,_Traits,_Alloc>' being compiled char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(93) : see reference to class template instantiation '_STL::basic_string<_Cha _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexc [ _CharT=char, _ ..\STLport-4.6.2\stlport\stdexcept(93) : '_STL::basic_string<_CharT,_Traits,_Alloc>' _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(93) : see reference to class template instantiation '_STL::basic_string<_CharT,_Traits,_Alloc>' being compor<char> ] ..\STLport-4.6.2\stlport\stdexcept(93) : see reference to cla with [ _CharT=char, ] ..\STLport-4.6.2\stlport\stdexcept(93) : see reference to class templat [ _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(85) : see reference to class template instantiation '_STL::basic_string<_CharT,_Traits,_Allc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(85) : see r compiled with [ 4.6.2\stlport\stdexcept(85) : see reference ttring<_CharT,_Traits,_Alloc>' being compiled char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(85) : see reference to class template instantiation '_STL::basic_string<_Cha _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexc [ _CharT=char, _ ..\STLport-4.6.2\stlport\stdexcept(85) : '_STL::basic_string<_CharT,_Traits,_Alloc>' _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] "cLINK=1 -DUSE_DATE_TIME_PRE_1_33_FACET_IO -D_STLP_DEBUG=1 -D_STLP_DEBUG_UNINITIALIZED=1 -D_STLP_USE_DYNAMIC_LIB=1 /Z7 /Od /Ob0 /EHsc /GR /MDd /Op /wd4675 /Zc:forScope -I"bin\boos_time\build\../src/gregorian/greg_month.cpp" ped <@boost!libs!date_time!build\boost_date_t of <@boost!libs!date_time!build\boost_date_tte_time!build\boost_date_time.dll\vc-7_1-stlpte_time!build\boost_date_time.dll\vc-7_1-stlp!date_time!build\boost_date_time.dll\vc-7_1-s!date_time!build\boost_date_time.dll\vc-7_1-schar_traits<wchar_t>> ] C:\ : see reference to function template instantrget,Source>::operator >><Target>(InputStream [ Target=boost::date_time::date_names_put<boost::gregorian::greg_facet_conf Source=NewSource, InputStreamable=boost::date_time::date_names_put_STL::ostreambuf_iterator<wchar_t,_STL::char_te_names_put.hpp(175) : see reference to func with [ Target=boost::date_time::date_names_put<boost::gregori>>::string_type, Config=boost::gregorian::greg_facet_config, charT=wchar_t, OutputIterator=_STL:s<wchar_t>>, Source=const wchar_ator>::iter_type &,const charT *const ) constchar_traits<wchar_t>> ] C:\put.hpp(212) : see reference to class templatL::char_traits<wchar_t>> ] src\gregorian\greg_month.cpp(147) : see refer ..\STLport-4.6.2\stlport\stdexcept(149) : see reference to class template instant _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(149) : seeSTL::basic_string<_CharT,_Traits,_Alloc>' bei _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(149) : see referencc_string<_CharT,_Traits,_Alloc>' being compilrT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(149) : see reference to clas_CharT,_Traits,_Alloc>' being compiled _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(149) : see reference to class templat [ _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(149) : see reference to class template instant _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(141) : seeSTL::basic_string<_CharT,_Traits,_Alloc>' bei _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(141) : see referencc_string<_CharT,_Traits,_Alloc>' being compilrT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(141) : see reference to clas_CharT,_Traits,_Alloc>' being compiled _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(141) : see reference to class templat [ _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(141) : see reference to class template instant _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(141) : seeSTL::basic_string<_CharT,_Traits,_Alloc>' bei _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(133) : see referencc_string<_CharT,_Traits,_Alloc>' being compilrT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(133) : see reference to clas_CharT,_Traits,_Alloc>' being compiled _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(133) : see reference to class templat [ _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(133) : see reference to class template instant _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(133) : seeSTL::basic_string<_CharT,_Traits,_Alloc>' bei _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(133) : see referencc_string<_CharT,_Traits,_Alloc>' being compilrT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(125) : see reference to clas_CharT,_Traits,_Alloc>' being compiled _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(125) : see reference to class templat [ _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(125) : see reference to class template instant _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(125) : seeSTL::basic_string<_CharT,_Traits,_Alloc>' bei _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(125) : see referencc_string<_CharT,_Traits,_Alloc>' being compilrT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(125) : see reference to clas_CharT,_Traits,_Alloc>' being compiled _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(117) : see reference to class templat [ _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(117) : see reference to class template instant _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(117) : seeSTL::basic_string<_CharT,_Traits,_Alloc>' bei _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(117) : see referencc_string<_CharT,_Traits,_Alloc>' being compilrT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(117) : see reference to clas_CharT,_Traits,_Alloc>' being compiled _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(117) : see reference to class templat [ _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(109) : see reference to class template instant _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(109) : seeSTL::basic_string<_CharT,_Traits,_Alloc>' bei _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(109) : see referencc_string<_CharT,_Traits,_Alloc>' being compilrT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(109) : see reference to clas_CharT,_Traits,_Alloc>' being compiled _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(109) : see reference to class templat [ _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(109) : see reference to class template instant _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(101) : seeSTL::basic_string<_CharT,_Traits,_Alloc>' bei _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(101) : see referencc_string<_CharT,_Traits,_Alloc>' being compilrT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(101) : see reference to clas_CharT,_Traits,_Alloc>' being compiled _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(101) : see reference to class templat [ _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(101) : see reference to class template instant _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(101) : seeSTL::basic_string<_CharT,_Traits,_Alloc>' bei _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(93) : see reference to class template instantiation '_STL::basicchar> ] ..\STLport-4.6.2\stlport\stdexcept(93) : see reference to class with [ _CharT=char, ] ..\STLport-4.6.2\stlport\stdexcept(93) : see reference to class template i [ _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(93) : see reference to class template instantiation '_STL::basic_string<_CharT,_Traits,_Alloc>STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(93) : see refempiled with [ .2\stlport\stdexcept(93) : see reference to cng<_CharT,_Traits,_Alloc>' being compiled r, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(85) : see reference to class template instantiation '_STL::basic_string<_CharT, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept[ _CharT=char, _Tra ..\STLport-4.6.2\stlport\stdexcept(85) : seeSTL::basic_string<_CharT,_Traits,_Alloc>' bei _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(85) : see reference to class template instantiation '_STL::basicchar> ] ..\STLport-4.6.2\stlport\stdexcept(85) : see reference to class with [ _CharT=char, ] ..\STLport-4.6.2\stlport\stdexcept(85) : see reference to class template i [ _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] EBUG -DNDEBUG -DBOOST_ALL_DYN_LINK=1 -DUSE_DATE_TIME_PRE_1_33_FACET_IO -D_STLP_USE_DYNAMIC_LIB=1 /Ogity /O2 /Gs /Ob2 /EHsc /GR /MD /Op\date_time\build\boost_date_time.dll\vc-7_1-soost_date_time.dll\vc-7_1-stlport\release\thrt_date_time-vc71-mt-p-1_33.CMD for lack of <@mt-p-1_33.CMD... ...skipped <@boost!libs!dat::string_type' (or there is no acceptable conputIterator=_STL::ostreambuf_iterator<wchar_t> ] C:\work\boost_1_33_0\boost\lexical_cast.hpp(221) : see reference to detail::lexical_stream<Target,Source>::operatled with [ Target=boost::date_time::date_names_put<boost::greambuf_iterator<wchar_t>>::string_type, Source=NewSource, Inpute ] C:\work\boost_1_33_0\boost\date_time\date_names_put.hpp(175) : see rTarget boost::lexical_cast<boost::date_time::date_names_put<Config,charT,OutputIterator>:: OutputIterator=_STL::ostreambuf1_33_0\boost\date_time\date_names_put.hpp(174Config,charT,OutputIterator>::put_string(boosputIterator=_STL::ostreambuf_iterator<wchar_t> ] C:\work\boost_1_33_0\boost\date_time\date_names_put.hpp(212) : see rst::date_time::date_names_put<Config,charT,Our_t, OutputIterator=_STL::ostreambuf_iterator<wchar_t> ] C: Config=boost::gregorian::greg_facet_config, charT=wchar_t ] ..\STLport-4.6.2\stlport\stdexcept(149\STLport-4.6.2\stlport\stdexcept(149) : see r compiled with [ 4.6.2\stlport\stdexcept(149) : see reference with [ _CharT<char>, _Alloc=_STL::allocator<cport\stdexcept(149) : see reference to class with [ _CharT=char, ] ..\STLport-4.6.2\stlport\stdexcept(149) : see reference to class template [ _CharT=char, ..\STLport-4.6.2\stlport\stdexcept(149\STLport-4.6.2\stlport\stdexcept(141) : see r compiled with [ 4.6.2\stlport\stdexcept(141) : see reference with [ _CharT<char>, _Alloc=_STL::allocator<cport\stdexcept(141) : see reference to class with [ _CharT=char, ] ..\STLport-4.6.2\stlport\stdexcept(141) : see reference to class template [ _CharT=char, ..\STLport-4.6.2\stlport\stdexcept(141\STLport-4.6.2\stlport\stdexcept(141) : see r compiled with [ 4.6.2\stlport\stdexcept(133) : see reference with [ _CharT<char>, _Alloc=_STL::allocator<cport\stdexcept(133) : see reference to class with [ _CharT=char, ] ..\STLport-4.6.2\stlport\stdexcept(133) : see reference to class template [ _CharT=char, ..\STLport-4.6.2\stlport\stdexcept(133\STLport-4.6.2\stlport\stdexcept(133) : see r compiled with [ 4.6.2\stlport\stdexcept(133) : see reference with [ _CharT<char>, _Alloc=_STL::allocator<cport\stdexcept(125) : see reference to class with [ _CharT=char, ] ..\STLport-4.6.2\stlport\stdexcept(125) : see reference to class template [ _CharT=char, ..\STLport-4.6.2\stlport\stdexcept(125\STLport-4.6.2\stlport\stdexcept(125) : see r compiled with [ 4.6.2\stlport\stdexcept(125) : see reference with [ _CharT<char>, _Alloc=_STL::allocator<cport\stdexcept(125) : see reference to class with [ _CharT=char, ] ..\STLport-4.6.2\stlport\stdexcept(117) : see reference to class template [ _CharT=char, ..\STLport-4.6.2\stlport\stdexcept(117\STLport-4.6.2\stlport\stdexcept(117) : see r compiled with [ 4.6.2\stlport\stdexcept(117) : see reference with [ _CharT<char>, _Alloc=_STL::allocator<cport\stdexcept(117) : see reference to class with [ _CharT=char, ] ..\STLport-4.6.2\stlport\stdexcept(117) : see reference to class template [ _CharT=char, ..\STLport-4.6.2\stlport\stdexcept(109\STLport-4.6.2\stlport\stdexcept(109) : see r compiled with [ 4.6.2\stlport\stdexcept(109) : see reference with [ _CharT<char>, _Alloc=_STL::allocator<cport\stdexcept(109) : see reference to class with [ _CharT=char, ] ..\STLport-4.6.2\stlport\stdexcept(109) : see reference to class template [ _CharT=char, ..\STLport-4.6.2\stlport\stdexcept(109\STLport-4.6.2\stlport\stdexcept(101) : see r compiled with [ 4.6.2\stlport\stdexcept(101) : see reference with [ _CharT<char>, _Alloc=_STL::allocator<cport\stdexcept(101) : see reference to class with [ _CharT=char, ] ..\STLport-4.6.2\stlport\stdexcept(101) : see reference to class template [ _CharT=char, ..\STLport-4.6.2\stlport\stdexcept(101\STLport-4.6.2\stlport\stdexcept(101) : see r compiled with [ 4.6.2\stlport\stdexcept(93) : see reference ttring<_CharT,_Traits,_Alloc>' being compiled char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(93) : see reference to class template instantiation '_STL::basic_string<_Cha _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexc [ _CharT=char, _ ..\STLport-4.6.2\stlport\stdexcept(93) : '_STL::basic_string<_CharT,_Traits,_Alloc>' _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(93) : see reference to class template instantiation '_STL::basic_string<_CharT,_Traits,_Alloc>' being compor<char> ] ..\STLport-4.6.2\stlport\stdexcept(93) : see reference to cla with [ _CharT=char, ] ..\STLport-4.6.2\stlport\stdexcept(85) : see reference to class templat [ _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(85) : see reference to class template instantiation '_STL::basic_string<_CharT,_Traits,_Allc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(85) : see r compiled with [ 4.6.2\stlport\stdexcept(85) : see reference ttring<_CharT,_Traits,_Alloc>' being compiled char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(85) : see reference to class template instantiation '_STL::basic_string<_Cha _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexc [ _CharT=char, _ "cl" /Zm800 -nologo /EHsc -c -DBOOST_DATE_TIME_STATIC_LINK -DUSE_DATE_TIME_PRE_1_33_FACET_IO -D_STLP_DEBUG=1 -D_STLP_DEBUG_UNte_time\build" -I"..\STLport-4.6.2\stlport" -1_33.CMD for lack of <@boost!libs!date_time!cpp C:\work\boost_1_33_0\boost\lexical_cast.ere is no acceptable conversion) witchar_t, OutputIterator=_STL::ost3_0\boost\lexical_cast.hpp(221) : see referenoost::detail::lexical_stream<Target,Source>:: compiled with [ Target=boost::date_time::date_names_put<boL::ostreambuf_iterator<wchar_t,_STL::char_trarce=NewSource, InputStreamable=b>>>::string_type ] C:\work\boost_1_33_0\boost\date_time\date_names_put.hpp(175) : see reference to function template st::date_time::date_names_put<Config,charT,Ou OutputIterator=_STL::ostreambuf_it C:\work\boost_1_33_0\boost\date_timte_time::date_names_put<Config,charT,OutputItchar_t, OutputIterator=_STL::ost3_0\boost\date_time\date_names_put.hpp(212) :n 'boost::date_time::date_names_put<Config,charT,OutputIterator>' being compiled T=wchar_t, OutputIterator=_STL:: with [ Config=boost::gregorian::greg_facet_config, charT=wchar_t ] ..\STLport-4.6.2\stlport\stdexcept(149) : see refempiled with [ .2\stlport\stdexcept(149) : see reference to with [ _CharT=ch> ] ..\STLport-4.6.2\stlport\stdexcept(149) : see reference to class temth [ _CharT=char, ] ..\STLport-4.6.2\stlport\stdexce [ _CharT=char, _ ..\STLport-4.6.2\stlport\stdexcept(149) :Lport-4.6.2\stlport\stdexcept(149) : see refempiled with [ .2\stlport\stdexcept(141) : see reference to with [ _CharT=ch> ] ..\STLport-4.6.2\stlport\stdexcept(141) : see reference to class temth [ _CharT=char, ] ..\STLport-4.6.2\stlport\stdexce [ _CharT=char, _ ..\STLport-4.6.2\stlport\stdexcept(141) :Lport-4.6.2\stlport\stdexcept(141) : see refempiled with [ .2\stlport\stdexcept(141) : see reference to with [ _CharT=ch> ] ..\STLport-4.6.2\stlport\stdexcept(133) : see reference to class temth [ _CharT=char, ] ..\STLport-4.6.2\stlport\stdexce [ _CharT=char, _ ..\STLport-4.6.2\stlport\stdexcept(133) :Lport-4.6.2\stlport\stdexcept(133) : see refempiled with [ .2\stlport\stdexcept(133) : see reference to with [ _CharT=ch> ] ..\STLport-4.6.2\stlport\stdexcept(133) : see reference to class temth [ _CharT=char, ] ..\STLport-4.6.2\stlport\stdexce [ _CharT=char, _ ..\STLport-4.6.2\stlport\stdexcept(125) :Lport-4.6.2\stlport\stdexcept(125) : see refempiled with [ .2\stlport\stdexcept(125) : see reference to with [ _CharT=ch> ] ..\STLport-4.6.2\stlport\stdexcept(125) : see reference to class temth [ _CharT=char, ] ..\STLport-4.6.2\stlport\stdexce [ _CharT=char, _ ..\STLport-4.6.2\stlport\stdexcept(117) :Lport-4.6.2\stlport\stdexcept(117) : see refempiled with [ .2\stlport\stdexcept(117) : see reference to with [ _CharT=ch> ] ..\STLport-4.6.2\stlport\stdexcept(117) : see reference to class temth [ _CharT=char, ] ..\STLport-4.6.2\stlport\stdexce [ _CharT=char, _ ..\STLport-4.6.2\stlport\stdexcept(117) :Lport-4.6.2\stlport\stdexcept(109) : see refempiled with [ .2\stlport\stdexcept(109) : see reference to with [ _CharT=ch> ] ..\STLport-4.6.2\stlport\stdexcept(109) : see reference to class temth [ _CharT=char, ] ..\STLport-4.6.2\stlport\stdexce [ _CharT=char, _ ..\STLport-4.6.2\stlport\stdexcept(109) :Lport-4.6.2\stlport\stdexcept(109) : see refempiled with [ .2\stlport\stdexcept(101) : see reference to with [ _CharT=ch> ] ..\STLport-4.6.2\stlport\stdexcept(101) : see reference to class temth [ _CharT=char, ] ..\STLport-4.6.2\stlport\stdexce [ _CharT=char, _ ..\STLport-4.6.2\stlport\stdexcept(101) :Lport-4.6.2\stlport\stdexcept(101) : see refempiled with [ .2\stlport\stdexcept(101) : see reference to with [ _CharT=ch> ] ..\STLport-4.6.2\stlport\stdexcept(93) : see reference to class temp,_Traits,_Alloc>' being compiled wit _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(93) : see reference to class template instantiation '_STL::basic_string<_CharT,_Traits,_lloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(93) : sert-4.6.2\stlport\stdexcept(93) : see referencc_string<_CharT,_Traits,_Alloc>' being compilrT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(93) : see reference to class template instantiation '_STL::basic_string<_ _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(93) : see reference to class template [ _CharT=char, ..\STLport-4.6.2\stlport\stdexcept(85) _CharT=char, _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(85) : see reference to class template instantiation '_STL::basic_string<_CharT,_Traits,_Alloc>' being ccator<char> ] ..\STLport-4.6.2\stlport\stdexcept(85) : see reference to with [ _CharT=ch> ] ..\STLport-4.6.2\stlport\stdexcept(85) : see reference to class temp,_Traits,_Alloc>' being compiled wit _Traits=_STL::char_traits<char>, _Alloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(85) : see reference to class template instantiation '_STL::basic_string<_CharT,_Traits,_lloc=_STL::allocator<char> ] ..\STLport-4.6.2\stlport\stdexcept(85) : se /Zm800 -nologo /EHsc -c -DBOOST_DATE_TIME_STATIC_LINK -DUSE_DATE_TIME_PRE_1_33_FACET_IO1 -D_STLP_USE_DYNAMIC_LIB=1 /Z7 /Od /Ob0 /EH_time.lib\vc-7_1-stlport\debug\threading-multp Terminate batch job (Y/N)?

2 1

any interest in lightweight version of boost::format
by Oliver Schoenborn 30 Oct '05

30 Oct '05

I know there is a boost::format and it's great. However, I needed something faster and with more "conventional" syntax. That's the coutf library. I've been using it for a few months and it's great. Just to be clear, I'm not suggesting a replacement of boost::format, which has several features that coutf does not. However in many cases you don't need those and that's why coutf is a fair bit faster. Also the syntax is more conventional and several people have mentioned they prefer that. I know Alexandrescu has also created something similar to coutf (I think he called it Printf), but I think mine is lighter, I think most people are not too concerned about not being able to printf 45 parameters, plus it has the Fmt/FmtGuard stuff :) . Anyways the docs and code are at http://noptrlib.sf.net/utils/coutf, just did another update today. Coutf could be a good second alternative to boost::format for some people. Here are some examples of use: coutf("Program started at %s:%s:%s\n", hours, minutes, seconds); cerrf("Error: file %s, line %5s invalid\n", filename, lineNum); std::string msg = strf("Hex of %s is %04Xs", 123, 123); int count = 10; std::ofstream ff("someFile.txt"); // prints array in hex format { FmtGuard fmt(ff, "%0#4x"); for (int i=0;i<count;i++) scoutf( ff, 1 + intArray[i], '\n' ); } // print in dec format scoutf( ff, count ); BOOST_LOG(trace) << strf("File %s at line %s\n", __FILE__, __LINE__); Cheers, Oliver

5 5

64-bit Boost Regression testing.
by Nik Yevik 28 Oct '05

28 Oct '05

Hi, I have built 64-bit Boost libraries on SUSE Linux ES 9 (SLES 9)for IBM POWER/PowerPC(PPC) using gcc 3.3.3 and 3.4.4. in both 32-bit and 64-bit. Now, I also want to run Boost 1.33.0 regresion test with gcc 3.4.4 in 64-bit to see if there are any problems with 64-bit compilation. Regression test helper programs and tests themselves are being built in 64-bit OK. However, the run tests give the error message: ***************************************************** unknown location(0): fatal error in "some_test_name": signal: memory access violation *** errors detected in test suite "Some Test Suite Name"; see standard output for details EXIT STATUS: 200 ***************************************************** I enabled detailed output and here is an example of what I see during the regression test (Just one orbitrary chosen test - the rest show pretty much the same picture).: ****************************************************** MkDir1 ../bin/boost/libs/assign/test/multi_index_container.test mkdir "../bin/boost/libs/assign/test/multi_index_container.test" MkDir1 ../bin/boost/libs/assign/test/multi_index_container.test/gcc mkdir "../bin/boost/libs/assign/test/multi_index_container.test/gcc" MkDir1 ../bin/boost/libs/assign/test/multi_index_container.test/gcc/debug mkdir "../bin/boost/libs/assign/test/multi_index_container.test/gcc/debug" MkDir1 ../bin/boost/libs/assign/test/multi_index_container.test/gcc/debug/address-model-64 mkdir "../bin/boost/libs/assign/test/multi_index_container.test/gcc/debug/address-model-64" MkDir1 ../bin/boost/libs/assign/test/multi_index_container.test/gcc/debug/address-model-64/architecture-power mkdir "../bin/boost/libs/assign/test/multi_index_container.test/gcc/debug/address-model-64/architecture-power" gcc-C++-action ../bin/boost/libs/assign/test/multi_index_container.test/gcc/debug/address-model-64/architecture-power/multi_index_container.o set -e "/home/nik/gcc-3.4.4-ppc-install/bin/g++" -m64 -c -Wall -ftemplate-depth-255 -g -O0 -fno-inline -mcpu=powerpc64 -m64 -I"../bin/boost/libs/assign/test" -I"/home/nik/boost_1_33_0" -I "/home/nik/boost_1_33_0" -o "../bin/boost/libs/assign/test/multi_index_container.test/gcc/debug/address-model-64/architecture-power/multi_index_container.o" "../libs/assign/test/multi_index_container.cpp" "/usr/bin/objcopy" --set-section-flags .debug_str=contents,debug "../bin/boost/libs/assign/test/multi_index_container.test/gcc/debug/address-model-64/architecture-power/multi_index_container.o" gcc-Link-action ../bin/boost/libs/assign/test/multi_index_container.test/gcc/debug/address-model-64/architecture-power/multi_index_container set -e LD_LIBRARY_PATH=/home/nik/gcc-3.4.4-ppc-install/lib64:/home/nik/gcc-3.4.4-ppc-install/lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH "/home/nik/gcc-3.4.4-ppc-install/bin/g++" -m64 -g -m64 -o "../bin/boost/libs/assign/test/multi_index_container.test/gcc/debug/address-model-64/architecture-power/multi_index_container" -L"/home/nik/gcc-3.4.4-ppc-install/lib64" -L"../bin/boost/libs/test/build/libboost_unit_test_framework.a/gcc/debug/address-model-64/architecture-power" -L"/home/nik/gcc-3.4.4-ppc-install/lib" "../bin/boost/libs/assign/test/multi_index_container.test/gcc/debug/address-model-64/architecture-power/multi_index_container.o" "../bin/boost/libs/test/build/libboost_unit_test_framework.a/gcc/debug/address-model-64/architecture-power/libboost_unit_test_framework.a" "../bin/boost/libs/test/build/libboost_unit_test_framework.a/gcc/debug/address-model-64/architecture-power/libboost_unit_test_framework.a" -Wl,-rpath-link,. Chmod1 ../bin/boost/libs/assign/test/multi_index_container.test/gcc/debug/address-model-64/architecture-power/multi_index_container chmod 711 "../bin/boost/libs/assign/test/multi_index_container.test/gcc/debug/address-model-64/architecture-power/multi_index_container" execute-test ../bin/boost/libs/assign/test/multi_index_container.test/gcc/debug/address-model-64/architecture-power/multi_index_container.run LD_LIBRARY_PATH=/home/nik/gcc-3.4.4-ppc-install/lib64:/home/nik/gcc-3.4.4-ppc-install/lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH PATH=/home/nik/gcc-3.4.4-ppc-install/lib64:$PATH export PATH ../bin/boost/libs/assign/test/multi_index_container.test/gcc/debug/address-model-64/architecture-power/multi_index_container > ../bin/boost/libs/assign/test/multi_index_container.test/gcc/debug/address-model-64/architecture-power/multi_index_container.output 2>&1 status=$? echo >> ../bin/boost/libs/assign/test/multi_index_container.test/gcc/debug/address-model-64/architecture-power/multi_index_container.output echo EXIT STATUS: $status >> ../bin/boost/libs/assign/test/multi_index_container.test/gcc/debug/address-model-64/architecture-power/multi_index_container.output if test $status -eq 0 ; then cp -f ../bin/boost/libs/assign/test/multi_index_container.test/gcc/debug/address-model-64/architecture-power/multi_index_container.output ../bin/boost/libs/assign/test/multi_index_container.test/gcc/debug/address-model-64/architecture-power/multi_index_container.run fi verbose=1 if test $status -ne 0 ; then verbose=0 fi if test $verbose -eq 0 ; then echo ====== BEGIN OUTPUT ====== cat ../bin/boost/libs/assign/test/multi_index_container.test/gcc/debug/address-model-64/architecture-power/multi_index_container.output echo ====== END OUTPUT ====== fi exit $status ====== BEGIN OUTPUT ====== Running 1 test case... unknown location(0): fatal error in "test_multi_index_container": signal: memory access violation *** errors detected in test suite "List Test Suite"; see standard output for details EXIT STATUS: 200 ====== END OUTPUT ====== ****************************************************** Indeed, trying to execute the 64-bit executable in gdb gives something like: Error accessing memory address 0x53e00001b5a6: Input/output error. (gdb) where #0 0x000053e00000d932 in ?? () #1 0x0000000000000000 in ?? () Previous frame identical to this frame (corrupt stack?) I modified slightly the run-tests.sh script and gcc-tools.jam to regression test in 64-bit. RUN_TESTS.SH: diff run_tests.sh.orig run_tests.sh 18c18 < boost_root="$HOME/CVSROOTs/Boost/boost_regression" --- > boost_root="/home/nik/boost_1_33_0" 134a135 > export LD_LIBRARY_PATH="/home/nik/gcc-3.4.4-ppc-install/lib64" 136c137 < "$bjam" -sTOOLS=$toolset -sBUILD=release run --- > "$bjam" -a -d+2 -sTOOLS=$toolset -sBUILD=release run "-sBUILD=<architecture>power <address-model>64 <library-path>/home/nik/gcc-3.4.4-ppc-install/lib64" 152a154 > export LD_LIBRARY_PATH="/home/nik/gcc-3.4.4-ppc-install/lib64" 154c156 < "$bjam" -sTOOLS=$tool --dump-tests test 2>&1 | tee regress.log --- > "$bjam" -a -d+2 -sTOOLS=$tool "-sBUILD=<architecture>power <address-model>64 <library-path>/home/nik/gcc-3.4.4-ppc-install/lib64" --dump-tests test 2>&1 | tee regress.log GCC_TOOLS.JAM - added two lines: > flags gcc CFLAGS <architecture>power/<address-model>64 : -m64 ; > flags gcc LINKFLAGS <architecture>power/<address-model>64 : -m64 ; What am I missing here? What am I doing wrong? Any help would be greatly appreciated. __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

1 0

[date_time] is it possible to parse a string out from given patterns?
by Roman Morokutti 28 Oct '05

28 Oct '05

Is it possible to parse a date out from a string like this? The example below is from a java program. private static final String PLANSTART_PATTERN = "dd.MM.yyyy HH:mm"; /** * Converts a String of type 01.01.2005 to a * CDate object * @param sForcamDate * @return the converted object */ private CDate convertToCDate(String sForcamDate, String sPattern) { if (sForcamDate == null || sForcamDate.length() == 0) return null; try { SimpleDateFormat sdf = new SimpleDateFormat(sPattern, Locale.getDefault()); sdf.parse(sForcamDate); Calendar cal = sdf.getCalendar(); return new CDate(cal.getTime()); } catch (ParseException ex) { return null; } } For more information on SimpleDateFormat see: http://java.sun.com/j2se/1.4.2/docs/api/java/text/SimpleDateFormat.html

4 6

A basic interior properties question
by Gat, Yoram 28 Oct '05

28 Oct '05

Hi all, I just started using BGL and created the following program (MSVS 7.1), storing some data in an interior property and then retrieving them: #include "boost/graph/adjacency_list.hpp" struct NodeProperties { int a, b, c; }; typedef boost::adjacency_list< boost::listS,boost::listS,boost::undirectedS, boost::property<boost::vertex_all_t,NodeProperties> > Graph; typedef boost::graph_traits<Graph>::vertex_descriptor VertexDescriptor; typedef boost::property_map<Graph,boost::vertex_all_t>::type AllMap; int main(int argc, char const *argv[]) { Graph graph; AllMap allMap = get(boost::vertex_all,graph); VertexDescriptor vd = boost::add_vertex(graph); NodeProperties np; np.a = 1; np.b = 2; np.c = 3; allMap[vd] = np; NodeProperties np1 = allMap[vd]; // const AllMap::value_type &vt = boost::get(allMap,vd); // NodeProperties np1 = vt.m_value; return 0; } For which I get the following error: c:\Documents and Settings\ygat\Desktop\Work\InternalProperty\InternalProperty.cpp(24): error C2440: 'initializing' : cannot convert from 'boost::detail::vertex_property_map<Graph,PropertyTag>::Property' to 'NodeProperties' with [ Graph=Graph, PropertyTag=boost::vertex_all_t ] After some poking around, I discovered that if I replace the offending line with the two commented lines, things work. Is this the right way to retrieve the data? Why can the NodeProperties object be on the rhs but not on the lhs of an assignment to the property map? Thanks, Yoram

1 0

[multi_index] non-intrusive keys
by Adi Shavit 28 Oct '05

28 Oct '05

Hi, In my application I used a multi_map of multi_maps as a data structure to provide indexing with 2 keys, say long strings. Access is logarithmic on both keys and the keys are not part of the stored object, thus are potentially only stored once. I'd like to use multi_index as a more elegant replacement. However, I'm not clear about where the keys are stored. In my app, the keys are stored separately from the data, as the keys to maps, as part of the map data structure. It seems that in multi_index the keys have to be inside the stored data. In this case, 10 objects with the same key(s) will all have to hold copies of the keys (as members). Is there a way to avoid this? I hope I'm clear, Thanks, Adi

1 0

singleton in boost::library?
by Oliver.Kowalke＠infineon.com 28 Oct '05

28 Oct '05

Hello, why no singleton-template is available in boost?

3 2

Boost T-Shirts @ Cafe Press
by Jeff Garland 28 Oct '05

28 Oct '05

Hi All - As everyone is probably already aware, we have a new Boost logo that was created by booster Zoltan 'cad' Juhasz. As part of the final logo refinement process, the moderators asked Zoltan if he could create T-Shirts with the new logo. We also felt it was appropriate that Zoltan be the beneficiary of any proceeds associated with the T-Shirts since it was his tireless work that went into the logo and T-Shirt design. With that in mind, I'm delighted to announce that Zoltan worked out some T-Shirt designs and has set up a couple shops at Cafe Press so that people can purchase Boost T-Shirts. - http://www.cafepress.com/boostlibs - http://www.cafepress.com/boostlibsb If you have suggestions or other ideas you can find Zoltan's contact info at: http://people.inf.elte.hu/cad Jeff

1 0