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

Re: [Boost-users] [bind] Help with functional compositionofshared_ptr::use_count in std::map
by Küppers, Ben 11 Jun '07

11 Jun '07

> map<string, shared_ptr<data> > Fred; > > RemoveIf(Fred.begin(), > Fred.end(), > boost::bind(&map<string, shared_ptr<data> > >::value_type::second::unique, _1) > ) James, remove_if requires an assignment operator on the operated type but the value_type of a map is defined as std::pair< const T1, T2 >. The const on the first type will cause any assignment to fail. In other words, you can't use remove_if on a map. That said, in order to fix your bind you would need two functors. The type passed to the bind is the value_type of the map which is by definition a pair. You need to first invoke a functor on the pair to extract the second member and then call the member unique on the resulting smart pointer. In order to do so you'll need to write your own extractor, because the STL does not provide a functor to obtain the "second" field from a pair (I haven't found one in boost either). template< class Pair > struct second_of : std::unary_function< Pair, typename Pair:second_type > { typename Pair::second_type opertator()( const Pair& the_pair ) const { return the_pair.second; } }; std::for_each( Fred.begin(), Fred.end(), boost::bind( boost::shared_ptr< data >::unique, boost::bind( second_of< std::map< std::string, boost::shared_ptr< data > >::value_type >(), _1 ) ) ); Note that you can call for_each as it does not require the assignment operator. Hope this helps, Ben This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

2 1

Problems with boost.thread
by luca regini 11 Jun '07

11 Jun '07

I have some problems with boost.thread (version 1_34) under gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-52). The library ( all the boost distribution) compiles fine and a bjam on the ./libs/thread/test directory also report a successful test execution. However when i try to explicitly link one of the example (tread_group with the boost tread library using the following command line: g++ -I/opt/six/boost_1_33_1 -I/opt/six/boost_1_34/include/boost-1_34 -pthread -o mytest thread_group.cpp libboost_thread-gcc32-mt-d-1_34.so.1.34.0 i get a segmentation fault. >From a core dump i can see the following stacktrace: 0 0x008e78fb in boost::function0<void, std::allocator<boost::function_base> >::assign_to_own (this=0xb75e5420, f=@0xbfffacb0) at ../../../boost/function/function_template.hpp:647 647 f.vtable->manager(f.functor, this->functor, (gdb) backtrace #0 0x008e78fb in boost::function0<void, std::allocator<boost::function_base> >::assign_to_own (this=0xb75e5420, f=@0xbfffacb0) at ../../../boost/function/function_template.hpp:647 #1 0x008e748f in function0 (this=0xb75e5420, f=@0xbfffacb0) at ../../../boost/function/function_template.hpp:527 #2 0x008e6748 in thread_proxy (param=0xbfffac20) at ../../../libs/thread/src/thread.cpp:106 #3 0x0040f371 in start_thread () from /lib/tls/libpthread.so.0 #4 0x001d8ffe in clone () from /lib/tls/libc.so.6 Where is the problem?? Thanks in advance, Luca Regini

2 2

Question about boost mutex
by Meryl Silverburgh 11 Jun '07

11 Jun '07

Hi, I have a application which uses p_thread for creating threads, can i use the boost mutex classes for thread synchronization? Or the boost mutex class only works with boost thread class? Thank you.

2 1

[program options] & also an apology to the list...
by jono 10 Jun '07

10 Jun '07

...for my earlier grumpy email about program_options. i'm was wanting to pass some sequences to some options using boost::program_options. something like: [me@here ~]$program --opt1 1 2 3 4 --opt2 5 6 7 8 --opt3 xxx yyy zzz if i use desc.add_options("opt1", value< vector<string> >()->multitoken(), "...") i get all the tokens to the end of the line. can i make multitoken() stop eating tokens by recognizing a syntactic element; either an option specifier or a token it can't interpret as a required type? can i inherit from the value_semantic class to read multiple tokens maybe? this whole library is very interesting but subtle. i do better when i can read examples of working code. does anyone know a more extensive discussion of it besides the distibution docs? ...which are great by the way! cheers jono

2 1

Problem with boost::program_options
by Jonas Bösch 10 Jun '07

10 Jun '07

Hi, I'm having a problem with boost::program_options. I attached a stripped-down version of the code that demonstrates the problem. I have a number of positional arguments ( "ops" ), and one normal argument ( "input-file,i" ). Now, if i run the program ./op_test pos0 pos1 pos2 -i non_positional it interpretes the "non_positional" as further positional arg, and not as parameter belonging to -i. Any hints on how to solve this are greatly appreciated. I ran it on: Mac OS X 10.4 on a G5, with the latest XCode ( gcc 4.0.1 ) boost 1.34 Jonas

3 3

BGL: INTERNAL COMPILER ERROR in VC7.1
by Yariv Tal 10 Jun '07

10 Jun '07

This one was already posted by Nicholas Burlett awhile back (see http://lists.boost.org/MailArchives/boost-users/msg06534.php) but I have some new info that may help. The problem: ========= When compiling code that uses the boost.graph library the VC7.1 compiler shouts: c:\boost_1_32_0\boost\mpl\aux_\preprocessed\plain\apply_wrap.hpp(48) : fatal error C1001: INTERNAL COMPILER ERROR As Nicholas already noted, this seems to be due to some compiler problem with the boost.graph out_edge_iterators since it is caused by the following lines in my code: (FilteredGraphGenerator::FilteredGraph is a typedef of a boost::filtered_graph) typedef boost::graph_traits<FilteredGraphGenerator::FilteredGraph> ::out_edge_iterator oedge_iterator; oedge_iterator edgesItr, edgesEnd; boost::tie(edgesItr, edgesEnd) = boost::out_edges(itr->first, m_g.m_filteredGraph); while (edgesItr != edgesEnd) { // do anything! } In fact, it seems to be related to the operator!= between iterators (if the while loop is commented out it compiles). How ever, the error persists even after changing the operator!= to operator== : while (edgesItr == edgesEnd) { // do anything! } ========================================================================== Some findings: =========== * We used to use boost_1_30_0 and the code used to compile PERFECTLY. The problem only appeared after migrating to boost_1_32_0. * Calling directly to the "equal" function in iterator_core_access instead of the operator== works. typedef boost::graph_traits<FilteredGraphGenerator::FilteredGraph> ::out_edge_iterator oedge_iterator; oedge_iterator edgesItr, edgesEnd; boost::tie(edgesItr, edgesEnd) = boost::out_edges(itr->first,m_g.m_filteredGraph); while (boost::iterator_core_access::equal(edgesItr, edgesEnd, boost::mpl::true_())) { // do somthing } * The error message location is at the mpl::apply_wrap2 function. Any relation to the mpl::apply2 function used for declaring the operator== in the BOOST_ITERATOR_FACADE_INTEROP_HEAD macro? Have these functions changed since v1.30.0?

9 8

Problem with ProgramOptions
by Jonas Boesch 10 Jun '07

10 Jun '07

Hi, I'm having a problem with boost::program_options. I attached a stripped-down version of the code that demonstrates the problem. I have a number of positional arguments ( "ops" ), and one normal argument ( "input-file,i" ). Now, if i run the program ./op_test pos0 pos1 pos2 -i non_positional it interpretes the "non_positional" as further positional arg, and not as parameter belonging to -i. Any hints on how to solve this are greatly appreciated. My machine: Mac OS X 10.4 ppc ( G5 ) XCode 2.4.1 ( gcc 4.0.1 ) boost 1.34 Greetings, Jonas The code: // ------------------------ options.h ------------------- #ifndef __VMML__OPTIONS__H__ #define __VMML__OPTIONS__H__ #include <boost/program_options.hpp> #include<map> namespace vmml { namespace boost_po = ::boost::program_options; typedef ::boost::program_options::variables_map var_map; class options { public: options(); void setup( int argc, char* argv[] ); void get_operator_chain( std::vector< std::string >& op_chain ); protected: // generic options boost_po::options_description _generic_options; // op chain boost_po::options_description _all_options; std::map< std::string, boost_po::options_description* > _op_descs; // positional options boost_po::positional_options_description _positional_desc; boost_po::variables_map _options_map; std::vector< std::vector< std::string > > _op_cfgs_from_file; };//class options };//namespace vmml #endif // --------- options.cpp -------------------------------- #include "options.h" #include <iostream> #include <vector> #include <string> namespace vmml { options::options() : _generic_options( "Generic options" ) { _generic_options.add_options() ("input-file,i", "specify input file") ("ops,O", boost_po::value< std::vector< std::string > >()- >composing(), "specify operators " ) ; _positional_desc.add( "ops", -1 ); } void options::setup( int argc, char* argv[] ) { _all_options.add( _generic_options ); boost_po::store( boost_po::command_line_parser( argc, argv ) .options( _all_options ) .positional( _positional_desc ) //.allow_unregistered() .run(), _options_map ); boost_po::notify( _options_map ); } void options::get_operator_chain( std::vector< std::string >& op_chain ) { if ( _options_map.count("ops") ) { const std::vector< std::string >& ops = _options_map["ops"].as< std::vector< std::string > >(); op_chain = ops; } } }//namespace vmml int main( int argc, char** argv ) { vmml::options opt; opt.setup( argc, argv ); std::vector< std::string > ops; opt.get_operator_chain( ops ); std::vector< std::string >::iterator it = ops.begin(); std::vector< std::string >::iterator itend = ops.end(); for( ; it != itend; ++it ) { std::cout << *it << std::endl; } }

1 0

[boost.python] is it possible to make python::dict wrap an existing python dictionary object instead of making a copy?
by Marcin Kalicinski 10 Jun '07

10 Jun '07

python::dict m_mainNamespace = python::dict(m_mainModule.attr("__dict__")); The above code makes a copy of mainModule dictionary. Is it possible to make m_mainNamespace not a copy but a reference to mainModule dictionary? Marcin

2 1

Failing with "Getting Started on Windows" program
by Robert Murphy 10 Jun '07

10 Jun '07

Hello, Following instructions on the "Getting Started on Windows" page, I installed boost using the BoostPro 1.34.0 Installer on XP Pro. I included the Boost.Regex binaries as directed, too. I'm running VS C++ 2005 Express. SDK is not installed. All directories are linked to as instructed to do so in the properties window. I tried building the 2nd program: e-mail checker one. However I get "LINK : fatal error LNK1104: cannot open file 'user32.lib'" as an error. 'user32.lib' is in the SDK My questions are: 1. Must I have the SDK installed to use boost for general unit testing of code I personally generate? 2. Do I have to have the SDK installed for the above program to run? Thank you. _________________________________________________________________ Dont miss your chance to WIN $10,000 and other great prizes from Microsoft Office Live http://clk.atdmt.com/MRT/go/aub0540003042mrt/direct/01/

2 1

posting
by Jan Stetka 10 Jun '07

10 Jun '07

There is a spam issue. Each time I post to the list I get a reply: Delivered-To: jan.stetka(a)gmail.com Received: by 10.143.43.6 with SMTP id v6cs257677wfj; Sat, 9 Jun 2007 12:47:33 -0700 (PDT) Received: by 10.35.8.1 with SMTP id l1mr6177223pyi.1181418453286; Sat, 09 Jun 2007 12:47:33 -0700 (PDT) Received-SPF: fail X-Gmail-Fetch-Info: 485309469254 1 pop.tiscali.co.uk 110 janpstetka(a)tiscali.co.uk Return-Path: <postmaster(a)sina.com> Received: from r3-111.sinamail.sina.com.cn (202.108.3.111) by mail-11.uk.tiscali.com (7.3.110.8) id 4669D52F00718B6F for janpstetka(a)tiscali.co.uk; Sat, 9 Jun 2007 20:52:04 +0200 Received: (qmail 18402 invoked by uid 99); 9 Jun 2007 18:51:56 -0000 Date: 9 Jun 2007 18:51:56 -0000 Message-ID: <20070609185156.18401.qmail(a)mail3-111.sinamail.sina.com.cn> From: <postmaster(a)sina.com> To: <janpstetka(a)tiscali.co.uk> Subject: =?gbk?B?Ym9vc3QtdXNlcnNAc2luYS5jb221xNfUtq+72Li0?= MIME_version: 1.0 Content-type: text/plain; charset=gbk; format=flowed Content-transfer-encoding: 8BIT Your message received. Thank you. -- =================================================================== ע��2G��䣨 http://mail.sina.com.cn/chooseMode.html ��

2 1

interprocess
by Jan Stetka 09 Jun '07

09 Jun '07

Hi, Interprocess still has not been included in the documentation on the main site yet, wouldn't it be good to include it there as soon as possible as it would increase the usage of interprocess. The "quick guide for the impatient" on maps is very good and a welcome addition to the documentation. The documentation at http://ice.prohosting.com/newfunk/ boost/libs/interprocess/doc/html/interprocess/quick_guide.html #interprocess.quick_guide.qg_interprocess_map reads "Boost.Interprocess's map is The construction of map is a bit tricky, because" which could be an editing or typing mistake as it doesn't currently make much sense. Thanks

1 0

Non-trivial examples of Boost::Interprocess library usage
by Evan Torrie 09 Jun '07

09 Jun '07

Hi I'm new to Boost, and also new to Boost::Interprocess. I've been reading through the documentation for Boost::Interprocess, and have successfully written an application which creates a tree like structure in a managed_memory_mapped_file; saves it to disk, and then other processes can reopen that mmap'ed file and traverse the tree. However, I feel like I really am not making the best use of the library, and would like to get more experience by reading other example code from significant applications Does anyone have source code of a non-trivial application that exercises shared memory or memory-mapped files, storing objects with pointers to other objects (and strings) into the shared memory, deleting, updating, retrieving them etc. Specifically, say I'm trying to port an existing heap-based structure into shared memory. struct foo { int x, y; std::vector< std::string > keys; struct foo* left, right; } struct foo* root; What would this translate to in the boost::interprocess world? Is it possible to write templatized versions of these data structures that would work either with the existing std::allocator heap-based memory or with boost::interprocess stateful allocators without needing to create two versions of this data structure? One problem I've encountered is that default constructors for boost::interprocess::vector/string etc are not possible since they need to be constructed with a stateful allocator... so, does this mean that any constructor for object foo requires an allocator to be passed in which is then used in the initializer list to initialize these member containers? Sorry if this doesn't make sense - but any help would be appreciated. Thanks Evan. ----------------------------------------- E> evan.torrie(a)yahoo.com

3 2

Does Boost include SHA-1 implementation?
by Bo Xie 09 Jun '07

09 Jun '07

I know I can call openSSL(or its libcrypto) for SHA-1. But how about Windows? (I can not redistribute openSSL windows version.) My question is: Does Boost include SHA-1 implementation? Thanks! -Bo

3 2

boostcon slides online
by Ares Lagae 08 Jun '07

08 Jun '07

One of the previous posts in this list made me wondering. Wouldn't it be nice to have the slides from the boostcon talks online? Best regards, -- Ares Lagae Computer Graphics Research Group, Katholieke Universiteit Leuven http://www.cs.kuleuven.be/~ares/

2 1

[integer] Request: long long (64 bits) support for int_t and uint_t
by Niels Dekker - mail address until 2007-11-30 08 Jun '07

08 Jun '07

I would like to have "long long" and "unsigned long long" supported by boost::int_t and boost::uint_t. E.g., on Win32, VC++, I would expect int_t<64>::least to get me a long long. Are there plans to add this kind of support? Otherwise, should I submit my request as a ticket to svn.boost.org/trac/boost ? It looks like "long long" support can be added quite easily, as I already did so on my local copy of boost/integer.hpp. -- Niels Dekker http://www.xs4all.nl/~nd/dekkerware Scientific programmer at LKEB, Leiden University Medical Center

5 12

boost::bind as composite
by Boris 08 Jun '07

08 Jun '07

Hi, I have two predicates f1 and f2 and I want to construct the predicate f4 = f1 && f2 using boost::bind. Unfortunately I observe a strange behaviour of boost::bind I can not explain. struct Test { int a; int b; }; Test t = { 1, 2 }; typedef boost::function< bool (Test const&) > Fn; Fn f1 = bind( &Test::a, _1 ) == 1; assert (f1( t )); // Ok Fn f2 = bind( &Test::b, _1 ) == 3; assert (!f2( t )); // ok Fn f3 = bind( std::logical_and< bool >(), bind( &Test::a, _1 ) == 1, bind( &Test::b, _1 ) == 3 ); assert (!f3( t )); // Ok Fn f4 = bind( std::logical_and< bool >(), f1, f2 ); assert (!f4( t )); // assertion failed Why does the predicate f4 behave different from f3? Thanks, Boris

2 1

[parameter] A few usage questions
by John Maddock 08 Jun '07

08 Jun '07

I have a few usage questions for the Boost.Parameter library: 1) If I want to have a function called "policy" that's declared using BOOST_PARAMETER_FUNCTION can I access the types of the arguments both from within the functions body and for the functions return type: BOOST_PARAMETER_FUNCTION( (return-type-computed-from-arguments), policy, tag, // 3. namespace of tag types (optional // optional parameters, with defaults (domain_error, *, throw_on_error) ) (deduced (optional (precision, *, boost::mpl::int_<53>()) ) ) ) { // what type are the arguments? } I realise I can do this with an argument pack, but then either my users will have to call the function with an extra set of parenthesis, or I will have to write a bunch of forwarding functions myself - which itself generates a "what the is the return type" problem. >From within the body of the BOOST_PARAMETER_FUNCTION generated function it appears that I can use the name "Args" to refer to the type of the argument pack, and maybe in the return type as well? But this isn't documented, so can I rely on it? 2) All the arguments I want to pass are actually going to end up being used in meta-programs: for symbolic values, I can make each one a unique enum type, and use the type of the argument (even though it's actually passed as a value) to generate my metacode. But I have one optional argument where I require the value to be an arbitrary compile time constant, the only interface I can come up with at present is something like: policy(_digits10 = mpl::int_<10>()); But I'd really like to be able to write: policy(_digits10 = 12); and have the "12" converted to mpl::int_<12> "by magic", but I can't think of any magic that could be applied here... anyone any ideas? Thanks, John.

2 3

[boost::variant] does 'incomplete<T>' still exist?
by jono 08 Jun '07

08 Jun '07

hi. i read a tutorial at http://electra.lbl.gov/stuff/variant/doc/tutorial.html which says a boost::variant type can be declared with an incomplete type in its typelist by using incomplete<T>. i'm using boost 1.33.1 & i can't find incomplete<T> anywhere. does it still exist? the tutorial is dated '14 February 2003'. can variants use incomplete types? i want to have a variant represent a type which has a variant member. can i do that? i'm working on a kind of envelope/letter idiom for dispatching operations on values. cheers jono

1 0

Re: [Boost-users] port of GameDev SDL lib in Boost?
by Christian Henning 08 Jun '07

08 Jun '07

Hi there, I think there is something wrong with the timer. Whenever I run the code ( see below ) it slows down for whatever reason. Is that a known problem? When I look at the output the frequency is certainly not 10 times a second. #include <windows.h> #include <iostream> #include <sdl.h> using namespace std; Uint32 time_elapsed( Uint32 interval, void* param ) { cout << interval << endl; return ++interval; } int main( int argc, char* argv[] ) { SDL_Init( SDL_INIT_VIDEO | SDL_INIT_TIMER ); SDL_TimerID id = SDL_AddTimer( 100, &time_elapsed, NULL ); SDL_Event event; while( SDL_PollEvent( &event ) >= 0 ) { ::Sleep( 100 ); } return 0; }

2 1

[signal] Invoking connect with same argument a second time allowed?
by Boris 08 Jun '07

08 Jun '07

Is it allowed to call connect() with the same argument (slot) a second time (without disconnecting in between)? I've been checking the documentation at http://www.boost.org/doc/html/boost/signalN.html#id1033842-bb but couldn't find any answer. I assume it is allowed (it doesn't throw any exception et al.) but don't want to build a software based on assumptions really. ;-) Boris

2 3

wave: preprocessing Visual C++ 2005 stl
by Ludovic Aubert 07 Jun '07

07 Jun '07

Hello boost wave users, I have written a sample program which uses boost wave and I am trying to run it on its own source code. The environnement (especially the stl) is Microsoft Visual C++ 2005. Since typically an include file like "vector" will be preprocessed many times (once for every compilation unit), I am saving all the preprocessed tokens in a map<string, map<tuple<int,int>,string> > token, so that token[path][make_tuple(line,col)] = value. Then for each path I am using a forward iterator to spit out all the values into a buffer. The major trouble I have is with the macros #define STD_BEGIN namespace std { #define STD_END } defined in the file "yvals.h" Somehow, STD_BEGIN and STD_END are replaced by blanks and I get "namespace std{}" at the end of the files instead. Looks like the line and col for these items are wrong ... I would like to know if someone has already successfully preprocessed the stl delivered with Visual C++ 2005. Thank you in advance for your reply Ludovic Aubert

2 5

Filesystem Exception
by Surya Kiran Gullapalli 07 Jun '07

07 Jun '07

Hello all, I'm creating a directory using boost::filesystem::create_directory function. When i looked at the documentation, It said, Throws: basic_filesystem_error<Path> if Effects fails for any reason other than because the directory already exists. Now when i catch the exception like this try { boost::filesystem::create_directory (path) } catch (boost::filesystem::basic_filesystem_error <boost::filesystem::path>& e) { cout << e.what() << endl ; } e.what() returns the string boost::filesystem::create_directory. What i expect is why the create_directory failed. How can i get the string describing the problem. Thanks in advance, Surya

2 1

Re: [Boost-users] port of GameDev SDL lib in Boost?
by Christian Henning 07 Jun '07

07 Jun '07

My current version is more or less ready to use. you can check it here: http://gil-contributions.googlecode.com/svn/trunk/gil_2/boost/gil/extension… Let me know what you think. I'm not so sure if you can put your callback timer under the boost license. Maybe somebody else knows the answer. Christian On 6/6/07, fanzhe cui <fanzhe.cui(a)goldiom.com> wrote: > Christian, > > Boost is very widely accepted and utilized by game developers, and on the > web GameDev.net there are many many articles about various boost sub lib. > But I haven't seen many discussions about SDL lib on this boost mail list > from boost users/developers. SDL is very convenient cross-platform C++ > development platform that can be used not only game developers but also by > other developers. It has easy-to-use classes of multithreads, mutex, event > queues, timer callbacks, semaphores, key board input handling, audio, video, > to name a few. Most of these functionalities are available from Boost lib. > But I haven't seen good timer callback available from Boost lib (anybody can > correct me if I am not so informed of Boost timer). > > I tried to extract the timer functions (classes) from the SDL lib into an > individual timer lib, and the work is still in progress. I am not sure other > users in the list are interested in knowing about porting SDL timer to > Boost. So if you can tell me your email of this email list, I can send you > the project file. > > What exactly I did was that I included the relevant source files from SDL > package, and compile it with testing program. I was able to get the exe file > but the project also generated a library file in addition to the exe file. I > am confused by the fact that the project generating TimerTest.lib, that I > don't want t. Rather, I wanted to link them with TimerTest not intended to. > I checked the project configuration file, and there is no setting that will > generate a library file. I think it might be set in the program source code, > but I did not find it. > > I am interested in your idea of implement SDL wrapper in boost lib. Thank > you! > > Best regards, > Fanzhe Cui > +++++++++++++++++++++++++++ > Goldiom Systems LLC > - Information and Communication Technology Provider > Email: fanzhe.cui(a)goldiom.com > Tel: 973-210-4254 > www.goldiom.com > > > -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Christian Henning > Sent: Wednesday, June 06, 2007 10:06 AM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] port of GameDev SDL lib in Boost? > > Fanzhe, I have been working on a sdl wrapper for boost::gil. It lets > you draw on a canvas and react to event such as a timer event. I was > thinking of outsourcing this portion so people can use just that. The > good thing is the sdl is supporting almost the same platforms as boost > does. The bad thing probably is the license sdl is using, LGPL. > > If you want I can give you a pointer for the code. > > Christian > > On 6/6/07, fanzhe cui <fanzhe.cui(a)goldiom.com> wrote: > > Yes, I was referring to that library and more info could be found from the > > web: http://www.libsdl.org/. > > The problem with the boost timer that you mentioned is that it provides > the > > time elapsed, but not the interface like provided by SDL lib. Particularly > > the kind of timer callback function that is available in SDL lib is not > > available in Boost lit. > > > > Best regards, > > Fanzhe Cui > > > > ++++++++++++++++++++++ > > Goldiom Systems LLC > > - Information and Communication Technology Provider > > Email: fanzhe.cui(a)goldiom.com > > Tel: 973-210-4254 > > www.goldiom.com > > > > -----Original Message----- > > From: boost-users-bounces(a)lists.boost.org > > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Tarjei Knapstad > > Sent: Wednesday, June 06, 2007 4:02 AM > > To: boost-users(a)lists.boost.org > > Subject: Re: [Boost-users] port of GameDev SDL lib in Boost? > > > > On 6/6/07, fanzhe cui <fanzhe.cui(a)goldiom.com> wrote: > > > I have been using both Boost lib and GameDev SDL lib in same projects. > > Both > > > of the lib have very good platform independency. But they have some > > > functionalities overlapping each other and I would like to use only one > of > > > them. The timer lib in GameDev SDL is very easy to use and I hope such > lib > > > or functionally similar one exists in Boost lib. I had a look at boost > > > archive on previous discussion on implementing Boost timers and feel > that > > > there is still no good implementation of timer in Boost lib (correct me > if > > I > > > am wrong). Anybody in this email list had a look at GameDev timer and > have > > > considered implementing such a lib in Boost? > > > > > > > Are you referring to the Simple Direct Medialayer? > > > > http://lazyfoo.net/SDL_tutorials/lesson12/index.php > > > > What's wrong with/missing in boost::timer ? > > > > http://boost.org/libs/timer/index.html > > > > -- > > Tarjei > > _______________________________________________ > > Boost-users mailing list > > Boost-users(a)lists.boost.org > > http://lists.boost.org/mailman/listinfo.cgi/boost-users > > > > > > > > _______________________________________________ > > Boost-users mailing list > > Boost-users(a)lists.boost.org > > http://lists.boost.org/mailman/listinfo.cgi/boost-users > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users > > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users >

2 1

Re: [Boost-users] port of GameDev SDL lib in Boost?
by Christian Henning 07 Jun '07

07 Jun '07

Fanzhe, I have been working on a sdl wrapper for boost::gil. It lets you draw on a canvas and react to event such as a timer event. I was thinking of outsourcing this portion so people can use just that. The good thing is the sdl is supporting almost the same platforms as boost does. The bad thing probably is the license sdl is using, LGPL. If you want I can give you a pointer for the code. Christian On 6/6/07, fanzhe cui <fanzhe.cui(a)goldiom.com> wrote: > Yes, I was referring to that library and more info could be found from the > web: http://www.libsdl.org/. > The problem with the boost timer that you mentioned is that it provides the > time elapsed, but not the interface like provided by SDL lib. Particularly > the kind of timer callback function that is available in SDL lib is not > available in Boost lit. > > Best regards, > Fanzhe Cui > > ++++++++++++++++++++++ > Goldiom Systems LLC > - Information and Communication Technology Provider > Email: fanzhe.cui(a)goldiom.com > Tel: 973-210-4254 > www.goldiom.com > > -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Tarjei Knapstad > Sent: Wednesday, June 06, 2007 4:02 AM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] port of GameDev SDL lib in Boost? > > On 6/6/07, fanzhe cui <fanzhe.cui(a)goldiom.com> wrote: > > I have been using both Boost lib and GameDev SDL lib in same projects. > Both > > of the lib have very good platform independency. But they have some > > functionalities overlapping each other and I would like to use only one of > > them. The timer lib in GameDev SDL is very easy to use and I hope such lib > > or functionally similar one exists in Boost lib. I had a look at boost > > archive on previous discussion on implementing Boost timers and feel that > > there is still no good implementation of timer in Boost lib (correct me if > I > > am wrong). Anybody in this email list had a look at GameDev timer and have > > considered implementing such a lib in Boost? > > > > Are you referring to the Simple Direct Medialayer? > > http://lazyfoo.net/SDL_tutorials/lesson12/index.php > > What's wrong with/missing in boost::timer ? > > http://boost.org/libs/timer/index.html > > -- > Tarjei > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users > > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users >

2 2

Uninitialized value p$m_value
by Paul 07 Jun '07

07 Jun '07

Hi, I'm trying to learn how to use the Boost Graph Library. Here is a very simple code example. #include <boost/graph/adjacency_list.hpp> #include <string> int main( void ) { using namespace std; using namespace boost; typedef adjacency_list< listS, vecS, directedS, // Vertex properties property< vertex_name_t, std::string >, // Edge properties property< edge_weight_t, int > > Graph; Graph graph; // Graph traits used to access graph's iterator types graph_traits< Graph >::vertex_descriptor a, b; a = add_vertex( graph ); b = add_vertex( graph ); graph_traits< Graph >::edge_descriptor ed; bool inserted; tie( ed, inserted ) = add_edge( a, b, graph ); // LINE 26 return 0; } When I compile this with g++ v4, I get on my Debian Etch system the warning for line 26: /usr/include/boost/graph/detail/adjacency_list.hpp:263: warning: 'p$m_value' is used uninitialized in this function Line 263 in adjacency_list.hpp looks as follows: inline stored_edge_property(Vertex target, const Property& p = Property()) : stored_edge<Vertex>(target), m_property(new Property(p)) { } What am I doing wrong and how can I fix that? Thank you. Regards, Paul

1 0

[filesystem] remove for directories
by Ovanes Markarian 07 Jun '07

07 Jun '07

Hello all! Is there any way to remove a directory using boost::filesystem? remove and remove_all throw an exception. Remove docs reference a POSIX remove(). There is written: [quote] If path does not name a directory, remove(path) shall be equivalent to unlink(path). If path names a directory, remove(path) shall be equivalent to rmdir(path). [/quote] Unfortunately remove does not behave so (on WinXP and Visual C++ 8). One more issue: the link to the POSIX remove() doc points to link() and not remove. With Kind Regards, Ovanes

1 0

Signal not disconnecting?
by Christian Mol 07 Jun '07

07 Jun '07

Hi, I'm using the signal library in my application. However if I call disconnect() on my connection object the connection is not removed. Is this default behaviour? I would like not having this behaviour because the signal is connected to a member function within an object that is actually deleted. Any ideas? Regards, Christian

2 2

BGL compile error
by gast128 07 Jun '07

07 Jun '07

Dear all, We want to (DLL) export a boost graph. Probably on (DLL) exporting, the compiler tries to generate code for every member function. However on VC++7.1 it gives then a problem with operator[]. This can be easily verified with the following case: void Foo() { boost::adjacency_list<> graph; graph[0]; } We use here Boost 1.33.0. Anyone an idea? Wkr, me

2 8

[preprocessor] usage problem
by Christopher Lux 07 Jun '07

07 Jun '07

hi, i want to do the following in a win32 project, which generates a dlls. commonly there is a macro defined like this: #ifdef DLL_BUILD #define __scm_export __declspec(dllexport) #else #define __scm_export __declspec(dllimport) #endif now i have several projects which generate dlls and depend on each other like: core_lib <- graphics_lib now to do this it is needed to differenciate between dll builds. lets say with a macro CORE_DLL_BUILD and GFX_DLL_BUILD. BUT i think this is hell ;) and thought of something like this: i would like to have one macro __scm_export(lib) which decides by the lib parameter which lib is build. i tried it the following way: (code broken out of context) #include <boost/preprocessor.hpp> #include <boost/preprocessor/detail/is_nullary.hpp> #if SCM_COMPILER == SCM_COMPILER_MSVC #define __scm_export(lib) export_(BOOST_PP_EXPAND(BOOST_PP_CAT(SCM_BUILD_LIBRARY_, lib))) #define export_(lib) BOOST_PP_IF(BOOST_PP_IS_NULLARY(lib), __declspec(dllexport), __declspec(dllimport)) #define __scm_private(lib) #else #pragma error "unsupported compiler" #endif this way i only have to define something like /DSCM_BUILD_LIBRARY_core=() for the core project and /DSCM_BUILD_LIBRARY_ogl=() for the graphics library and use __scm_export(ogl) and __scm_export(core) in the particular libraries. this works perfectly, BUT i am searching for a more elegant way to do this, because i do not like the definition of a unary macro for the projects. i would like more to define it this way: /DSCM_BUILD_LIBRARY=core and /DSCM_BUILD_LIBRARY=ogl for the libs. i experimented with BOOST_PP_IIF and so on, but the problem is if these macros are presented with an undefined macro (like when i use the one lib in the other) they do not use the false alternative and insert a lengthy macro. after a long night i came up with the BOOST_PP_IS_NULLARY workaround, but as is said i do not think is is a very good solution. dies anyone have suggestions how to solve this on a more elegant way? Thanks -chris -- Christopher Lux | | Bauhaus University Weimar | Faculty of Media - Virtual Reality Systems Group

1 0

[date_time] Posix timespec support?
by Terry G 07 Jun '07

07 Jun '07

Does date_time support POSIX timespec? I assume that timespec is standard POSIX. Is it not? If so, is it supported now, or how should it be supported. I'd be willing to help. terry

2 2

Operator overloading and enable_if
by Bill Buklis 07 Jun '07

07 Jun '07

For a template class I'd like to add * and -> operators for types that support it (mainly pointers). However, most instantiations of this class won't be pointers and therefore these operators won't be valid. I understand that enable_if can't directly support member functions. But, how can I do the equivalent of this? template< typename T > class Sample { T data; public: Sample( T& data ) : data(data) { } typename boost::enable_if< boost::is_pointer<T>, T >::type operator->() const { return(data); } typename boost::enable_if< boost::is_pointer<T>, typename boost::remove_pointer<T>::type >::type operator*() const { return(*data); } };

2 3

[mpl] Fusion/MPL examples
by Zeljko Vrba 06 Jun '07

06 Jun '07

The fusion library manual gives a single example and says "this is just the tip of the iceberg". I was wondering whether the slides/materials from the Boost Conference are available? I'm most interested in the lectures "Boost Metaprogramming Concepts and Frameworks" and "Fusion by example". I'm in the process of (slowly) reading THE "MPL book" (by Dave and Alexei), but I'm looking for more "down-to-earth" examples, rather than constructing small DSLs or creating optimized versions of swap. Synopses of the above lectures contain: "We'll also get a taste of high-level metaprogramming abstractions by using several Boost metaprogramming librariesMPL, Preprocessor, and the Fusion tuple library to solve real problems." "The emphasis for the examples will be on using Boost.Fusion in application code, rather than as infrastructure for library developers." I'm in the process of writing a recursive data structure with very similar operations at every level, but still with small behavioral variations. It seems like a perfect problem for metaprogramming, but I fail to map MPL's type manipulation routines to my down-to-earth problem. I was hoping to get some more insight in MPL from the materials for the abovementioned lectures. Get a new perspective and background to keep in mind while reading the MPL book. So, I kindly ask Dave Abrahams, Dan Marsden and Joel de Guzman to make their lecture materials available on-line, if possible. Thanks and best regards, Zeljko.

4 5

Re: [Boost-users] [serialization] Wrapper + make_nvp woes
by Dan Thill 06 Jun '07

06 Jun '07

Thank you for the fast reply, Robert. > Another idea is to cast your character array to a ... > character array - like static_cast< int [64] &>(my array address) > but that would require a constant size which might not work > for you. I'm not certain I quite understand this. Perhaps I didn't get my thoughts down coherently. I'm seeking to write my serialization like this (sorry I forgot to include this in my initial msg): char some_array[5] = "test"; .... ar & make_nvp("some_array", make_char_array(some_array, 5)); And obtain the following output: output.xml: ... <some_array>test</some_array> output.txt: .... 4 test .... --------------------------- My aforementioned make_char_array() works fine for text archives--just not when the result is composed with make_nvp(). > Finally you can use the blunt instrument approach. > > save(.... > std::string temp_string; > // copy data into temp_string > ar << temp_string > > load > .. do the opposite. Which is pretty much what my serialization wrapper is doing (this is in fact, what I wrote initially, before trying to make it a serialization wrapper). While I can certainly do the blunt approach, it will require me to split my serialization function :(

2 2

Linking problesm with boost/format.hpp
by ronnie_raj 06 Jun '07

06 Jun '07

Hello, I'm been developing an application on SUSE 9.3, gcc 3.3.5 and within my makefile I have the following for the CPPFLAGS "-g -O0" and the code complied and linked fine. I reached the end of the development and decided to up the optimisation so I changed the line to "-O2" and removed the "-g". When I got the linking stage I got the following error: /usr/lib/gcc-lib/i586-suse-linux/3.3.5/../../../../i586-suse-linux/bin/ld: `.gnu.linkonce.t._ZN5boost2io6detail22parse_printf_directiveIcSt11char_traitsIcESaIcEN9__gnu_cxx17__normal_iteratorIPKcSsEESt5ctypeIcEEEbRT2_RKSD_PNS1_11format_itemIT_T0_T1_EERKT3_jh' referenced in section `.rodata' of sg_gui_export_dialog.o: defined in discarded section `.gnu.linkonce.t._ZN5boost2io6detail22parse_printf_directiveIcSt11char_traitsIcESaIcEN9__gnu_cxx17__normal_iteratorIPKcSsEESt5ctypeIcEEEbRT2_RKSD_PNS1_11format_itemIT_T0_T1_EERKT3_jh' of sg_gui_export_dialog.o For what I can figure out its complaining about boost. I got the above error for 4 files and within all 4 files I use the "<boost/format.hpp>" library. I have used other boost libraries in other files but the linker didn't complain about them it was only the files where I used "format.hpp". I had a play around and if the CPPFLAGS line within the makefile and if it reads "-g -O2" then it links fine but if I don't have the "-g" it comes up with error above. Does anyone have any clue as to what I'm doing wrong? Thanks, Kiran -- View this message in context: http://www.nabble.com/Linking-problesm-with-boost-format.hpp-tf3876852.html… Sent from the Boost - Users mailing list archive at Nabble.com.

2 1

[function] Bug in 1.34.0 with Sun Studio on Solaris
by Markus Bernhardt 06 Jun '07

06 Jun '07

Hi, I get the following warnings when using a boost::thread_specific_ptr<unsigned int> and compiling with Sun Studio 11 (with latest patches) or Sun Studio 12 on Solaris x86. Warning: Could not find source for boost::type_traits::ice_not<0>::value. "../../../build/debug/include/boost/function/function_template.hpp", line 407: Warning: Could not find source for boost::detail::function::function_allows_small_object_optimization<boost::detail::tss_adapter<unsigned>>::value. A similar warning is reported when I use boost::bind. Every comment is apreciated. Markus

4 4

Re: [Boost-users] port of GameDev SDL lib in Boost?
by Tarjei Knapstad 06 Jun '07

06 Jun '07

On 6/6/07, fanzhe cui <fanzhe.cui(a)goldiom.com> wrote: > I have been using both Boost lib and GameDev SDL lib in same projects. Both > of the lib have very good platform independency. But they have some > functionalities overlapping each other and I would like to use only one of > them. The timer lib in GameDev SDL is very easy to use and I hope such lib > or functionally similar one exists in Boost lib. I had a look at boost > archive on previous discussion on implementing Boost timers and feel that > there is still no good implementation of timer in Boost lib (correct me if I > am wrong). Anybody in this email list had a look at GameDev timer and have > considered implementing such a lib in Boost? > Are you referring to the Simple Direct Medialayer? http://lazyfoo.net/SDL_tutorials/lesson12/index.php What's wrong with/missing in boost::timer ? http://boost.org/libs/timer/index.html -- Tarjei

2 1

Compilation errors when using boost libraries
by Varadarajan, Satiamoorthy (GE Infra, Transportation) 06 Jun '07

06 Jun '07

Hi, this is my first time to use Boost -librairies. I have created a Project folder where in my complete Software architeture is available. I have placed boost libraries downloaded from boost.org site within INCLUDE dir of VC 2005 Install directory. However I received many compilation errors. Can anyone help me to resolve these errors. Am I doing the right thing to get the CPP Software to compile. List of Errors I have received are here by ------ Build started: Project: vc2005_mcf52xxinit, Configuration: Debug Win32 ------ Compiling... CPU_MCF5282Init.cpp c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(63) : error C2653: 'T1' : is not a class or namespace name c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(63) : error C2065: 'value' : undeclared identifier c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(66) : error C2065: 'T2' : undeclared identifier c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(67) : error C2065: 'T3' : undeclared identifier c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(70) : error C2899: typename cannot be used outside a template declaration c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(70) : error C2955: 'boost::mpl::if_c' : use of class template requires template argument list c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(35) : see declaration of 'boost::mpl::if_c' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : error C2989: 'boost::mpl::if_' : class template has already been declared as a non-class template c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(56) : see declaration of 'boost::mpl::if_' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : error C2143: syntax error : missing ';' before '<' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : error C2913: explicit specialization; 'boost::mpl::if_' is not a specialization of a class template c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : error C2059: syntax error : '<' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : error C2143: syntax error : missing ';' before '{' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : error C2447: '{' : missing function header (old-style formal list?) c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : error C2947: expecting '>' to terminate template-argument-list, found '<' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : error C2146: syntax error : missing ';' before identifier 'na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : error C3856: 'boost::mpl': class is not a class template c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : error C2086: 'int boost::mpl::na' : redefinition c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : error C2086: 'int boost::mpl::na' : redefinition c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : error C2143: syntax error : missing ';' before '>' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : warning C4091: 'typedef ' : ignored on left of 'boost::mpl::if_' when no variable is declared c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : error C2143: syntax error : missing ';' before '<' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : error C2059: syntax error : '<' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : warning C4091: 'typedef ' : ignored on left of 'boost::mpl::if_' when no variable is declared c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : error C2143: syntax error : missing ';' before '<' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : error C2059: syntax error : '<' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(133) : error C2059: syntax error : '}' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(133) : error C2143: syntax error : missing ';' before '}' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(133) : error C2059: syntax error : '}' c:\program files\microsoft visual studio 8\vc\include\boost\type_traits\type_with_alignment.hpp(32) : error C2143: syntax error : missing ';' before '{' c:\program files\microsoft visual studio 8\vc\include\boost\type_traits\type_with_alignment.hpp(32) : error C2447: '{' : missing function header (old-style formal list?) c:\program files\microsoft visual studio 8\vc\include\boost\mpl\eval_if.hpp(40) : error C2143: syntax error : missing ',' before '<' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\eval_if.hpp(44) : see reference to class template instantiation 'boost::mpl::eval_if<C,F1,F2>' being compiled c:\program files\microsoft visual studio 8\vc\include\boost\mpl\eval_if.hpp(40) : error C2039: 'type' : is not a member of '`global namespace'' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\eval_if.hpp(67) : error C2923: 'boost::mpl::eval_if' : 'boost::mpl::na' is not a valid template type argument for parameter 'C' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\eval_if.hpp(67) : error C2923: 'boost::mpl::eval_if' : 'boost::mpl::na' is not a valid template type argument for parameter 'F1' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\eval_if.hpp(67) : error C2923: 'boost::mpl::eval_if' : 'boost::mpl::na' is not a valid template type argument for parameter 'F2' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\eval_if.hpp(67) : error C2913: explicit specialization; 'boost::mpl::eval_if' is not a specialization of a class template c:\program files\microsoft visual studio 8\vc\include\boost\mpl\eval_if.hpp(67) : error C3203: 'eval_if' : unspecialized class template can't be used as a template argument for template parameter 'T', expected a real type c:\program files\microsoft visual studio 8\vc\include\boost\mpl\identity.hpp(40) : error C2923: 'boost::mpl::identity' : 'boost::mpl::na' is not a valid template type argument for parameter 'T' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\identity.hpp(40) : error C2913: explicit specialization; 'boost::mpl::identity' is not a specialization of a class template c:\program files\microsoft visual studio 8\vc\include\boost\mpl\identity.hpp(40) : error C3203: 'identity' : unspecialized class template can't be used as a template argument for template parameter 'T', expected a real type c:\program files\microsoft visual studio 8\vc\include\boost\mpl\identity.hpp(40) : error C2953: 'boost::mpl::lambda<int,Tag>' : class template has already been defined c:\program files\microsoft visual studio 8\vc\include\boost\mpl\eval_if.hpp(67) : see declaration of 'boost::mpl::lambda<int,Tag>' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\identity.hpp(41) : error C2923: 'boost::mpl::make_identity' : 'boost::mpl::na' is not a valid template type argument for parameter 'T' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\identity.hpp(41) : error C2913: explicit specialization; 'boost::mpl::make_identity' is not a specialization of a class template c:\program files\microsoft visual studio 8\vc\include\boost\mpl\identity.hpp(41) : error C3203: 'make_identity' : unspecialized class template can't be used as a template argument for template parameter 'T', expected a real type c:\program files\microsoft visual studio 8\vc\include\boost\mpl\identity.hpp(41) : error C2953: 'boost::mpl::lambda<int,Tag>' : class template has already been defined c:\program files\microsoft visual studio 8\vc\include\boost\mpl\eval_if.hpp(67) : see declaration of 'boost::mpl::lambda<int,Tag>' c:\program files\microsoft visual studio 8\vc\include\boost\aligned_storage.hpp(36) : error C2065: 'max_align' : undeclared identifier c:\program files\microsoft visual studio 8\vc\include\boost\aligned_storage.hpp(36) : error C2955: 'boost::alignment_of' : use of class template requires template argument list c:\program files\microsoft visual studio 8\vc\include\boost\type_traits\alignment_of.hpp(61) : see declaration of 'boost::alignment_of' c:\program files\microsoft visual studio 8\vc\include\boost\aligned_storage.hpp(54) : error C2065: 'type_with_alignment' : undeclared identifier c:\program files\microsoft visual studio 8\vc\include\boost\aligned_storage.hpp(48) : see reference to class template instantiation 'boost::detail::aligned_storage::aligned_storage_imp<size_,alignment_>:: data_t' being compiled c:\program files\microsoft visual studio 8\vc\include\boost\aligned_storage.hpp(57) : see reference to class template instantiation 'boost::detail::aligned_storage::aligned_storage_imp<size_,alignment_>' being compiled c:\program files\microsoft visual studio 8\vc\include\boost\aligned_storage.hpp(54) : error C3203: 'identity' : unspecialized class template can't be used as a template argument for template parameter 'F1', expected a real type c:\program files\microsoft visual studio 8\vc\include\boost\aligned_storage.hpp(54) : error C2974: 'boost::mpl::eval_if_c' : invalid template argument for 'F2', type expected c:\program files\microsoft visual studio 8\vc\include\boost\mpl\eval_if.hpp(62) : see declaration of 'boost::mpl::eval_if_c' c:\program files\microsoft visual studio 8\vc\include\boost\aligned_storage.hpp(55) : error C2059: syntax error : '>' c:\program files\microsoft visual studio 8\vc\include\boost\aligned_storage.hpp(55) : error C2039: 'type' : is not a member of '`global namespace'' c:\program files\microsoft visual studio 8\vc\include\boost\aligned_storage.hpp(55) : error C2238: unexpected token(s) preceding ';' d:\ucii_dart\software engineering\adu\code\pal\cpu\cpu_mcf52xxinterruptcontroller.h(57) : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int d:\ucii_dart\software engineering\adu\code\pal\cpu\cpu_mcf52xxinterruptcontroller.h(57) : error C2143: syntax error : missing ';' before '*' d:\ucii_dart\software engineering\adu\code\pal\cpu\cpu_mcf52xxinterruptcontroller.h(57) : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int c:\program files\microsoft visual studio 8\vc\include\boost\mpl\sizeof.hpp(32) : error C2923: 'boost::mpl::sizeof_' : 'boost::mpl::na' is not a valid template type argument for parameter 'T' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\sizeof.hpp(32) : error C2913: explicit specialization; 'boost::mpl::sizeof_' is not a specialization of a class template c:\program files\microsoft visual studio 8\vc\include\boost\mpl\sizeof.hpp(32) : error C3203: 'sizeof_' : unspecialized class template can't be used as a template argument for template parameter 'T', expected a real type c:\program files\microsoft visual studio 8\vc\include\boost\mpl\sizeof.hpp(32) : error C2953: 'boost::mpl::lambda<int,Tag>' : class template has already been defined c:\program files\microsoft visual studio 8\vc\include\boost\mpl\eval_if.hpp(67) : see declaration of 'boost::mpl::lambda<int,Tag>' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\void.hpp(71) : error C2923: 'boost::mpl::is_void_' : 'boost::mpl::na' is not a valid template type argument for parameter 'T' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\void.hpp(71) : error C2913: explicit specialization; 'boost::mpl::is_void_' is not a specialization of a class template c:\program files\microsoft visual studio 8\vc\include\boost\mpl\void.hpp(71) : error C3203: 'is_void_' : unspecialized class template can't be used as a template argument for template parameter 'T', expected a real type c:\program files\microsoft visual studio 8\vc\include\boost\mpl\void.hpp(71) : error C2953: 'boost::mpl::lambda<int,Tag>' : class template has already been defined c:\program files\microsoft visual studio 8\vc\include\boost\mpl\eval_if.hpp(67) : see declaration of 'boost::mpl::lambda<int,Tag>' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\void.hpp(72) : error C2923: 'boost::mpl::is_not_void_' : 'boost::mpl::na' is not a valid template type argument for parameter 'T' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\void.hpp(72) : error C2913: explicit specialization; 'boost::mpl::is_not_void_' is not a specialization of a class template c:\program files\microsoft visual studio 8\vc\include\boost\mpl\void.hpp(72) : error C3203: 'is_not_void_' : unspecialized class template can't be used as a template argument for template parameter 'T', expected a real type c:\program files\microsoft visual studio 8\vc\include\boost\mpl\void.hpp(72) : error C2953: 'boost::mpl::lambda<int,Tag>' : class template has already been defined c:\program files\microsoft visual studio 8\vc\include\boost\mpl\eval_if.hpp(67) : see declaration of 'boost::mpl::lambda<int,Tag>' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\next_prior.hpp(44) : error C2923: 'boost::mpl::next' : 'boost::mpl::na' is not a valid template type argument for parameter 'T' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\next_prior.hpp(44) : error C2913: explicit specialization; 'boost::mpl::next' is not a specialization of a class template c:\program files\microsoft visual studio 8\vc\include\boost\mpl\next_prior.hpp(44) : error C3203: 'next' : unspecialized class template can't be used as a template argument for template parameter 'T', expected a real type c:\program files\microsoft visual studio 8\vc\include\boost\mpl\next_prior.hpp(44) : error C2953: 'boost::mpl::lambda<int,Tag>' : class template has already been defined c:\program files\microsoft visual studio 8\vc\include\boost\mpl\eval_if.hpp(67) : see declaration of 'boost::mpl::lambda<int,Tag>' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\next_prior.hpp(45) : error C2923: 'boost::mpl::prior' : 'boost::mpl::na' is not a valid template type argument for parameter 'T' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\next_prior.hpp(45) : error C2913: explicit specialization; 'boost::mpl::prior' is not a specialization of a class template c:\program files\microsoft visual studio 8\vc\include\boost\mpl\next_prior.hpp(45) : error C3203: 'prior' : unspecialized class template can't be used as a template argument for template parameter 'T', expected a real type c:\program files\microsoft visual studio 8\vc\include\boost\mpl\next_prior.hpp(45) : error C2953: 'boost::mpl::lambda<int,Tag>' : class template has already been defined c:\program files\microsoft visual studio 8\vc\include\boost\mpl\eval_if.hpp(67) : see declaration of 'boost::mpl::lambda<int,Tag>' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\tag.hpp(33) : error C2143: syntax error : missing ',' before '<' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\tag.hpp(48) : see reference to class template instantiation 'boost::mpl::tag<T,Default>' being compiled c:\program files\microsoft visual studio 8\vc\include\boost\mpl\tag.hpp(37) : error C2039: 'type' : is not a member of '`global namespace'' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(32) : error C2923: 'boost::mpl::plus_impl' : 'boost::mpl::na' is not a valid template type argument for parameter 'Tag1' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(32) : error C2923: 'boost::mpl::plus_impl' : 'boost::mpl::na' is not a valid template type argument for parameter 'Tag2' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(38) : error C2913: explicit specialization; 'boost::mpl::plus_impl' is not a specialization of a class template c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(47) : error C2976: 'boost::mpl::plus_impl' : too few template arguments c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(19) : see declaration of 'boost::mpl::plus_impl' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(56) : error C2976: 'boost::mpl::plus_impl' : too few template arguments c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(19) : see declaration of 'boost::mpl::plus_impl' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(69) : error C2923: 'boost::mpl::plus' : 'boost::mpl::na' is not a valid template type argument for parameter 'N3' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(71) : see reference to class template instantiation 'boost::mpl::plus<N1,N2,N3,N4,N5>' being compiled c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(69) : error C2923: 'boost::mpl::plus' : 'boost::mpl::na' is not a valid template type argument for parameter 'N4' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(69) : error C2923: 'boost::mpl::plus' : 'boost::mpl::na' is not a valid template type argument for parameter 'N5' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(69) : error C3203: 'plus' : unspecialized class template can't be used as a template argument for template parameter 'N1', expected a real type c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(69) : error C2923: 'boost::mpl::plus' : 'boost::mpl::na' is not a valid template type argument for parameter 'N3' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(69) : error C2923: 'boost::mpl::plus' : 'boost::mpl::na' is not a valid template type argument for parameter 'N4' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(69) : error C2923: 'boost::mpl::plus' : 'boost::mpl::na' is not a valid template type argument for parameter 'N5' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(69) : error C3203: 'plus' : unspecialized class template can't be used as a template argument for template parameter 'N1', expected a real type c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(69) : error C2923: 'boost::mpl::plus' : 'boost::mpl::na' is not a valid template type argument for parameter 'N3' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(69) : error C2923: 'boost::mpl::plus' : 'boost::mpl::na' is not a valid template type argument for parameter 'N4' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(69) : error C2923: 'boost::mpl::plus' : 'boost::mpl::na' is not a valid template type argument for parameter 'N5' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(69) : error C3203: 'plus' : unspecialized class template can't be used as a template argument for template parameter 'N1', expected a real type c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(69) : error C2923: 'boost::mpl::plus' : 'boost::mpl::na' is not a valid template type argument for parameter 'N3' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(69) : error C2923: 'boost::mpl::plus' : 'boost::mpl::na' is not a valid template type argument for parameter 'N4' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(69) : error C2923: 'boost::mpl::plus' : 'boost::mpl::na' is not a valid template type argument for parameter 'N5' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(70) : error C2955: 'boost::mpl::plus' : use of class template requires template argument list c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(69) : see declaration of 'boost::mpl::plus' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(78) : error C2923: 'boost::mpl::plus' : 'boost::mpl::na' is not a valid template type argument for parameter 'N5' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\if.hpp(131) : see declaration of 'boost::mpl::na' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(85) : error C2976: 'boost::mpl::plus' : too few template arguments c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(69) : see declaration of 'boost::mpl::plus' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(99) : error C2976: 'boost::mpl::plus' : too few template arguments c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(69) : see declaration of 'boost::mpl::plus' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(116) : error C2976: 'boost::mpl::plus' : too few template arguments c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(69) : see declaration of 'boost::mpl::plus' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(118) : error C2913: explicit specialization; 'boost::mpl::plus' is not a specialization of a class template c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(118) : error C3203: 'plus' : unspecialized class template can't be used as a template argument for template parameter 'T', expected a real ype c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(118) : error C2953: 'boost::mpl::lambda<int,Tag>' : class template has already been defined c:\program files\microsoft visual studio 8\vc\include\boost\mpl\eval_if.hpp(67) : see declaration of 'boost::mpl::lambda<int,Tag>' c:\program files\microsoft visual studio 8\vc\include\boost\mpl\aux_\preprocessed\plain\plus.hpp(118) : fatal error C1003: error count exceeds 100; stopping compilation Build log was saved at "file://d:\Users\307004223\My Documents\Visual Studio 2005\Projects\vc2005_mcf52xxinit\vc2005_mcf52xxinit\Debug\BuildLog.htm" vc2005_mcf52xxinit - 107 error(s), 2 warning(s) ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== Regards Satia

5 7

[program_options] is this library actually useful
by jp＠day-one.com 06 Jun '07

06 Jun '07

hi, i hate rewriting getopts, but avaliable implimentations are always horrible, so there i was. then i decided to use boost::program_options .... all i want to do is something like..: translate --seq1 10 --seq2 10 13 --filter *.cpp *.hpp *.h where seq1 and seq2 can take any number of numbers between 0 and 255 anyway, if i use anything like desc.add_options ("seq1", po::value< std::vector<byte> >() -> multitoken() -> composing() -> notifier(seq1()), "byte sequence to find") it just returns all the tokens following the first option. is the library too stupid to stop eating tokens when it comes to another option? if so, what is its point? please... jono

2 1

boost:array lacks a statically-checked get()
by Benoit Hudson 06 Jun '07

06 Jun '07

Reading the archives, I see that the idea of adding a template <unsigned i> T get(); function to boost::array has been somewhat summarily rejected as unnecessary: http://lists.boost.org/boost-users/2005/08/12983.php et seq. And yet I'm finding myself wanting it repeatedly. Here are three places I've seen it crop up: (1) My current application is an arbitrary-dimensional geometry code. I want it to be a template argument what dimension we live in (2, 3, 4, ...). In d dimensions, a simplex has d+1 vertices on it, a point has d coordinates, and an face is a (d-1)-dimensional simplex that has d vertices. You can imagine the potential for off-by-one bugs (personally, I need not imagine). These get caught at runtime when using the array operator[], but I'd rather they be caught at compile time when possible. Therefore, when I'm feeling caffeinated, I write the appropriate BOOST_STATIC_ASSERT (which is of course itself sometimes off by one). (2) I've seen (and written) rather a lot of GUI, networking, and cross-language glue where a common idiom is to have an array of function pointers. Sometimes, the 'name' of the function is an integer read in at runtime. Sometimes, it is known at compile-time. Typically I've seen this implemented using an enum; calling function i is then functions[i](args), whereas calling function foo is functions[FOO](args). The former one can only be checked at run-time. The latter one should be checked at compile-time. It's fine for me to force me to write it as functions.get<FOO>(args) to get compile-time checking, but I do not want to be forced to change both entry FOO in the array, and every call to foo() elsewhere, if I change the name of the function (i.e. during debugging). When I've done this in the past, I've been living in C-land or C++ without boost, so the idea of compile-time checking didn't even occur to me (and, of course, bugs cropped up all the time). (3) Sometimes I don't need an array at all -- I just want a tuple with all values the same type. It's far handier to declare that type as array<foo, 4> than as tuple<foo, foo, foo, foo>. Also, we can now also use the uber-delicious BOOST_FOREACH on the array, which can't be done on the tuple. Summarizing: whenever a client wants to use both integers and names to access a field, array::get<> is useful and matches the boost philosophy of compile-time checking over runtime checking. The change is small in terms of LOC, and does not affect any code outside this one function (and, as far as I can determine, is even ABI-compatible with the prior array code). The runtime implication is nil. -- Benoît

2 4

[serialization] Wrapper + make_nvp woes
by Dan Thill 06 Jun '07

06 Jun '07

Greetings, I have a need to serialize plain old C character arrays as strings within the xml and text archive types. By default, these are serialized element by element. I've read the previous messages on the list on the perils of doing such (buffer overflows), and I hit across a somewhat acceptable solution using serialization wrappers. I'm new to all of this, so I based my implementation off of "nvp" and "binary_object" ------------------------------- struct char_array { char* const m_t; const std::size_t m_size; template<class Archive> void save(Archive & ar, const unsigned int /* file_version */) const { const std::string t(m_t); ar.operator<<(t); } template<class Archive> void load(Archive & ar, const unsigned int /* file_version */) const { std::string t; ar.operator>>(t); scASSERT_MSG(t.size() < m_size, "A corruption occurred"); strncpy(const_cast<char*>(m_t), t.c_str(), m_size); } BOOST_SERIALIZATION_SPLIT_MEMBER() explicit char_array( char* const t, std::size_t size) : m_t(t), m_size(size) {} char_array(const char_array & rhs) : m_t(rhs.m_t), m_size(rhs.m_size) {} }; ----------------------------------------------- The premise is simple, probably naive, and not too efficient: Convert each char[] to a std::string, and serialize that. Loading is just the reverse. However, I keep getting a compile time exception in the xml archive loading code. This is with Boost 1.33, VC8. 1>c:\Boost\include\boost-1_33_1\boost/archive/basic_xml_oarchive.hpp(86) : error C2027: use of undefined type 'boost::STATIC_ASSERTION_FAILURE<x>' 1> with 1> [ 1> x=false 1> ] 1> c:\Boost\include\boost-1_33_1\boost/archive/detail/interface_oarchive.hpp(78) : see reference to function template instantiation 'void boost::archive::basic_xml_oarchive<Archive>::save_override<T>(T &,int)' being compiled 1> with 1> [ 1> Archive=boost::archive::xml_oarchive, 1> T=const std::string 1> ] 1> d:\SDEV8\SOURCE\include\sc_s11n/char_array.h(49) : see reference to function template instantiation 'Archive &boost::archive::detail::interface_oarchive<Archive>::operator <<<const std::string>(T &)' being compiled 1> with 1> [ 1> Archive=boost::archive::xml_oarchive, 1> T=const std::string 1> ] It seems as if, after serializing the nvp object, it's expecting an nvp object around the std::string. Is there a way that I can call the default serialization for std::string from my char_array wrapper, without having it go through the normal xml specializations which require it to be part of an nvp? I'm new with this, so please be gentle. I've consumed almost the entire list archive and I can't come up with a fix. Thanks, Dan

2 1

[serialization]: text (xml) iarchive - format options for integers?
by Frank Bergemann 06 Jun '07

06 Jun '07

Hi, can i make xml_iarchive accept "0x11" instead of "17" for an int type data element? Or do i have to derive my own iarchive and implement that myself? \Frank _______________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

2 1

[Graph] remove edges and reinsert them
by Dominik Heide 06 Jun '07

06 Jun '07

Hi there, I want to delete a vertex from a graph and later reinsert it again. I did this by removing all edges from that vertex and later adding the edges again. But the behavior of the program quite strange. First, I use a undirected adjacancy list typedef adjacency_list<vecS, vecS, undirectedS, no_property, no_property> Graph; When, use Graph g, gs; // set g typename graph_traits<GraphT>::vertex_iterator vi, ve, vii, vei; typename graph_traits<GraphT>::out_edge_iterator out_i, out_end, tmp; for( tie(vi, ve) = vertices(g); vi != ve; vi++) { gs = g; clear_vertex( *vi, g) // some code g = gs; } everything is fine. I don't want to save the whole graph since I only delete a couple of edges. Therefore, I did vector<typename graph_traits<GraphT>::vertex_descriptor> deletedEdges; typename vector<typename graph_traits<GraphT>::vertex_descriptor>::iterator dei; typename graph_traits<GraphT>::vertex_iterator vi, ve, vii, vei; typename graph_traits<GraphT>::out_edge_iterator out_i, out_end, tmp; ... for( tie(vi, ve) = vertices(g); vi != ve; vi++) { for( tie( out_i, out_end ) = out_edges( *vi, g); out_i != out_end; out_i++) { deletedEdges.push_back(target(*out_i, g)); } clear_vertex( *vi, g) // some code for(dei = deletedEdges.begin(); dei < deletedEdges.end(); ++dei) { add_edge( *vi, *dei, g); } } This code does not restore the graph completely. Although it looks the same the shortest paths are different to the ones with the above code. Is there something about clear_vertex() I don't know and therefore don't restore corectly? Any help appreachiated, Thank you, Dominik

2 1

[BGL] topological_sort compile error
by David A. Greene 05 Jun '07

05 Jun '07

Hi everyone, I'm having trouble with BGL's (Boost 1.33.1) topological sort. In my source code I have this simple call: std::vector<my_vertex> rev_topo_order; topological_sort(*t, std::back_inserter(rev_topo_order)); Here "t" is an iterator to a list of graphs declared like this: typedef boost::adjacency_list< boost::setS, // Out edge list type boost::listS, // Vertex list type boost::bidirectionalS, // Needed for DAG, topo sort my_property_bundle // Vertex properties > my_graph_type; The error trace below is mostly gobbledygook to me, but it looks like it's running into trouble with BGL's default bgl_named_params. The call chain runs through this curious bit of code: template <typename VertexListGraph, typename OutputIterator> void topological_sort(VertexListGraph& g, OutputIterator result) { topological_sort(g, result, bgl_named_params<int, buffer_param_t>(0)); // bogus } That looks...interesting to me. What's with the "bogus" comment? Any idea what's going on here? Any more information I can provide that would be helpful? The gmane archives show that Renaud Lepere ran into this problem in August '06 but I can't find any replies to his question. He gave a small example which I've confirmed reproduces the problem with g++ 4.1.2: #include <boost/graph/graph_traits.hpp> #include <boost/graph/adjacency_list.hpp> #include <boost/graph/depth_first_search.hpp> #include <boost/graph/visitors.hpp> #include <boost/graph/topological_sort.hpp> #include <iterator> typedef boost::adjacency_list<boost::vecS, boost::listS, boost::bidirectionalS, int, int > Graph; typedef boost::graph_traits<Graph>::vertex_descriptor Vertex; typedef std::vector< Vertex > Vertices; int main() { Graph g; Vertices vs; boost::topological_sort(g, back_inserter(vs)); } Thanks for any help you can give. -Dave ---------------------- Error trace ---------------------- ./boost-1_33_1/boost/property_map.hpp: In member function 'R boost::iterator_property_map<RandomAccessIterator, IndexMap, T, R>::operator[](typename boost::property_traits<IndexMap>::key_type) const [with RandomAccessIterator = __gnu_cxx::__normal_iterator<boost::default_color_type*, std::vector<boost::default_color_type, std::allocator<boost::default_color_type> > >, IndexMap = boost::adj_list_vertex_property_map<boost::adjacency_list<boost::setS, boost::listS, boost::bidirectionalS, myclass::my_property_bundle, boost::no_property, boost::no_property, boost::listS>, boost::detail::error_property_not_found, const boost::detail::error_property_not_found&, boost::vertex_index_t>, T = boost::default_color_type, R = boost::default_color_type&]': ./boost-1_33_1/boost/property_map.hpp:319: instantiated from 'void boost::put(const boost::put_get_helper<Reference, PropertyMap>&, K, const V&) [with PropertyMap = boost::iterator_property_map<__gnu_cxx::__normal_iterator<boost::default_color_type*, std::vector<boost::default_color_type, std::allocator<boost::default_color_type> > >, boost::adj_list_vertex_property_map<boost::adjacency_list<boost::setS, boost::listS, boost::bidirectionalS, myclass::my_property_bundle, boost::no_property, boost::no_property, boost::listS>, boost::detail::error_property_not_found, const boost::detail::error_property_not_found&, boost::vertex_index_t>, boost::default_color_type, boost::default_color_type&>, Reference = boost::default_color_type&, K = void*, V = boost::default_color_type]' ./boost-1_33_1/boost/graph/depth_first_search.hpp:197: instantiated from 'void boost::depth_first_search(const VertexListGraph&, DFSVisitor, ColorMap, typename boost::graph_traits<G>::vertex_descriptor) [with VertexListGraph = boost::adjacency_list<boost::setS, boost::listS, boost::bidirectionalS, myclass::my_property_bundle, boost::no_property, boost::no_property, boost::listS>, DFSVisitor = boost::topo_sort_visitor<std::back_insert_iterator<std::vector<void*, std::allocator<void*> > > >, ColorMap = boost::iterator_property_map<__gnu_cxx::__normal_iterator<boost::default_color_type*, std::vector<boost::default_color_type, std::allocator<boost::default_color_type> > >, boost::adj_list_vertex_property_map<boost::adjacency_list<boost::setS, boost::listS, boost::bidirectionalS, myclass::my_property_bundle, boost::no_property, boost::no_property, boost::listS>, boost::detail::error_property_not_found, const boost::detail::error_property_not_found&, boost::vertex_index_t>, boost::default_color_type, boost::default_color_type&>]' ./boost-1_33_1/boost/graph/depth_first_search.hpp:246: instantiated from 'static void boost::detail::dfs_dispatch<boost::detail::error_property_not_found>::apply(const VertexListGraph&, DFSVisitor, Vertex, const boost::bgl_named_params<P, T, R>&, boost::detail::error_property_not_found) [with VertexListGraph = boost::adjacency_list<boost::setS, boost::listS, boost::bidirectionalS, myclass::my_property_bundle, boost::no_property, boost::no_property, boost::listS>, Vertex = void*, DFSVisitor = boost::topo_sort_visitor<std::back_insert_iterator<std::vector<void*, std::allocator<void*> > > >, P = boost::topo_sort_visitor<std::back_insert_iterator<std::vector<void*, std::allocator<void*> > > >, T = boost::graph_visitor_t, R = boost::bgl_named_params<int, boost::buffer_param_t, boost::no_property>]' ./boost-1_33_1/boost/graph/depth_first_search.hpp:324: instantiated from 'void boost::depth_first_search(const VertexListGraph&, const boost::bgl_named_params<P, T, R>&) [with VertexListGraph = boost::adjacency_list<boost::setS, boost::listS, boost::bidirectionalS, myclass::my_property_bundle, boost::no_property, boost::no_property, boost::listS>, P = boost::topo_sort_visitor<std::back_insert_iterator<std::vector<void*, std::allocator<void*> > > >, T = boost::graph_visitor_t, R = boost::bgl_named_params<int, boost::buffer_param_t, boost::no_property>]' ./boost-1_33_1/boost/graph/topological_sort.hpp:64: instantiated from 'void boost::topological_sort(VertexListGraph&, OutputIterator, const boost::bgl_named_params<P, T, R>&) [with VertexListGraph = boost::adjacency_list<boost::setS, boost::listS, boost::bidirectionalS, myclass::my_property_bundle, boost::no_property, boost::no_property, boost::listS>, OutputIterator = std::back_insert_iterator<std::vector<void*, std::allocator<void*> > >, P = int, T = boost::buffer_param_t, R = boost::no_property]' ./boost-1_33_1/boost/graph/topological_sort.hpp:70: instantiated from 'void boost::topological_sort(VertexListGraph&, OutputIterator) [with VertexListGraph = boost::adjacency_list<boost::setS, boost::listS, boost::bidirectionalS, myclass::my_property_bundle, boost::no_property, boost::no_property, boost::listS>, OutputIterator = std::back_insert_iterator<std::vector<void*, std::allocator<void*> > >]' [ User code instantiations snipped] ./boost-1_33_1/boost/property_map.hpp:349: error: no match for 'operator+' in '((const boost::iterator_property_map<__gnu_cxx::__normal_iterator<boost::default_color_type*, std::vector<boost::default_color_type, std::allocator<boost::default_color_type> > >, boost::adj_list_vertex_property_map<boost::adjacency_list<boost::setS, boost::listS, boost::bidirectionalS, myclass::my_property_bundle, boost::no_property, boost::no_property, boost::listS>, boost::detail::error_property_not_found, const boost::detail::error_property_not_found&, boost::vertex_index_t>, boost::default_color_type, boost::default_color_type&>*)this)->boost::iterator_property_map<__gnu_cxx::__normal_iterator<boost::default_color_type*, std::vector<boost::default_color_type, std::allocator<boost::default_color_type> > >, boost::adj_list_vertex_property_map<boost::adjacency_list<boost::setS, boost::listS, boost::bidirectionalS, myclass::my_property_bundle, boost::no_property, boost::no_property, boost::listS>, boost::detail::error_property_not_found, const boost::detail::error_property_not_found&, boost::vertex_index_t>, boost::default_color_type, boost::default_color_type&>::iter + boost::get [with PropertyMap = boost::adj_list_vertex_property_map<boost::adjacency_list<boost::setS, boost::listS, boost::bidirectionalS, myclass::my_property_bundle, boost::no_property, boost::no_property, boost::listS>, boost::detail::error_property_not_found, const boost::detail::error_property_not_found&, boost::vertex_index_t>, Reference = const boost::detail::error_property_not_found&, K = void*](((const boost::put_get_helper<const boost::detail::error_property_not_found&, boost::adj_list_vertex_property_map<boost::adjacency_list<boost::setS, boost::listS, boost::bidirectionalS, myclass::my_property_bundle, boost::no_property, boost::no_property, boost::listS>, boost::detail::error_property_not_found, const boost::detail::error_property_not_found&, boost::vertex_index_t> >&)((const boost::put_get_helper<const boost::detail::error_property_not_found&, boost::adj_list_vertex_property_map<boost::adjacency_list<boost::setS, boost::listS, boost::bidirectionalS, myclass::my_property_bundle, boost::no_property, boost::no_property, boost::listS>, boost::detail::error_property_not_found, const boost::detail::error_property_not_found&, boost::vertex_index_t> >*)(&((const boost::iterator_property_map<__gnu_cxx::__normal_iterator<boost::default_color_type*, std::vector<boost::default_color_type, std::allocator<boost::default_color_type> > >, boost::adj_list_vertex_property_map<boost::adjacency_list<boost::setS, boost::listS, boost::bidirectionalS, myclass::my_property_bundle, boost::no_property, boost::no_property, boost::listS>, boost::detail::error_property_not_found, const boost::detail::error_property_not_found&, boost::vertex_index_t>, boost::default_color_type, boost::default_color_type&>*)this)->boost::iterator_property_map<__gnu_cxx::__normal_iterator<boost::default_color_type*, std::vector<boost::default_color_type, std::allocator<boost::default_color_type> > >, boost::adj_list_vertex_property_map<boost::adjacency_list<boost::setS, boost::listS, boost::bidirectionalS, myclass::my_property_bundle, boost::no_property, boost::no_property, boost::listS>, boost::detail::error_property_not_found, const boost::detail::error_property_not_found&, boost::vertex_index_t>, boost::default_color_type, boost::default_color_type&>::index))), ((void* const&)((void* const*)(& v))))' ./lib/gcc/i686-pc-linux-gnu/4.1.2/../../../../include/c++/4.1.2/bits/stl_iterator.h:703: note: candidates are: __gnu_cxx::__normal_iterator<_Iterator, _Container> __gnu_cxx::__normal_iterator<_Iterator, _Container>::operator+(const typename std::iterator_traits<_Iter>::difference_type&) const [with _Iterator = boost::default_color_type*, _Container = std::vector<boost::default_color_type, std::allocator<boost::default_color_type> >] ./lib/gcc/i686-pc-linux-gnu/4.1.2/../../../../include/c++/4.1.2/bits/stl_bvector.h:353: note: std::_Bit_const_iterator std::operator+(ptrdiff_t, const std::_Bit_const_iterator&) ./lib/gcc/i686-pc-linux-gnu/4.1.2/../../../../include/c++/4.1.2/bits/stl_bvector.h:267: note: std::_Bit_iterator std::operator+(ptrdiff_t, const std::_Bit_iterator&)

2 3

Newbie question: IPC
by Stew Paddaso 05 Jun '07

05 Jun '07

Does boost currently provide facilities for named pipes and/or shared memory between processes? I didn't see any reference to it after looking at this webpage: http://www.boost.org/libs/libraries.htm After doing a Google search, I noticed that the shmem library appears to have been accepted after review, but it is not listed on the page I referenced above. Thanks.

3 2

Boost Python: Howto wrap "out" arguments of a methode
by Alexander Eisenhuth 05 Jun '07

05 Jun '07

How to wrap methode Get with Boost.Python? class MyClass { public: MyClass(); void GetX(double &pos_x); [...] I'v tried it with: .def( "GetX" , &::MyClass::GetX , bp::arg("") , bp::return_value_policy<bp::return_arg<1>() >() But when I try it in python: Boost.Python.ArgumentError: Python argument types in MyClass.GetX(MyClass, int) did not match C++ signature: GetX(class MyClass::LedPosition_C {lvalue}, int {lvalue} ) Any ideas? Thanks Alexander

2 1

[boost.intrusive] Assertion failure with SunCC
by Zeljko Vrba 05 Jun '07

05 Jun '07

The following simple program crashes with assertion failure when compiled under Solaris 11 with SunCC: Sun C++ 5.8 Patch 121018-10 2007/02/21 Assertion failed: node_algorithms::unique(to_insert), file boost/boost/intrusive/list.hpp, line 168 I'm using the latest Boost.Intrusive from CVS (snapshot taken 2007-06-03). I have tracked the problem, but I don't know wheter it's the code or compiler problem; see below the code for cause. == Begin code // Program to demonstrate a bug with SunCC and member hooks. #include <boost/intrusive/list.hpp> struct klass { void *data_klass; boost::intrusive::list_member_hook<> hook_; typedef boost::intrusive::list< boost::intrusive::list_member_hook<>::value_traits< klass, &klass::hook_>, false> list; }; static klass Gd; static klass::list Gl; int main(void) { => Gl.push_back(Gd); return 0; } == End code When the program is started, the hook's prev_ and next_ members are initialized correctly to &Gd.hook_ (0x8062dd8). The member_value_traits instance is by dbx resolved to boost::intrusive::detail::member_value_traits< klass,boost::intrusive::list_member_hook< (boost::intrusive::linking_policy)1,void*>, klass::hook_>::to_node_ptr ^^^^^^^^^^^^ Corresponds to the template P parameter. The statement MemberHookType* result = &(value.*P); sets result to 0x8062dd4 (4 bytes off from the hooks address). Finally, in push_back method, the to_insert value receives 0x8062dd4 which equals &Gd (ie. it points to the start of the object) instead of &Gd.hook_. Should this be reported as a compiler bug? BTW, I'll try using base hooks as a workaround. (PS: the code works fine with gcc4.2)

5 13

lib folder?
by Mike Wyatt 05 Jun '07

05 Jun '07

I just installed MinGW and Boost. The boost_1_34_0 folder I extracted from the downloaded zip did not contain a "lib" folder, which is referred to in the Getting Started for Windows guide (http://www.boost.org/more/getting_started/windows.html) I've already built all the Boost libraries, so I'm guessing that I need to copy the lib folder from the new stage folder into the boost root. Is that correct? Also, I built bjam with the "mingw" toolset, and Boost with "gcc". Is that a problem? Here are the commands I ran: *Building bjam*: c:\Program Files\boost_1_34_0\tools\jam\src\build mingw *Building Boost*: c:\Program Files\boost_1_34_0\bjam --build-dir=build --toolset=gcc stage Does that make sense? Am I doing everything right, so far?

2 2

Boost 1.34 and VC++ x64
by Cory Nelson 05 Jun '07

05 Jun '07

This was pretty straightforward for 1.33, but 1.34 using BB2 seems to have changed things a bit. There doesn't seem to be any documentation on compiling 1.34 for x64 with VC++ - can anyone offer some insight?

6 8

program_options linking problem
by Moritz Moeller 05 Jun '07

05 Jun '07

I've got a linking issue with this lib on Linux. If I don't specify -lboost_program_options, I naturally get several pages of missing symbols. No surprise there. However, if I /do/ specify it, I still get /some/!? ________________________________________________________________________________ Creating bin/baker g++ obj/mesh.o obj/dnHumpBaker.o -L/hosts/norwich/user_data/ritz/usr/local/3delight-6.5.24/Linux-x86_64/lib -l3delight -lboost_program_options -o bin/baker obj/dnHumpBaker.o(.text+0xb84): In function `main': dnHumpBaker.cpp: undefined reference to `boost::program_options::options_description::options_description(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned int)' obj/dnHumpBaker.o(.gnu.linkonce.t._ZN5boost15program_options25basic_command_line_parserIcE7optionsERKNS0_19options_descriptionE[boost::program_options::basic_command_line_parser<char>::options(boost::program_options::options_description const&)]+0x15): In function `boost::program_options::basic_command_line_parser<char>::options(boost::program_options::options_description const&)': dnHumpBaker.cpp: undefined reference to `boost::program_options::detail::cmdline::set_options_description(boost::program_options::options_description const&)' obj/dnHumpBaker.o(.gnu.linkonce.t._ZN5boost15program_options25basic_command_line_parserIcE10positionalERKNS0_30positional_options_descriptionE[boost::program_options::basic_command_line_parser<char>::positional(boost::program_options::positional_options_description const&)]+0x5): In function `boost::program_options::basic_command_line_parser<char>::positional(boost::program_options::positional_options_description const&)': dnHumpBaker.cpp: undefined reference to `boost::program_options::detail::cmdline::set_positional_options(boost::program_options::positional_options_description const&)' obj/dnHumpBaker.o(.gnu.linkonce.t._ZN5boost15program_options25basic_command_line_parserIcE3runEv[boost::program_options::basic_command_line_parser<char>::run()]+0x40): In function `boost::program_options::basic_command_line_parser<char>::run()': dnHumpBaker.cpp: undefined reference to `boost::program_options::detail::cmdline::run()' obj/dnHumpBaker.o(.gnu.linkonce.t._ZN5boost15program_options25basic_command_line_parserIcEC1EiPPc[boost::program_options::basic_command_line_parser<char>::basic_command_line_parser(int, char**)]+0x3e): In function `boost::program_options::basic_command_line_parser<char>::basic_command_line_parser(int, char**)': dnHumpBaker.cpp: undefined reference to `boost::program_options::detail::cmdline::cmdline(std::vector<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&)' collect2: ld returned 1 exit status make: *** [baker] Error 1

1 0

BOOST vs ACE
by dhruva 05 Jun '07

05 Jun '07

Hi, I am new to BOOST and to ACE. Pardon me if this question appears stupid for the seasones BOOST/ACE developers/users. From what little I know of the two frameworks, I am noticing many overlapping functionalities (shared memory, streams, threads). Is there some place/someone that can provide me a top level differences and situations that makes one framework more suited than the other. Any help or pointers is greatly appreciated. Thanks in advance. with best regards, dhruva -- Dhruva Krishnamurthy Contents reflect my personal views only!

2 1

Pb compiling spirit with Sun C++ 5.5
by Christophe Delarue 05 Jun '07

05 Jun '07

HI boost users, We are trying to compile boost spirit to use the xml serialization, but we got compiler error on : CC -V CC: Sun C++ 5.5 2003/03/12 + /Soft/sunstudio/8/bin/CC +d -g -xs -mt -DBOOST_ALL_DYN_LINK=1 + -DBOOST_ALL_NO_LIB=1 -I. -I/Home/ut0bcm/Boost/boost_1_34_0 + -I/Soft/sunstudio/8/prod/include/CC/stlport4 -I/usr/include + -library=stlport4 -c -o bin.v2/libs/wave/build/sun/debug/threading-multi/instantiate_cpp_exprgrammar.o libs/wave/src/instantiate_cpp_exprgrammar.cpp "./boost/spirit/phoenix/actor.hpp", line 345: Error: Could not find a match for phoenix::actor<phoenix::BaseT>::operator()(phoenix::A&) const. "./boost/spirit/phoenix/actor.hpp", line 354: Error: Could not find a match for phoenix::actor<phoenix::BaseT>::operator()(phoenix::A&, phoenix::B&) const. "./boost/spirit/phoenix/actor.hpp", line 354: Error: Too many args in template, from phoenix::B on ignored. "./boost/spirit/phoenix/actor.hpp", line 363: Error: Could not find a match for phoenix::actor<phoenix::BaseT>::operator()(phoenix::A&, phoenix::B&, phoenix::C&) const. "./boost/spirit/phoenix/actor.hpp", line 363: Error: Too many args in template, from phoenix::B on ignored. "./boost/spirit/phoenix/actor.hpp", line 373: Error: Could not find a match for phoenix::actor<phoenix::BaseT>::operator()(phoenix::A&, phoenix::B&, phoenix::C&, phoenix::D&) const. "./boost/spirit/phoenix/actor.hpp", line 373: Error: Too many args in template, from phoenix::B on ignored. "./boost/spirit/phoenix/actor.hpp", line 382: Error: Could not find a match for phoenix::actor<phoenix::BaseT>::operator()(phoenix::A&, phoenix::B&, phoenix::C&, phoenix::D&, phoenix::E&) const. "./boost/spirit/phoenix/actor.hpp", line 382: Error: Too many args in template, from phoenix::B on ignored. "./boost/spirit/phoenix/actor.hpp", line 397: Error: Could not find a match for phoenix::actor<phoenix::BaseT>::operator()(phoenix::A&, phoenix::B&, phoenix::C&, phoenix::D&, phoenix::E&, phoenix::F&) const. "./boost/spirit/phoenix/actor.hpp", line 397: Error: Too many args in template, from phoenix::B on ignored. "./boost/spirit/phoenix/actor.hpp", line 589: Error: Could not find a match for phoenix::actor<phoenix::BaseT>::operator()(const phoenix::unpack_tuple<phoenix::actor<phoenix::BaseT>::TupleT>&) const. -- -- Christophe Delarue mailto:christophe.delarue@gmail.com 06 12 95 49 56

1 0

Formatting and passing variable parameters.
by Prasanta K Chakravarty 05 Jun '07

05 Jun '07

Hi, 1) I have to generate unique id on the basis of file name and line no. For that I am using macros __FILE__ and __LINE__. But __FILE__ is giving full path with the file name and two double quotes at the begining and end(for example, "C:\Project\Test\log.cfg" ). I need to get the unique id in the format as <file name>_<line no>. For example if above is the file description and let line no is 11, then the unique id would be log_11. Please suggest. 2) I have to pass variable no of arguments in the macro. So, I want to use Boost PARAM macro. For example, if LIST is the macro name and I want to call it as LIST(MSG_ID, "good", 5, "failed", "50%", 10); Here parameters are of different types, only the fist parameter is fixed that is string type and always with same variable name. Other parameters will vary. Please help me out in making the macro with variable no. of parameters. Please suggest, Thanks Prasanta

1 0

[boost] [bimap] New Version
by Matias Capeletto 05 Jun '07

05 Jun '07

Hello boost, I have released a new version of the Boost.Bimap. The main attraction of this new release is the possibility to add information about each relation. I have been working very hard to ensure that Bimap works well with the others boost libraries. I have added new sections to the "Bimap and Boost" docs to show how to combine them. For example, from Bimap and Boost.Foreach: ------------------------------------------------------------------------------------------------------ typedef bimap< int, string > bm_type; bm_type bm; assign::insert( bm ) (1,"one") (2,"two") (3,"three"); BOOST_FOREACH( bm_type::right_const_reference p, bm.right ) { std::cout << p.first << " ---> " << p.second << std::endl; } ------------------------------------------------------------------------------------------------------ prints: ------------------------------------------------------------------------------------------------------ one ---> 1 three ---> 3 two ---> 2 ------------------------------------------------------------------------------------------------------ ================================================== I really need feedback! ================================================== If you are using this library please send me your comments (if you want by private email: matias <dot> capeletto <at> gmail <dot> com ) Library sources are in the vault: ---------------------------------------------------------------------------------------------------- http://tinyurl.com/2t8c87 Documentation can be viewed online here: ---------------------------------------------------------------------------------------------------- http://tinyurl.com/22sja5 Or can be downloaded from: ---------------------------------------------------------------------------------------------------- http://tinyurl.com/22jfdf Main changes ---------------------------------------------------------------------------------------------------- Lib: * Added support for information about the relations * Added range_type and const_range_type typedef to indexed views * Change the way you tag the collections. * hard implementation decision * Some small bug fixes Docs: * New relation and pair layout diagram * New section: Additional information * More examples in Bimap and Boost * New section: Bimap and Boost.Xpressive * New section: Bimap and Boost.Typeof * New section: Bimap and Boost.Foreach * Update the reference Comments are welcome Best regards Matias

1 1

Boost python: cannot compile lambda
by chun ping wang 04 Jun '07

04 Jun '07

---------- Forwarded message ---------- From: chun ping wang <cablepuff(a)gmail.com> Date: May 31, 2007 1:24 PM Subject: Boost python: cannot compile lambda To: boost-users(a)list.boost.org hi , while trying to compile boost.python i get these following errors. ar: creating ./lib/libOperatingSystem.a ranlib ./lib/libOperatingSystem.a rm -f ./lib/DeadLockAvoid.o ./lib/ContainerOperation.o make[1]: Leaving directory `C:/CPW/cs_classes' g++.exe -Wall -D__DEBUG__ -c ./cs540/c++/DeadLockPythonWrapper.cpp -o ./boost_py thon/DeadLockPythonWrapper.o -I"C:/Boost/include/boost_1_34" -I"C:/Python25/inc lude" -I"./Scripts" -ansi -fexceptions -fverbose-asm -fexpensive-optimization s -O3 -pg -g3 In file included from ./cs540/c++/DeadLockPythonWrapper.cpp:7: ./cs540/c++/cppdef/ContainerOperation.cpp: In function `CONT<T, std::allocator<_ CharT> > operator-(CONT<T, std::allocator<_CharT> >, CONT<T, std::allocator<_Cha rT> >)': ./cs540/c++/cppdef/ContainerOperation.cpp:32: error: `_1' undeclared (first use this function) ./cs540/c++/cppdef/ContainerOperation.cpp:32: error: (Each undeclared identifier is reported only once for each function it appears in.) ./cs540/c++/cppdef/ContainerOperation.cpp:32: error: `_2' undeclared (first use this function) ./cs540/c++/cppdef/ContainerOperation.cpp: In function `CONT<T, std::allocator<_ CharT> > operator+(CONT<T, std::allocator<_CharT> >, CONT<T, std::allocator<_Cha rT> >)': ./cs540/c++/cppdef/ContainerOperation.cpp:44: error: `_1' undeclared (first use this function) ./cs540/c++/cppdef/ContainerOperation.cpp:44: error: `_2' undeclared (first use this function) ./cs540/c++/cppdef/ContainerOperation.cpp: In function `CONT<T, std::allocator<_ CharT> > operator*(CONT<T, std::allocator<_CharT> >, CONT<T, std::allocator<_Cha rT> >)': ./cs540/c++/cppdef/ContainerOperation.cpp:56: error: `_1' undeclared (first use this function) ./cs540/c++/cppdef/ContainerOperation.cpp:56: error: `_2' undeclared (first use this function) ./cs540/c++/cppdef/ContainerOperation.cpp: In function `CONT<T, std::allocator<_ CharT> > operator/(CONT<T, std::allocator<_CharT> >, CONT<T, std::allocator<_Cha rT> >)': ./cs540/c++/cppdef/ContainerOperation.cpp:68: error: `_1' undeclared (first use this function) ./cs540/c++/cppdef/ContainerOperation.cpp:68: error: `_2' undeclared (first use this function) ./cs540/c++/cppdef/ContainerOperation.cpp: In function `CONT<T, std::allocator<_ CharT> > operator%(CONT<T, std::allocator<_CharT> >, CONT<T, std::allocator<_Cha rT> >)': ./cs540/c++/cppdef/ContainerOperation.cpp:80: error: `_1' undeclared (first use this function) ./cs540/c++/cppdef/ContainerOperation.cpp:80: error: `_2' undeclared (first use this function) Is there a way to integerate lambda into boost python. OperatingSystemLib.mak works .. i just can't put lambda inside implementation file for boost.python. thanks.

2 2

[program_options] allow_unregistered() function for parse_environment
by Chris Weed 04 Jun '07

04 Jun '07

Hi, I would like to parse the environment variables on my system, but also allow unregistered options, similar to <http://www.boost.org/doc/html/program_options/howto.html#id1593176> with the command line parser. Is this possible? I can't seem to get it to work. Thanks, Chris

1 0

[multi_index] MSVC 8.0 visualizers for boost::multi_index_container
by Filip Konvička 04 Jun '07

04 Jun '07

Hello all, here is another version of MSVC 2005 visualizers for multi_index_container. Thanks to Joaquín for his invaluable support! This version supports sequenced, random_access, ordered and hashed indices. Hashed indices are visualized including the internal bucket structure, indicating empty bucket, single-item bucket and multiple-item bucket (see the example below). As in the previous version, contents of autoexp.dat.txt go into Microsoft Visual Studio 8\Common7\Packages\Debugger\autoexp.dat For your container to be visualized, you need to call the VISUALIZE_MULTI_INDEX_CONTAINER macro at the global namespace level (see the attached example, test2.cpp, and a screenshot of a test2.cpp debugging session, sample_hash.png). I strongly recommend using #define BOOST_MULTI_INDEX_LIMIT_INDEXED_BY_SIZE 5 #define BOOST_MULTI_INDEX_LIMIT_TAG_SIZE 3 #define BOOST_MULTI_INDEX_LIMIT_COMPOSITE_KEY_SIZE 5 in order to reduce symbol name lengths, because otherwise the resulting symbols are too long for the visualizer to work (this typically happens with more than 1 index in a multi_index_container). Also beware, using type hiding techniques described at http://boost.org/libs/multi_index/doc/compiler_specifics.html#type_hiding will cause visualizers to fail. Enjoy! Cheers, Filip ;------------------------------------ ; boost::multi_index_container - base boost::multi_index::multi_index_container<*,*,*>{ preview(#($c.node_count, " items (multi_index_container)")) children( #( data:((msvc_helpers::multi_index_helper_2<boost::multi_index::multi_index_container<$T1,$T2,$T3> >*)&$c)->header, original members: [$c,!] ) ) } ;----------------------------------------------- ; boost::multi_index_container - sequenced index boost::multi_index::detail::header_holder<boost::multi_index::detail::sequenced_index_node<*>,*>{ preview(#("sequenced index")) children( #( #list( head : *(((boost::multi_index::detail::sequenced_index_node_impl*)(boost::multi_index::detail::sequenced_index_node_trampoline<$T1>*)($c.member))->next_), size : (($T2*)&$c)->node_count, next : next_ ) : ((msvc_helpers::multi_index_helper<boost::multi_index::detail::sequenced_index_node<$T1> >*)(boost::multi_index::detail::sequenced_index_node<$T1>*)(boost::multi_index::detail::sequenced_index_node_trampoline<$T1>*)(&$e))->value ) ) } ;--------------------------------------------------- ; boost::multi_index_container - random access index boost::multi_index::detail::header_holder<boost::multi_index::detail::random_access_index_node<*>,*>{ preview(#("random access index")) children( #( #array( expr: (($T2*)&$c)->ptrs.spc.data_[$i], size: (($T2*)&$c)->node_count ) : ((msvc_helpers::multi_index_helper<boost::multi_index::detail::random_access_index_node<$T1> >*)(boost::multi_index::detail::random_access_index_node<$T1>*)(boost::multi_index::detail::random_access_index_node_trampoline<$T1>*)&$e)->value ) ) } ;-------------------------------------------- ; boost::multi_index_container - hashed index boost::multi_index::detail::header_holder<boost::multi_index::detail::hashed_index_node<*>,*>{ preview(#("hashed index - ", (($T2*)&$c)->node_count, " in ", (($T2*)&$c)->buckets.size_, " buckets")) children( #( #array( expr : (($T2*)&$c)->buckets.spc.data_[$i], size : (($T2*)&$c)->buckets.size_ ) : (msvc_helpers::multi_index_helper_3<boost::multi_index::detail::hashed_index_node<$T1> >*)(void*)&$e ) ) } msvc_helpers::multi_index_helper_3<boost::multi_index::detail::hashed_index_node<*> >{ preview(#if ( ((boost::multi_index::detail::hashed_index_node_impl*)&$c)->next_==((boost::multi_index::detail::hashed_index_node_impl*)&$c) ) ; no data at all (#("---")) #else ( #if ( ((boost::multi_index::detail::hashed_index_node_impl*)&$c)->next_->next_==((boost::multi_index::detail::hashed_index_node_impl*)&$c) ) ( ; 1 item: preview as _value_ #( ((msvc_helpers::multi_index_helper<boost::multi_index::detail::hashed_index_node<$T1> >*)(boost::multi_index::detail::hashed_index_node<$T1>*)(boost::multi_index::detail::hashed_index_node_trampoline<$T1>*)(((boost::multi_index::detail::hashed_index_node_impl*)&$c)->next_))->value) ) #else ( ; multiple items: preview as [_value_ ...] #("[", ((msvc_helpers::multi_index_helper<boost::multi_index::detail::hashed_index_node<$T1> >*)(boost::multi_index::detail::hashed_index_node<$T1>*)(boost::multi_index::detail::hashed_index_node_trampoline<$T1>*)(((boost::multi_index::detail::hashed_index_node_impl*)&$c)->next_))->value, " ...]") ) ) ) children( #( ; multiple items: view as list #list( head: ((boost::multi_index::detail::hashed_index_node_impl*)&$c)->next_, next: next_, skip: ((boost::multi_index::detail::hashed_index_node_impl*)&$c) ) : ((msvc_helpers::multi_index_helper<boost::multi_index::detail::hashed_index_node<$T1> >*)(boost::multi_index::detail::hashed_index_node<$T1>*)(boost::multi_index::detail::hashed_index_node_trampoline<$T1>*)(&$e))->value ) ) } ;--------------------------------------------- ; boost::multi_index_container - ordered index boost::multi_index::detail::header_holder<boost::multi_index::detail::ordered_index_node<*>,*>{ preview(#("ordered index")) children( #( #tree( head : *(boost::multi_index::detail::ordered_index_node_compressed_base*)(boost::multi_index::detail::ordered_index_node_impl*)(void*)(((boost::multi_index::detail::ordered_index_node_trampoline<$T1>*)($c.member))->parentcolor_&~1U), size : (($T2*)&$c)->node_count, left : left_, right : right_, skip : 0 ) : ((msvc_helpers::multi_index_helper<boost::multi_index::detail::ordered_index_node<$T1> >*)(boost::multi_index::detail::ordered_index_node<$T1>*)(boost::multi_index::detail::ordered_index_node_trampoline<$T1>*)(&$e))->value ) ) } #define BOOST_MULTI_INDEX_LIMIT_INDEXED_BY_SIZE 5 #define BOOST_MULTI_INDEX_LIMIT_TAG_SIZE 3 #define BOOST_MULTI_INDEX_LIMIT_COMPOSITE_KEY_SIZE 5 #include "mic_visualizer.hpp" #include <string> #include <boost/multi_index_container.hpp> #include <boost/multi_index/sequenced_index.hpp> #include <boost/multi_index/hashed_index.hpp> #include <boost/multi_index/ordered_index.hpp> #include <boost/multi_index/random_access_index.hpp> using namespace boost::multi_index; using std::wstring; using namespace std; struct test { wstring x; wstring y; test(wchar_t const *str, wchar_t const *str2=L"def") : x(str), y(str2) {} bool operator<(test const& other) const { return x<other.x; } bool operator==(test const& other) const { return x==other.x; } }; namespace boost { inline std::size_t hash_value(test const& t) { return hash_value(t.x); } } typedef multi_index_container<test, indexed_by<hashed_non_unique<identity<test> > > > cont; VISUALIZE_MULTI_INDEX_CONTAINER(cont); int wmain() { cont test_cont; test_cont.insert(test(L"aaa")); test_cont.insert(test(L"aaa", L"other")); test_cont.insert(test(L"aac")); return 0; // see screenshoxt } #ifndef MIC_VISUALIZER_HPP #define MIC_VISUALIZER_HPP #if !defined(_DEBUG)||!defined(_MSC_VER)||(_MSC_VER<1400) #define VISUALIZE_MULTI_INDEX_CONTAINER(Type) /* empty def */ #else namespace msvc_helpers { template<typename T> struct multi_index_helper { }; template<typename T> struct multi_index_helper_2 { }; template<typename T> struct multi_index_helper_3 { }; } #define __VISUALIZE_MIC_INDEX_DEF(Type) \ boost::multi_index::detail::multi_index_node_type< \ Type::value_type, \ Type::index_specifier_type_list, \ std::allocator<Type::value_type> >::type /// Enables MSVC visualizers for multi_index_container Type #define VISUALIZE_MULTI_INDEX_CONTAINER(Type) \ namespace msvc_helpers { \ template<> \ struct multi_index_helper_2<Type> { \ typedef __VISUALIZE_MIC_INDEX_DEF(Type) index_node_type; \ typedef \ boost::base_from_member< \ boost::detail::allocator::rebind_to< \ std::allocator<Type::value_type>, \ index_node_type \ >::type> \ base_type; \ typedef \ boost::multi_index::detail::header_holder< \ index_node_type, Type> \ header_holder_type; \ typedef \ boost::multi_index::detail::multi_index_base_type< \ Type::value_type, \ Type::index_specifier_type_list, \ std::allocator<Type::value_type> >::type \ index_type; \ /* mimic multi_index_container layout */ \ base_type base; \ header_holder_type header; \ index_type index; \ unsigned int node_count; \ /* ensure that the debugger sees this template instance */ \ static void get() { \ multi_index_helper_2<Type> *ensure_inst=0; \ } \ }; \ template<> \ struct multi_index_helper_3<__VISUALIZE_MIC_INDEX_DEF(Type)> { \ /* ensure that the debugger sees this template instance */ \ static void get() { \ multi_index_helper_3< \ __VISUALIZE_MIC_INDEX_DEF(Type)> *ensure_inst=0; \ } \ }; \ template<> \ struct multi_index_helper<__VISUALIZE_MIC_INDEX_DEF(Type)> { \ typedef __VISUALIZE_MIC_INDEX_DEF(Type) index_node_type; \ /* mimic index_node_base<Type::value_type> layout */ \ Type::value_type value; \ /* ensure that the debugger sees this template instance */ \ static void get() { \ multi_index_helper<index_node_type> *ensure_inst=0; \ } \ }; \ } #endif #endif

1 0

[mpi] cvs, 2 errors, build missing -fPIC and install duplicate target
by Chris Fairles 04 Jun '07

04 Jun '07

--build-configuration notice: found boost-build.jam at /home/cfairles/repos/boost/boost-build.jam notice: loading Boost.Build from /home/cfairles/repos/boost/tools/build/v2 searching "/etc" "/home/cfairles" "/usr/share/boost-build" "/home/cfairles/repos/boost/tools/build/v2" "/home/cfairles/repos/boost/tools/build/v2/kernel" "/home/cfairles/repos/boost/tools/build/v2/util" "/home/cfairles/repos/boost/tools/build/v2/build" "/home/cfairles/repos/boost/tools/build/v2/tools" "/home/cfairles/repos/boost/tools/build/v2/new" "/home/cfairles/repos/boost/tools/build/v2/." for "site-config.jam" notice: loading site-config.jam from /home/cfairles/repos/boost/tools/build/v2/site-config.jam Loading explicitly specifier user configuration file: user-config.jam notice: using gcc libraries :: <toolset>gcc-4.1.1 :: /usr/lib64/ccache/bin /usr/lib64/ccache/lib /usr/lib64/ccache/lib32 /usr/lib64/ccache/lib64 notice: using gcc archiver :: <toolset>gcc-4.1.1 :: ar warning: toolset gcc initialization: can't find tool windres warning: initialized from notice: using rc compiler :: <toolset>gcc-4.1.1 :: as notice: looking for python 2.4 notice: searching for python binaries in /usr/bin notice: trying Python interpreter command /usr/bin/python2.4 notice: /usr/bin/python2.4 invokes actual Python (major,minor) version 2.4 notice: qualifying Python interpreter found notice: Python interpreter command is /usr/bin/python2.4 notice: Python include path is /usr/include/python2.4 notice: Python library path is /usr/lib/python2.4/config ===============MPI Auto-configuration=============== Found recent LAM-MPI or Open MPI wrapper compiler: mpic++ MPI compilation flags: -I/usr/include/openmpi -I/usr/include/openmpi/openmpi -m64 -pthread MPI link flags: -m64 -pthread -L/usr/lib64/openmpi -lmpi_cxx -lmpi -lorte -lopal -ldl -Wl,--export-dynamic -lnsl -lutil -lm -ldl MPI build features: <include>/usr/include/openmpi <include>/usr/include/openmpi/openmpi <threading>multi <cxxflags>-m64 <threading>multi <library-path>/usr/lib64/openmpi <find-shared-library>mpi_cxx <find-shared-library>mpi <find-shared-library>orte <find-shared-library>opal <find-shared-library>dl <find-shared-library>nsl <find-shared-library>util <find-shared-library>m <find-shared-library>dl <linkflags>-m64 <linkflags>-Wl,--export-dynamic MPI launcher: mpirun -np ==================================================== notice: iostreams: using prebuilt zlib notice: iostreams: using prebuilt bzip2 user-config.jam: using gcc; using python : 2.4 : /usr ; using mpi ; Error #1: Building with: ./tools/jam/src/bin.linux/bjam -d+2 -sICU_PATH=/usr variant=release threading=multi --layout=system --user-config=user-config.jam --with-date_time --with-filesystem --with-function_types --with-iostreams --with-mpi --with-program_options --with-python --with-serialization --with-signals --with-system --with-thread --with-test I obtained the following linker error. /usr/bin/ld: bin.v2/libs/mpi/build/gcc-4.1.1/release/link-static/threading-multi/collectives.o: relocation R_X86_64_32 against `__dso_handle' can not be used when making a shared object; recompile with -fPIC Solved by adding using gcc : : : <cxxflags>-fPIC ; to user-config.jam Error #2: ./tools/jam/src/bin.linux/bjam -d+2 -sICU_PATH=/usr variant=release threading=multi --layout=system --user-config=user-config.jam --prefix=/home/cfairles/usr --exec-prefix=/home/cfairles/usr --libdir=/home/cfairles/usr/lib64 --includedir=/home/cfairles/usr/include --with-date_time --with-filesystem --with-function_types --with-iostreams --with-mpi --with-program_options --with-python --with-serialization --with-signals --with-system --with-thread --with-test install /home/cfairles/repos/boost/tools/build/v2/build/virtual-target.jam:996: in virtual-target.register-actual-name from module virtual-target error: Duplicate name of actual target: <p/home/cfairles/usr/lib64>mpi.so error: previous virtual target { common%common.copy-mpi.so.PYTHON_EXTENSION { gcc%gcc.link.dll-mpi.so.PYTHON_EXTENSION { gcc%gcc.compile.c++-collectives.o.OBJ { python/collectives.cpp.CPP } } { gcc%gcc.compile.c++-py_communicator.o.OBJ { python/py_communicator.cpp.CPP } } { gcc%gcc.compile.c++-datatypes.o.OBJ { python/datatypes.cpp.CPP } } { gcc%gcc.compile.c++-documentation.o.OBJ { python/documentation.cpp.CPP } } { gcc%gcc.compile.c++-py_environment.o.OBJ { python/py_environment.cpp.CPP } } { gcc%gcc.compile.c++-py_exception.o.OBJ { python/py_exception.cpp.CPP } } { gcc%gcc.compile.c++-module.o.OBJ { python/module.cpp.CPP } } { gcc%gcc.compile.c++-py_request.o.OBJ { python/py_request.cpp.CPP } } { gcc%gcc.compile.c++-skeleton_and_content.o.OBJ { python/skeleton_and_content.cpp.CPP } } { gcc%gcc.compile.c++-status.o.OBJ { python/status.cpp.CPP } } { gcc%gcc.compile.c++-py_timer.o.OBJ { python/py_timer.cpp.CPP } } { gcc%gcc.link.dll-libboost_mpi_python-mt.so.SHARED_LIB { gcc%gcc.compile.c++-serialize.o.OBJ { python/serialize.cpp.CPP } } { gcc%gcc.link.dll-libboost_python-mt.so.SHARED_LIB { gcc%gcc.compile.c++-numeric.o.OBJ { numeric.cpp.CPP } } { gcc%gcc.compile.c++-list.o.OBJ { list.cpp.CPP } } { gcc%gcc.compile.c++-long.o.OBJ { long.cpp.CPP } } { gcc%gcc.compile.c++-dict.o.OBJ { dict.cpp.CPP } } { gcc%gcc.compile.c++-tuple.o.OBJ { tuple.cpp.CPP } } { gcc%gcc.compile.c++-str.o.OBJ { str.cpp.CPP } } { gcc%gcc.compile.c++-slice.o.OBJ { slice.cpp.CPP } } { gcc%gcc.compile.c++-aix_init_module.o.OBJ { aix_init_module.cpp.CPP } } { gcc%gcc.compile.c++-from_python.o.OBJ { converter/from_python.cpp.CPP } } { gcc%gcc.compile.c++-registry.o.OBJ { converter/registry.cpp.CPP } } { gcc%gcc.compile.c++-type_id.o.OBJ { converter/type_id.cpp.CPP } } { gcc%gcc.compile.c++-enum.o.OBJ { object/enum.cpp.CPP } } { gcc%gcc.compile.c++-class.o.OBJ { object/class.cpp.CPP } } { gcc%gcc.compile.c++-function.o.OBJ { object/function.cpp.CPP } } { gcc%gcc.compile.c++-inheritance.o.OBJ { object/inheritance.cpp.CPP } } { gcc%gcc.compile.c++-life_support.o.OBJ { object/life_support.cpp.CPP } } { gcc%gcc.compile.c++-pickle_support.o.OBJ { object/pickle_support.cpp.CPP } } { gcc%gcc.compile.c++-errors.o.OBJ { errors.cpp.CPP } } { gcc%gcc.compile.c++-module.o.OBJ { module.cpp.CPP } } { gcc%gcc.compile.c++-builtin_converters.o.OBJ { converter/builtin_converters.cpp.CPP } } { gcc%gcc.compile.c++-arg_to_python_base.o.OBJ { converter/arg_to_python_base.cpp.CPP } } { gcc%gcc.compile.c++-iterator.o.OBJ { object/iterator.cpp.CPP } } { gcc%gcc.compile.c++-stl_iterator.o.OBJ { object/stl_iterator.cpp.CPP } } { gcc%gcc.compile.c++-object_protocol.o.OBJ { object_protocol.cpp.CPP } } { gcc%gcc.compile.c++-object_operators.o.OBJ { object_operators.cpp.CPP } } { gcc%gcc.compile.c++-wrapper.o.OBJ { wrapper.cpp.CPP } } { gcc%gcc.compile.c++-import.o.OBJ { import.cpp.CPP } } { gcc%gcc.compile.c++-exec.o.OBJ { exec.cpp.CPP } } } { gcc%gcc.link.dll-libboost_mpi-mt.so.SHARED_LIB { gcc%gcc.compile.c++-broadcast.o.OBJ { broadcast.cpp.CPP } } { gcc%gcc.compile.c++-communicator.o.OBJ { communicator.cpp.CPP } } { gcc%gcc.compile.c++-computation_tree.o.OBJ { computation_tree.cpp.CPP } } { gcc%gcc.compile.c++-content_oarchive.o.OBJ { content_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-environment.o.OBJ { environment.cpp.CPP } } { gcc%gcc.compile.c++-exception.o.OBJ { exception.cpp.CPP } } { gcc%gcc.compile.c++-graph_topology.o.OBJ { graph_topology.cpp.CPP } } { gcc%gcc.compile.c++-group.o.OBJ { group.cpp.CPP } } { gcc%gcc.compile.c++-mpi_datatype_cache.o.OBJ { mpi_datatype_cache.cpp.CPP } } { gcc%gcc.compile.c++-mpi_datatype_oarchive.o.OBJ { mpi_datatype_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-packed_iarchive.o.OBJ { packed_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-packed_oarchive.o.OBJ { packed_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-packed_skeleton_iarchive.o.OBJ { packed_skeleton_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-packed_skeleton_oarchive.o.OBJ { packed_skeleton_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-point_to_point.o.OBJ { point_to_point.cpp.CPP } } { gcc%gcc.compile.c++-request.o.OBJ { request.cpp.CPP } } { gcc%gcc.compile.c++-text_skeleton_oarchive.o.OBJ { text_skeleton_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-timer.o.OBJ { timer.cpp.CPP } } { gcc%gcc.link.dll-libboost_serialization-mt.so.SHARED_LIB { gcc%gcc.compile.c++-basic_archive.o.OBJ { basic_archive.cpp.CPP } } { gcc%gcc.compile.c++-basic_iarchive.o.OBJ { basic_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-basic_iserializer.o.OBJ { basic_iserializer.cpp.CPP } } { gcc%gcc.compile.c++-basic_oarchive.o.OBJ { basic_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-basic_oserializer.o.OBJ { basic_oserializer.cpp.CPP } } { gcc%gcc.compile.c++-basic_pointer_iserializer.o.OBJ { basic_pointer_iserializer.cpp.CPP } } { gcc%gcc.compile.c++-basic_pointer_oserializer.o.OBJ { basic_pointer_oserializer.cpp.CPP } } { gcc%gcc.compile.c++-basic_serializer_map.o.OBJ { basic_serializer_map.cpp.CPP } } { gcc%gcc.compile.c++-basic_text_iprimitive.o.OBJ { basic_text_iprimitive.cpp.CPP } } { gcc%gcc.compile.c++-basic_text_oprimitive.o.OBJ { basic_text_oprimitive.cpp.CPP } } { gcc%gcc.compile.c++-basic_xml_archive.o.OBJ { basic_xml_archive.cpp.CPP } } { gcc%gcc.compile.c++-binary_iarchive.o.OBJ { binary_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-binary_oarchive.o.OBJ { binary_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-codecvt_null.o.OBJ { codecvt_null.cpp.CPP } } { gcc%gcc.compile.c++-extended_type_info.o.OBJ { extended_type_info.cpp.CPP } } { gcc%gcc.compile.c++-extended_type_info_no_rtti.o.OBJ { extended_type_info_no_rtti.cpp.CPP } } { gcc%gcc.compile.c++-extended_type_info_typeid.o.OBJ { extended_type_info_typeid.cpp.CPP } } { gcc%gcc.compile.c++-polymorphic_iarchive.o.OBJ { polymorphic_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-polymorphic_oarchive.o.OBJ { polymorphic_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-stl_port.o.OBJ { stl_port.cpp.CPP } } { gcc%gcc.compile.c++-text_iarchive.o.OBJ { text_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-text_oarchive.o.OBJ { text_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-void_cast.o.OBJ { void_cast.cpp.CPP } } { gcc%gcc.compile.c++-xml_grammar.o.OBJ { xml_grammar.cpp.CPP } } { gcc%gcc.compile.c++-xml_iarchive.o.OBJ { xml_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-xml_oarchive.o.OBJ { xml_oarchive.cpp.CPP } } } } { gcc%gcc.link.dll-libboost_serialization-mt.so.SHARED_LIB { gcc%gcc.compile.c++-basic_archive.o.OBJ { basic_archive.cpp.CPP } } { gcc%gcc.compile.c++-basic_iarchive.o.OBJ { basic_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-basic_iserializer.o.OBJ { basic_iserializer.cpp.CPP } } { gcc%gcc.compile.c++-basic_oarchive.o.OBJ { basic_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-basic_oserializer.o.OBJ { basic_oserializer.cpp.CPP } } { gcc%gcc.compile.c++-basic_pointer_iserializer.o.OBJ { basic_pointer_iserializer.cpp.CPP } } { gcc%gcc.compile.c++-basic_pointer_oserializer.o.OBJ { basic_pointer_oserializer.cpp.CPP } } { gcc%gcc.compile.c++-basic_serializer_map.o.OBJ { basic_serializer_map.cpp.CPP } } { gcc%gcc.compile.c++-basic_text_iprimitive.o.OBJ { basic_text_iprimitive.cpp.CPP } } { gcc%gcc.compile.c++-basic_text_oprimitive.o.OBJ { basic_text_oprimitive.cpp.CPP } } { gcc%gcc.compile.c++-basic_xml_archive.o.OBJ { basic_xml_archive.cpp.CPP } } { gcc%gcc.compile.c++-binary_iarchive.o.OBJ { binary_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-binary_oarchive.o.OBJ { binary_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-codecvt_null.o.OBJ { codecvt_null.cpp.CPP } } { gcc%gcc.compile.c++-extended_type_info.o.OBJ { extended_type_info.cpp.CPP } } { gcc%gcc.compile.c++-extended_type_info_no_rtti.o.OBJ { extended_type_info_no_rtti.cpp.CPP } } { gcc%gcc.compile.c++-extended_type_info_typeid.o.OBJ { extended_type_info_typeid.cpp.CPP } } { gcc%gcc.compile.c++-polymorphic_iarchive.o.OBJ { polymorphic_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-polymorphic_oarchive.o.OBJ { polymorphic_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-stl_port.o.OBJ { stl_port.cpp.CPP } } { gcc%gcc.compile.c++-text_iarchive.o.OBJ { text_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-text_oarchive.o.OBJ { text_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-void_cast.o.OBJ { void_cast.cpp.CPP } } { gcc%gcc.compile.c++-xml_grammar.o.OBJ { xml_grammar.cpp.CPP } } { gcc%gcc.compile.c++-xml_iarchive.o.OBJ { xml_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-xml_oarchive.o.OBJ { xml_oarchive.cpp.CPP } } } } { gcc%gcc.link.dll-libboost_mpi-mt.so.SHARED_LIB { gcc%gcc.compile.c++-broadcast.o.OBJ { broadcast.cpp.CPP } } { gcc%gcc.compile.c++-communicator.o.OBJ { communicator.cpp.CPP } } { gcc%gcc.compile.c++-computation_tree.o.OBJ { computation_tree.cpp.CPP } } { gcc%gcc.compile.c++-content_oarchive.o.OBJ { content_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-environment.o.OBJ { environment.cpp.CPP } } { gcc%gcc.compile.c++-exception.o.OBJ { exception.cpp.CPP } } { gcc%gcc.compile.c++-graph_topology.o.OBJ { graph_topology.cpp.CPP } } { gcc%gcc.compile.c++-group.o.OBJ { group.cpp.CPP } } { gcc%gcc.compile.c++-mpi_datatype_cache.o.OBJ { mpi_datatype_cache.cpp.CPP } } { gcc%gcc.compile.c++-mpi_datatype_oarchive.o.OBJ { mpi_datatype_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-packed_iarchive.o.OBJ { packed_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-packed_oarchive.o.OBJ { packed_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-packed_skeleton_iarchive.o.OBJ { packed_skeleton_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-packed_skeleton_oarchive.o.OBJ { packed_skeleton_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-point_to_point.o.OBJ { point_to_point.cpp.CPP } } { gcc%gcc.compile.c++-request.o.OBJ { request.cpp.CPP } } { gcc%gcc.compile.c++-text_skeleton_oarchive.o.OBJ { text_skeleton_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-timer.o.OBJ { timer.cpp.CPP } } { gcc%gcc.link.dll-libboost_serialization-mt.so.SHARED_LIB { gcc%gcc.compile.c++-basic_archive.o.OBJ { basic_archive.cpp.CPP } } { gcc%gcc.compile.c++-basic_iarchive.o.OBJ { basic_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-basic_iserializer.o.OBJ { basic_iserializer.cpp.CPP } } { gcc%gcc.compile.c++-basic_oarchive.o.OBJ { basic_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-basic_oserializer.o.OBJ { basic_oserializer.cpp.CPP } } { gcc%gcc.compile.c++-basic_pointer_iserializer.o.OBJ { basic_pointer_iserializer.cpp.CPP } } { gcc%gcc.compile.c++-basic_pointer_oserializer.o.OBJ { basic_pointer_oserializer.cpp.CPP } } { gcc%gcc.compile.c++-basic_serializer_map.o.OBJ { basic_serializer_map.cpp.CPP } } { gcc%gcc.compile.c++-basic_text_iprimitive.o.OBJ { basic_text_iprimitive.cpp.CPP } } { gcc%gcc.compile.c++-basic_text_oprimitive.o.OBJ { basic_text_oprimitive.cpp.CPP } } { gcc%gcc.compile.c++-basic_xml_archive.o.OBJ { basic_xml_archive.cpp.CPP } } { gcc%gcc.compile.c++-binary_iarchive.o.OBJ { binary_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-binary_oarchive.o.OBJ { binary_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-codecvt_null.o.OBJ { codecvt_null.cpp.CPP } } { gcc%gcc.compile.c++-extended_type_info.o.OBJ { extended_type_info.cpp.CPP } } { gcc%gcc.compile.c++-extended_type_info_no_rtti.o.OBJ { extended_type_info_no_rtti.cpp.CPP } } { gcc%gcc.compile.c++-extended_type_info_typeid.o.OBJ { extended_type_info_typeid.cpp.CPP } } { gcc%gcc.compile.c++-polymorphic_iarchive.o.OBJ { polymorphic_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-polymorphic_oarchive.o.OBJ { polymorphic_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-stl_port.o.OBJ { stl_port.cpp.CPP } } { gcc%gcc.compile.c++-text_iarchive.o.OBJ { text_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-text_oarchive.o.OBJ { text_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-void_cast.o.OBJ { void_cast.cpp.CPP } } { gcc%gcc.compile.c++-xml_grammar.o.OBJ { xml_grammar.cpp.CPP } } { gcc%gcc.compile.c++-xml_iarchive.o.OBJ { xml_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-xml_oarchive.o.OBJ { xml_oarchive.cpp.CPP } } } } { gcc%gcc.link.dll-libboost_serialization-mt.so.SHARED_LIB { gcc%gcc.compile.c++-basic_archive.o.OBJ { basic_archive.cpp.CPP } } { gcc%gcc.compile.c++-basic_iarchive.o.OBJ { basic_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-basic_iserializer.o.OBJ { basic_iserializer.cpp.CPP } } { gcc%gcc.compile.c++-basic_oarchive.o.OBJ { basic_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-basic_oserializer.o.OBJ { basic_oserializer.cpp.CPP } } { gcc%gcc.compile.c++-basic_pointer_iserializer.o.OBJ { basic_pointer_iserializer.cpp.CPP } } { gcc%gcc.compile.c++-basic_pointer_oserializer.o.OBJ { basic_pointer_oserializer.cpp.CPP } } { gcc%gcc.compile.c++-basic_serializer_map.o.OBJ { basic_serializer_map.cpp.CPP } } { gcc%gcc.compile.c++-basic_text_iprimitive.o.OBJ { basic_text_iprimitive.cpp.CPP } } { gcc%gcc.compile.c++-basic_text_oprimitive.o.OBJ { basic_text_oprimitive.cpp.CPP } } { gcc%gcc.compile.c++-basic_xml_archive.o.OBJ { basic_xml_archive.cpp.CPP } } { gcc%gcc.compile.c++-binary_iarchive.o.OBJ { binary_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-binary_oarchive.o.OBJ { binary_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-codecvt_null.o.OBJ { codecvt_null.cpp.CPP } } { gcc%gcc.compile.c++-extended_type_info.o.OBJ { extended_type_info.cpp.CPP } } { gcc%gcc.compile.c++-extended_type_info_no_rtti.o.OBJ { extended_type_info_no_rtti.cpp.CPP } } { gcc%gcc.compile.c++-extended_type_info_typeid.o.OBJ { extended_type_info_typeid.cpp.CPP } } { gcc%gcc.compile.c++-polymorphic_iarchive.o.OBJ { polymorphic_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-polymorphic_oarchive.o.OBJ { polymorphic_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-stl_port.o.OBJ { stl_port.cpp.CPP } } { gcc%gcc.compile.c++-text_iarchive.o.OBJ { text_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-text_oarchive.o.OBJ { text_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-void_cast.o.OBJ { void_cast.cpp.CPP } } { gcc%gcc.compile.c++-xml_grammar.o.OBJ { xml_grammar.cpp.CPP } } { gcc%gcc.compile.c++-xml_iarchive.o.OBJ { xml_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-xml_oarchive.o.OBJ { xml_oarchive.cpp.CPP } } } } } error: created from ./install-proper-lib error: another virtual target { common%common.copy-mpi.so.PYTHON_EXTENSION { gcc%gcc.link.dll-mpi.so.PYTHON_EXTENSION { gcc%gcc.compile.c++-collectives.o.OBJ { python/collectives.cpp.CPP } } { gcc%gcc.compile.c++-py_communicator.o.OBJ { python/py_communicator.cpp.CPP } } { gcc%gcc.compile.c++-datatypes.o.OBJ { python/datatypes.cpp.CPP } } { gcc%gcc.compile.c++-documentation.o.OBJ { python/documentation.cpp.CPP } } { gcc%gcc.compile.c++-py_environment.o.OBJ { python/py_environment.cpp.CPP } } { gcc%gcc.compile.c++-py_exception.o.OBJ { python/py_exception.cpp.CPP } } { gcc%gcc.compile.c++-module.o.OBJ { python/module.cpp.CPP } } { gcc%gcc.compile.c++-py_request.o.OBJ { python/py_request.cpp.CPP } } { gcc%gcc.compile.c++-skeleton_and_content.o.OBJ { python/skeleton_and_content.cpp.CPP } } { gcc%gcc.compile.c++-status.o.OBJ { python/status.cpp.CPP } } { gcc%gcc.compile.c++-py_timer.o.OBJ { python/py_timer.cpp.CPP } } { gcc%gcc.archive-libboost_mpi_python-mt.a.STATIC_LIB { gcc%gcc.compile.c++-serialize.o.OBJ { python/serialize.cpp.CPP } } } { gcc%gcc.archive-libboost_python-mt.a.STATIC_LIB { gcc%gcc.compile.c++-numeric.o.OBJ { numeric.cpp.CPP } } { gcc%gcc.compile.c++-list.o.OBJ { list.cpp.CPP } } { gcc%gcc.compile.c++-long.o.OBJ { long.cpp.CPP } } { gcc%gcc.compile.c++-dict.o.OBJ { dict.cpp.CPP } } { gcc%gcc.compile.c++-tuple.o.OBJ { tuple.cpp.CPP } } { gcc%gcc.compile.c++-str.o.OBJ { str.cpp.CPP } } { gcc%gcc.compile.c++-slice.o.OBJ { slice.cpp.CPP } } { gcc%gcc.compile.c++-aix_init_module.o.OBJ { aix_init_module.cpp.CPP } } { gcc%gcc.compile.c++-from_python.o.OBJ { converter/from_python.cpp.CPP } } { gcc%gcc.compile.c++-registry.o.OBJ { converter/registry.cpp.CPP } } { gcc%gcc.compile.c++-type_id.o.OBJ { converter/type_id.cpp.CPP } } { gcc%gcc.compile.c++-enum.o.OBJ { object/enum.cpp.CPP } } { gcc%gcc.compile.c++-class.o.OBJ { object/class.cpp.CPP } } { gcc%gcc.compile.c++-function.o.OBJ { object/function.cpp.CPP } } { gcc%gcc.compile.c++-inheritance.o.OBJ { object/inheritance.cpp.CPP } } { gcc%gcc.compile.c++-life_support.o.OBJ { object/life_support.cpp.CPP } } { gcc%gcc.compile.c++-pickle_support.o.OBJ { object/pickle_support.cpp.CPP } } { gcc%gcc.compile.c++-errors.o.OBJ { errors.cpp.CPP } } { gcc%gcc.compile.c++-module.o.OBJ { module.cpp.CPP } } { gcc%gcc.compile.c++-builtin_converters.o.OBJ { converter/builtin_converters.cpp.CPP } } { gcc%gcc.compile.c++-arg_to_python_base.o.OBJ { converter/arg_to_python_base.cpp.CPP } } { gcc%gcc.compile.c++-iterator.o.OBJ { object/iterator.cpp.CPP } } { gcc%gcc.compile.c++-stl_iterator.o.OBJ { object/stl_iterator.cpp.CPP } } { gcc%gcc.compile.c++-object_protocol.o.OBJ { object_protocol.cpp.CPP } } { gcc%gcc.compile.c++-object_operators.o.OBJ { object_operators.cpp.CPP } } { gcc%gcc.compile.c++-wrapper.o.OBJ { wrapper.cpp.CPP } } { gcc%gcc.compile.c++-import.o.OBJ { import.cpp.CPP } } { gcc%gcc.compile.c++-exec.o.OBJ { exec.cpp.CPP } } } { gcc%gcc.archive-libboost_mpi-mt.a.STATIC_LIB { gcc%gcc.compile.c++-broadcast.o.OBJ { broadcast.cpp.CPP } } { gcc%gcc.compile.c++-communicator.o.OBJ { communicator.cpp.CPP } } { gcc%gcc.compile.c++-computation_tree.o.OBJ { computation_tree.cpp.CPP } } { gcc%gcc.compile.c++-content_oarchive.o.OBJ { content_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-environment.o.OBJ { environment.cpp.CPP } } { gcc%gcc.compile.c++-exception.o.OBJ { exception.cpp.CPP } } { gcc%gcc.compile.c++-graph_topology.o.OBJ { graph_topology.cpp.CPP } } { gcc%gcc.compile.c++-group.o.OBJ { group.cpp.CPP } } { gcc%gcc.compile.c++-mpi_datatype_cache.o.OBJ { mpi_datatype_cache.cpp.CPP } } { gcc%gcc.compile.c++-mpi_datatype_oarchive.o.OBJ { mpi_datatype_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-packed_iarchive.o.OBJ { packed_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-packed_oarchive.o.OBJ { packed_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-packed_skeleton_iarchive.o.OBJ { packed_skeleton_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-packed_skeleton_oarchive.o.OBJ { packed_skeleton_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-point_to_point.o.OBJ { point_to_point.cpp.CPP } } { gcc%gcc.compile.c++-request.o.OBJ { request.cpp.CPP } } { gcc%gcc.compile.c++-text_skeleton_oarchive.o.OBJ { text_skeleton_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-timer.o.OBJ { timer.cpp.CPP } } } { gcc%gcc.archive-libboost_serialization-mt.a.STATIC_LIB { gcc%gcc.compile.c++-basic_archive.o.OBJ { basic_archive.cpp.CPP } } { gcc%gcc.compile.c++-basic_iarchive.o.OBJ { basic_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-basic_iserializer.o.OBJ { basic_iserializer.cpp.CPP } } { gcc%gcc.compile.c++-basic_oarchive.o.OBJ { basic_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-basic_oserializer.o.OBJ { basic_oserializer.cpp.CPP } } { gcc%gcc.compile.c++-basic_pointer_iserializer.o.OBJ { basic_pointer_iserializer.cpp.CPP } } { gcc%gcc.compile.c++-basic_pointer_oserializer.o.OBJ { basic_pointer_oserializer.cpp.CPP } } { gcc%gcc.compile.c++-basic_serializer_map.o.OBJ { basic_serializer_map.cpp.CPP } } { gcc%gcc.compile.c++-basic_text_iprimitive.o.OBJ { basic_text_iprimitive.cpp.CPP } } { gcc%gcc.compile.c++-basic_text_oprimitive.o.OBJ { basic_text_oprimitive.cpp.CPP } } { gcc%gcc.compile.c++-basic_xml_archive.o.OBJ { basic_xml_archive.cpp.CPP } } { gcc%gcc.compile.c++-binary_iarchive.o.OBJ { binary_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-binary_oarchive.o.OBJ { binary_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-codecvt_null.o.OBJ { codecvt_null.cpp.CPP } } { gcc%gcc.compile.c++-extended_type_info.o.OBJ { extended_type_info.cpp.CPP } } { gcc%gcc.compile.c++-extended_type_info_no_rtti.o.OBJ { extended_type_info_no_rtti.cpp.CPP } } { gcc%gcc.compile.c++-extended_type_info_typeid.o.OBJ { extended_type_info_typeid.cpp.CPP } } { gcc%gcc.compile.c++-polymorphic_iarchive.o.OBJ { polymorphic_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-polymorphic_oarchive.o.OBJ { polymorphic_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-stl_port.o.OBJ { stl_port.cpp.CPP } } { gcc%gcc.compile.c++-text_iarchive.o.OBJ { text_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-text_oarchive.o.OBJ { text_oarchive.cpp.CPP } } { gcc%gcc.compile.c++-void_cast.o.OBJ { void_cast.cpp.CPP } } { gcc%gcc.compile.c++-xml_grammar.o.OBJ { xml_grammar.cpp.CPP } } { gcc%gcc.compile.c++-xml_iarchive.o.OBJ { xml_iarchive.cpp.CPP } } { gcc%gcc.compile.c++-xml_oarchive.o.OBJ { xml_oarchive.cpp.CPP } } } } } error: created from ./install-proper-lib error: added properties: <define>BOOST_PYTHON_STATIC_LIB <library>object(file-target)@20365 <library>object(file-target)@20426 <library>object(file-target)@20523 <library>object(file-target)@20535 <link>static error: removed properties: <define>BOOST_PYTHON_DYNAMIC_LIB <library>object(file-target)@575 <library>object(file-target)@676 <library>object(file-target)@856 <link>shared <xdll-path>/home/cfairles/repos/boost/bin.v2/libs/mpi/build/gcc-4.1.1/release/threading-multi <xdll-path>/home/cfairles/repos/boost/bin.v2/libs/python/build/gcc-4.1.1/release/threading-multi <xdll-path>/home/cfairles/repos/boost/bin.v2/libs/serialization/build/gcc-4.1.1/release/threading-multi /home/cfairles/repos/boost/tools/build/v2/build/virtual-target.jam:459: in actualize-no-scanner from module object(file-target)@20868 /home/cfairles/repos/boost/tools/build/v2/build/virtual-target.jam:111: in object(file-target)(a)20868.actualize from module object(file-target)@20868 /home/cfairles/repos/boost/tools/build/v2/build-system.jam:476: in load from module build-system /home/cfairles/repos/boost/tools/build/v2/kernel/modules.jam:261: in import from module modules /home/cfairles/repos/boost/tools/build/v2/kernel/bootstrap.jam:132: in boost-build from module /home/cfairles/repos/boost/boost-build.jam:9: in module scope from module Not all Boost libraries built properly. Haven't found a workaround yet. Chris

2 1

CGAL and the BGL
by Andreas Fabri 04 Jun '07

04 Jun '07

The CGAL Open Source Project is pleased to announce the release 3.3 of CGAL, the Computational Geometry Algorithms Library, a robust, easy-to-use, and efficient C++ software library of geometric data structures and algorithms. We don't post the full announcement here, because that would be off-topic, but we want to point out that CGAL comes with partial specializations of the boost::graph_traits for several CGAL data structures and overloaded versions of the global functions for graph traversal. This is done for the 2D triangulations, the 2D arrangements of curves, and the polyhdral surface, that is for data structures with vertices and edges. This allows for example to compute the Euclidean minimum spanning tree of a point set in the plane, by running the BGL minimum spanniung tree algorithms on a CGAL 2D Delaunay triangulation, without converting the latter to a BGL graph. For more iformation see http://www.cgal.org/Manual/3.3/doc_html/cgal_manual/packages.html#Pkg:BGL

2 1

[multi_index] MSVS 2005 visualizers?
by Filip Konvička 04 Jun '07

04 Jun '07

Hi, I just wanted to know if anyone succeeded creating a visualizer for multi_index containers. I'd love to spend some time doing that for the good of the community (and my own, of course :-)), but I could not find any data members for exploration in the debugger's watch window. Any suggestions? See the following blog for more info: http://www.virtualdub.org/blog/pivot/entry.php?id=120 Some info can be found in the autoexp.dat file directly - there are pre-defined visualizers for eg. std::map (which works nice). Thanks, Filip

6 32

[date_time] UNICODE and wcout problems
by Filip Konvička 04 Jun '07

04 Jun '07

Hi, in MSVC 8.0 _UNICODE build, after I send a ptime to wcout, I can no longer print "international" characters. When I use a temporary wostringstream for printing the ptime, everything is OK. Minimal repro see below (the "2" at the end is never printed). With some characters like the "š" in the example, the output is totally cut off; with others, like "á", the codepage is changed, so the characters are displayed incorrectly. Any suggestions? Thanks, Filip // _UNICODE must be defined; the "2" is never printed. #include <string> #include <iostream> #include <sstream> #include <locale.h> #include <boost/date_time/posix_time/posix_time.hpp> using boost::posix_time::ptime; using boost::date_time::not_a_date_time; int main() { wstring intl=L"\x161"; wostringstream ss; ss << ptime(not_a_date_time); wcout << ss.str() << endl; wcout << intl << endl; wcout << L"1" << endl; wcout << ptime(not_a_date_time) << endl; wcout << intl << endl; wcout << L"2" << endl; }

4 10

[thread_safe_signals] won't compile on VC71
by David Matz 04 Jun '07

04 Jun '07

Hello, I'm very impressed from Mr. Hess' work on thread safe signals for the boost library. In my opinion it's a great step to provide thread safe signals in a common library like boost and I like to use it as replacement for third party libs. Unfortunately I going in trouble when using the latest version of this module (thread_safe_signals-2007-03-19.tgz which is the same as out of the cvs). I can't get it compile on Microsoft VS71. I tried with gcc and VS8 and it works but for the VS71 compiler which we are working it fails. As mentioned in the documentation I included the headers of thread_safe_signals before the normal boost headers which are in fact 1_33_1 (same results with 1_34_0). The I picked up a sample project signal_test.cpp from boost/test/ and start to compile it but it fails with the following compiler hints: Kompilieren... signal_test.cpp ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(95) : error C2143: Syntaxfehler: Es fehlt ',' vor '&' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(109): Siehe Verweis auf Instanziierung der kompilierten Klassenvorlage 'boost::slot0<R,SlotFunction>' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(95) : error C2143: Syntaxfehler: Es fehlt ',' vor '&' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(109): Siehe Verweis auf Instanziierung der kompilierten Klassenvorlage 'boost::slot1<R,T1,SlotFunction>' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(95) : error C2143: Syntaxfehler: Es fehlt ',' vor '&' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(109): Siehe Verweis auf Instanziierung der kompilierten Klassenvorlage 'boost::slot2<R,T1,T2,SlotFunction>' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(95) : error C2143: Syntaxfehler: Es fehlt ',' vor '&' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(109): Siehe Verweis auf Instanziierung der kompilierten Klassenvorlage 'boost::slot3<R,T1,T2,T3,SlotFunction>' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(95) : error C2143: Syntaxfehler: Es fehlt ',' vor '&' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(109): Siehe Verweis auf Instanziierung der kompilierten Klassenvorlage 'boost::slot4<R,T1,T2,T3,T4,SlotFunction>' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(95) : error C2143: Syntaxfehler: Es fehlt ',' vor '&' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(109): Siehe Verweis auf Instanziierung der kompilierten Klassenvorlage 'boost::slot5<R,T1,T2,T3,T4,T5,SlotFunction>' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(95) : error C2143: Syntaxfehler: Es fehlt ',' vor '&' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(109): Siehe Verweis auf Instanziierung der kompilierten Klassenvorlage 'boost::slot6<R,T1,T2,T3,T4,T5,T6,SlotFunction>' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(95) : error C2143: Syntaxfehler: Es fehlt ',' vor '&' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(109): Siehe Verweis auf Instanziierung der kompilierten Klassenvorlage 'boost::slot7<R,T1,T2,T3,T4,T5,T6,T7,SlotFunction>' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(95) : error C2143: Syntaxfehler: Es fehlt ',' vor '&' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(109): Siehe Verweis auf Instanziierung der kompilierten Klassenvorlage 'boost::slot8<R,T1,T2,T3,T4,T5,T6,T7,T8,SlotFunction>' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(95) : error C2143: Syntaxfehler: Es fehlt ',' vor '&' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(109): Siehe Verweis auf Instanziierung der kompilierten Klassenvorlage 'boost::slot9<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,SlotFunction>' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(95) : error C2143: Syntaxfehler: Es fehlt ',' vor '&' ...\thread_safe_signals\boost\thread_safe_signals\detail\slot_template.hpp(109): Siehe Verweis auf Instanziierung der kompilierten Klassenvorlage 'boost::slot10<R,T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,SlotFunction>' The same error comes up with other example snippets like doc_view.cpp or something else. At this stage I can't understand what is going on. Any help is very welcome. -- David Matz ---------------------------- Software Developer Spatial View GmbH david.matz<at>spatialview.com registration court: Amtsgericht Dresden, HRB 21104 managing directors: Wolfgang Opel, Jens Wiegrebe

2 2

[interprocess]
by Aaron W. LaFramboise 03 Jun '07

03 Jun '07

I just got Boost.Interprocess working, and it's really an amazing library. Ion, it's obvious you've put a lot of time into this library, and the result is really nice. However, I've had these issues so far: (1) Is there a way to get a managed_shared_memory segment to tell me allocation statistics? What I'd like is something that can tell me. (a) Segment size (b) Allocated memory (c) Most importantly, free memory (2) It's been brought up before, but there seriously needs to be a way to grow managed shared memory segments. I understand that this is really tricky to implement, and probably just as tricky to use safely, but it's an important feature, in my opinion. I guess the main difficulties here are the potential change of base, and atomicity? (3) Regarding priv_open_or_create() in managed_open_or_create_impl.hpp, this implementation creates some small annoyances for me by throwing. I don't have any idea how to tell if POSIX O_CREAT actually created anything or not. However, I'm using Windows, and on Windows, you always can tell, as far as I know, both for file creation and named shared memory object creation. Would it be difficult to avoid throwing for the Windows case?

3 4

Re: [Boost-users] newbie ordering question forboost::multi_index::ordered_non_unique
by "JOAQUIN LOPEZ MU?Z" 02 Jun '07

02 Jun '07

Hello Kevin, ----- Mensaje original ----- De: Kevin McMahon <kevinmcm(a)alum.mit.edu> Fecha: Sábado, Junio 2, 2007 4:15 pm Asunto: [Boost-users] newbie ordering question forboost::multi_index::ordered_non_unique Para: boost-users(a)lists.boost.org > I'd like to pop items in my data set ordered by a key, but if the > key is identical then ordered in the order I inserted them. > Is there a good way to do that? I guess I could make a > composite key using an increasing id. Although it is not documented (and I think I should document it in light of LWG issue 233), non-hinted insertion always happens at the end of all previously stored elements with equivalent key. Is this what you want? Are you observing otherwise? Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

[date_time] nanosec resolution compile problem
by Christopher Lux 02 Jun '07

02 Jun '07

Hi, i am trying to use date_time with nanosec resolution for the fractional seconds part. So i define BOOST_DATE_TIME_POSIX_TIME_STD_CONFIG in my projects using date_time. Now i get the compiler warning below. I found out that the problem in the said function is that in boost/date_time/date_duration.hpp the struct duration_traits_adapted defines the int_type as long and not as int_64t. The warning is generated in the add_time_duration() funtion of the split_timedate_system class. So i imagine that this is a bigger issue, because if the durations get bigger than what a long can hold (what will happen fast with nanosec resolution) the problems will come. Can this be resolved with an small fix to the duration_traits_adapted struct or have there to be more fixes? Here the compiler warning (VS.net 2005 SP1) boost\boost/date_time/time_system_split.hpp(189) : warning C4244: 'initializing' : conversion from '__int64' to 'long', possible loss of data D:\_devel\schism_wc_x86\schism\projects\cmake\..\..\ext\inc\boost\boost/date_time/time_system_split.hpp(180) : while compiling class template member function 'boost::posix_time::simple_time_rep boost::date_time::split_timedate_system<config>::add_time_duration(const boost::posix_time::simple_time_rep &,boost::posix_time::time_duration)' with [ config=boost::posix_time::posix_time_system_config ] D:\_devel\schism_wc_x86\schism\projects\cmake\..\..\ext\inc\boost\boost/date_time/time.hpp(52) : see reference to class template instantiation 'boost::date_time::split_timedate_system<config>' being compiled with [ config=boost::posix_time::posix_time_system_config ] D:\_devel\schism_wc_x86\schism\projects\cmake\..\..\ext\inc\boost\boost/date_time/posix_time/ptime.hpp(32) : see reference to class template instantiation 'boost::date_time::base_time<T,time_system>' being compiled with [ T=boost::posix_time::ptime, time_system=boost::posix_time::posix_time_system ] -chris -- Christopher Lux | | Bauhaus University Weimar | Faculty of Media - Virtual Reality Systems Group

2 2

converting ptime to/from CLR (.NET) DateTime
by Jens Schluetter 02 Jun '07

02 Jun '07

Hi, I'm kinda stuck. I'm working on an inter op library to glue C++ code that uses ptime with C# code that uses (of course) the .NET DateTime format. Since the system needs the outmost performance I'm looking for a way to use binary conversion. Conversion from .NET to ptime is easy since there is a from_ftime<> conversion method, however the other direction is somewhat blocked since no ptime to FILE_TIME conversion exists. My current workaround is using ISO time strings but performance is somewhat dismal since there is a lot of string <> binary conversion. Does anyone know of a more straight forward (binary)way of converting? And just in case, using regular time_t as common denominator is not an option since at leas millisecond resolution is required. I'd be greatful for any recommendations/ideas. Cheers, Jens.

2 1

datetime istream and ostream operators don't match
by Lothar Werzinger 02 Jun '07

02 Jun '07

compile the attached cppunit test with -DHIDE_BOOST_DATETIME_BUGS=false to see where datetime ostream operator produces an output that the datetime istream operator can not digest. Lothar -- Lothar Werzinger Dipl.-Ing. Univ. framework & platform architect Tradescape Inc. 111 West St. John Street, Suite 200 San Jose, Ca 95113 email: lothar(a)tradescape.biz web: http://www.tradescape.biz

2 1

Requesting boost x64 getting started documentation
by Daniel Svensson 02 Jun '07

02 Jun '07

Would someone who know how to do it add information about how to build boost for x64 to the online "getting started" documentation. An example command line like "bjam address-model=64 install" would probably be sufficient. See the "Boost 1.34 and VC++ x64" thread; > > Cory Nelson wrote: >> >> This was pretty straightforward for 1.33, but 1.34 using BB2 seems to >> >> have changed things a bit. There doesn't seem to be any documentation >> >> on compiling 1.34 for x64 with VC++ - can anyone offer some insight? > > > > Yea, as with previous Boost.Build versions those options are not > > documented :-) Just add an "address-model=64" argument when building. > > > >

1 0

[BGL] boost::bind fails to compile when used with edge iterators in for_each
by Sashan Govender 01 Jun '07

01 Jun '07

Hi I'm trying to run a functor over edges from a graph using for_each however it fails when the iterators are edges. The same technique works for iterators to vertices. Here is the compiler error: g++ -o bind_edge_test bind_edge_test.cpp /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/bits/stl_algo.h: In function '_Function std::for_each(_InputIterator, _InputIterator, _Function) [with _InputIterator = boost::detail::undirected_edge_iter<std::_List_iterator<boost::list_edge<void*, boost::property<boost::edge_name_t, unsigned int, boost::no_property> > >, boost::detail::edge_desc_impl<boost::undirected_tag, void*>, int>, _Function = boost::_bi::bind_t<void, Op, boost::_bi::list2<boost::arg<1>, boost::_bi::value<int> > >]': bind_edge_test.cpp:79: instantiated from here /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/bits/stl_algo.h:159: error: no match for call to '(boost::_bi::bind_t<void, Op, boost::_bi::list2<boost::arg<1>, boost::_bi::value<int> > >) (boost::detail::edge_desc_impl<boost::undirected_tag, void*>)' I've attached the file. Thanks for the help. -- sashan http://sashang.orcon.net.nz/

3 3

[iostreams] skip bug (repost)
by Phillip Seaver 01 Jun '07

01 Jun '07

I ran into a problem when using restrict on a file_source. The problem was that it decided that the stream wasn't seekable and called the version of skip that reads a character at a time until it gets to the requested offset, instead of just calling seek. The code was similar to this: namespace io = boost::iostreams; std::string filename; io::filtering_istream rstr(io::restrict(io::file_source(filename), 10, 100)); I've attached a patch that solved my problem. It was checking to see if the device was seekable (which means input_seekable and output_seekable), but since it was an input device, it was just input_seekable. Phillip Seaver --- skip.hpp.orig 2007-03-20 16:20:55.253000000 -0400 +++ skip.hpp 2007-03-20 16:11:51.096750000 -0400 @@ -67,7 +67,17 @@ void skip(Device& dev, stream_offset off) { typedef typename mode_of<Device>::type mode; - detail::skip(dev, off, is_convertible<mode, seekable>()); + typedef mpl::or_< + mpl::and_< + is_convertible<mode, input>, + is_convertible<mode, input_seekable> + >, + mpl::and_< + is_convertible<mode, output>, + is_convertible<mode, output_seekable> + > + > can_seek; + detail::skip(dev, off, can_seek()); } template<typename Filter, typename Device>

2 1

Problem with 1.34 Regex Package
by Jeffery Cavallaro 01 Jun '07

01 Jun '07

Hi, all! I am a bit of a newbie, so forgive if this has already been covered. The 1.34 regex package (or at least my build of it on FC6) appears to be broken. Please consider the following: #include <iostream> #include <iomanip> #include <boost/regex.hpp> int main(int argc, char *argv[]) { boost::regex rl("ab"); boost::regex ru("AB"); bool pass = regex_search("ab", rl); std::cout << std::boolalpha << pass << std::endl; pass = regex_search("AB", ru); std::cout << std::boolalpha << pass << std::endl; return EXIT_SUCCESS; } When built with 1.33 (as delivered with FC6), both tests return true. When built under 1.34 (downloaded and built), the uppercase test returns false. Yuck. Am I missing something? (probably...) -- Jeffery Cavallaro POSTINI Engineering Group 650-486-8342 ----------------------------------------------------------- This message may contain confidential and/or privileged information. This information is intended to be read only by the individual or entity to whom it is addressed. If you are not the intended recipient, you are on notice that any review, disclosure, copying, distribution or use of the contents of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete or destroy any copy of this message.

1 1

newbie ordering question for boost::multi_index::ordered_non_unique
by Kevin McMahon 01 Jun '07

01 Jun '07

I'd like to pop items in my data set ordered by a key, but if the key is identical then ordered in the order I inserted them. Is there a good way to do that? I guess I could make a composite key using an increasing id. -kevin

1 0

[Boost.Test 1.34] Multiple instances of unit_test_log_t singleton
by Kolya 01 Jun '07

01 Jun '07

Hi, All! I am using Boost.Test library in my own application and I have included boost/test/unit_test.hpp in many my cpp-files. When I used boost version 1.33.1 all works fine. But in version 1.34 I have following compiler error: file1.obj : error LNK2005: "class unit_test_log_t::boost::unit_test_log_t & boost::unit_test::`anonymous namespace'::unit_test_log" (?unit_test_log@?A0xa35d3712@unit_test@boost@@3AAVunit_test_log_t@23@A) already defined in file2.obj After including boost/test/unit_test.hpp class unit_test_log has multiple instances. See boost/test/unit_test_log.hpp for details: BOOST_TEST_SINGLETON_INST( unit_test_log ) It means that following code will be included in many cpp-files! namespace { unit_test_log_t & inst = unit_test_log_t::instance(); } When I replace BOOST_TEST_SINGLETON_INST( unit_test_log ) in boost/test/unit_test_log.hpp with namespace {extern unit_test_log_t & unit_test_log;} and in one of my cpp-files add: namespace boost { namespace unit_test { BOOST_TEST_SINGLETON_INST( unit_test_log ) } } all works fine May be I do not understand something? Is there any legal workaround from this situation? I do not like touch boost core files by myself. Thank you! VC++ 7.1, boost 1.34, xp sp2.

4 6

Bind: more convenience operators?
by Arno Schoedl 01 Jun '07

01 Jun '07

Bind has operator! overloaded to allow convenient notting of bound functions. Is there a specific reason not to overload all other operators in a similar way, for example for defining an AND of two predicates f and g as boost::bind( f, _1 ) && boost::bind( g, _1 )? Arno

2 1

[TR1] Configuration macros
by Scott Meyers 01 Jun '07

01 Jun '07

I'm having trouble understanding the information at http://www.boost.org/doc/html/boost_tr1/config.html, and having already spent a fair amount of time running test programs and pouring over the output of the preprocessor for various compilers, I'm hoping that somebody in the know can just explain things to me. My goal is simple: use Boost.TR1 such that if my compiler ships with a library with support for whatever TR1 component I want to use, I'll get that native support. But if the library that ships with the compiler lacks support for the TR1 component I need, I want to fall back on the Boost implementation, if there is one. And I want to uniformly refer to TR1 components as if they are in the namespace std::tr1. My reading of the above-referenced page leads me to believe that this is the behavior I'm supposed to get by default. And it's consistent with the tests I've performed using VC8 and g++ 4.1. But then I read this: > The configuration macros used by each TR1 component are documented in each library section (and all together in the Boost.Config documentation), but defining BOOST_HAS_TR1 will turn on native TR1 support for everything (if your standard library has it), which can act as a convenient shortcut. This kind of suggests that I should define BOOST_HAS_TR1. Should I? So far I have not. And then I read this: > Boost.TR1 does not currently enable gcc's native TR1 implementation as this is currently in an early stage of development. However, you may choose to do so by defining BOOST_HAS_GCC_TR1. This pretty clearly suggests that I should define BOOST_HAS_GCC_TR1. Should I? So far, I have. I've also found that unless I define it like this, > #ifdef __GNUC__ > #define BOOST_HAS_GCC_TR1 > #endif compilation with VC8 fails, which I find kind of strange. Here's an error I get: > D:\C++\Boost\Current\boost/tr1/type_traits.hpp(11): fatal error C1083: Cannot open include file: 'type_traits': No such file or dire > ctory Why should defining BOOST_HAS_GCC_TR1 have any effect on a VC8 compilation? All clarification about the correct settings of TR1 configuration macros for at least VC8 and g++ 4.1 would be much appreciated. Thanks, Scott

3 5

[bind] Convenience operator overloads
by Arno Schödl 01 Jun '07

01 Jun '07

Hello, are there any plans to provide more convenience operator overloads, such as operator! which is already implemented? I don't see any reason why not to overload all operators in that fashion. Thanks, Arno -- Arno Schoedl · aschoedl(a)think-cell.com Technical Director think-cell Software GmbH · Invalidenstr. 34 · 10115 Berlin, Germany http://www.think-cell.com · phone +49-30-666473-10 · fax +49-30-666473-19 Geschäftsführer: Dr. Markus Hannebauer, Arno Schoedl · Amtsgericht Charlottenburg, HRB 85229

1 0

[tokenizer] position of tokenizer
by Seweryn Habdank-Wojewódzki 01 Jun '07

01 Jun '07

Hi Is that possible to take actual position of the tokenizer in the parsed string? The question is motivated by such a case: 1. there is a line with data separated by e.g. "\t' sign 1 23 3.45 21 2093 494 3.4 2. important is only some of them let say from 2nd token to 5th token, but after parsing them I want to pass tokens from 6th to the end to the other string. Now I am iterating tokenizer to the end, and concatenate it. If I have had a position of tokenizer on the string I can simply create new substring with out iteration. Maybe there is other solution for that. Regards. -- |\/\/| Seweryn Habdank-Wojewódzki \/\/

1 0

Bind & Memory Leakage
by Sudhir Parikh 01 Jun '07

01 Jun '07

BoundsChecker is reporting a memory leak for every 'bind' call. I am using the threadpool includes, v 0.2.3, with "libboost_thread-vc71-mt-gd-1_33_1.lib", MSVC 7.1. Any help is appreciated. The usage is similar to the following working example: void task(int param1) { // performs some task printf("%d : Param1 : %d\n", GetCurrentThreadId(), param1); Sleep(1000); } void foo() { boost::threadpool::pool tp(5); // Threadpool with 5 threads while (1) { for (int i = 0; i < 10; i++) { // Seems like there is memory allocation which is not // deallocated after returning from the function call. tp.schedule(boost::bind(task, i)); } tp.wait(); // wait to finish off the remaining tasks Sleep(5000); // sleep for 5 seconds } }

2 1

[Unit Test] default FPC_STRONG limtations when checking close to 0.
by Chris Fairles 01 Jun '07

01 Jun '07

After wondering why my BOOST_CHECK_CLOSE(some_number_close_to_zero, 0.0) hadn't been working, I found that the default comparison type is FPC_STRONG which means the ration between the abs val of the difference and BOTH values must be < tolerance but this doesn't turn out to be true (running through what safe_fpt_division outputs atm ... difference between 0.0{0} and 0.0 std::numeric_limits<double>::epsilon(){-2.2204460492503131e-16} exceeds 0.01% It should work using FPC_WEAK but I can't find a way through the test_tools to easily change this. I have three solutions at this time. 1) Use BOOST_CHECK_SMALL. However, I have code that loops through matrix indicies like: for (int j = 0; j < matrix.col; j++) for (int i = 0; i < matrix.row; i++) BOOST_CHECK_CLOSE(matrix(i,j), data(i,j), tolerance); I'm going to have to use an if statement for the special case where I'm testing against 0 and it doesn't use the tolerance anyway so the test is completely different. Theres another number to determine "how small" the number should be. 2) Use check_is_close explicitly and change the default comparison type to FPC_WEAK. This means going outside the nice auto-unit-test and test-tools framework which although I'm fine with, other programmers writing test cases on my team might not be. 3) Define my own macro to simplify solution 2. Something along the lines of: CHECK_IS_CLOSE_WEAK(x,y,t) { check_is_close(x ,y,t, FPC_WEAK); } Are there any other recommended solutions?

2 3

[smart_ptr] shared_ptr and shared_array of const
by Tim Day 31 May '07

31 May '07

The ability to assign a shared_ptr<T> to shared_ptr<const T> is useful for controlling which parts of software have write access to the shared object, so I'm surprised that while e.g boost::shared_ptr<int> sp(new int); boost::shared_ptr<const int> csp=sp; compiles fine, and prohibits e.g *csp=0;, the equivalent for shared_array doesn't compile: boost::shared_array<int> sa(new int[10]); boost::shared_array<const int> csa=sa; // not allowed [The gcc 4.1.2 error is "conversion from ‘boost::shared_array<int>’ to non-scalar type ‘boost::shared_array<const int>’ requested"] I'm looking to prevent modification of elements of csa of course. The obvious alternative is to use a shared_ptr to a std::vector of course: boost::shared_ptr<std::vector<int> > sv(new std::vector<int>(10)); boost::shared_ptr<const std::vector<int> > csv=sv; // fine // (*csv)[0]=0; // prevented by const, as intended However, it's unclear to me exactly why the shared_array of const doesn't work as expected. Am I missing some necessary detail to make it work, is shared_array simply less featureful (the header is certainly shorter) or is there some reason it can't work ? Thanks for any explanation Tim [I'm using boost 1.33.1]

1 0

Error compiling Boost.Python library on Solaris
by Belousov, Arkadiy, GCM 31 May '07

31 May '07

Hello all! I have a compilation error with Boost 1.34.0, Sun Workshop 11 compiler. Compiling Python library, I get "libs/python/src/object/class.cpp", line 458: Error: Overloading ambiguity between "boost::python::api::getattr<boost::python::scope, char[11], boost::python::str>(const boost::python::scope&, const char(&)[11], const boost::python::str&)" and "boost::python::api::getattr(const boost::python::api::object&, const char*, const boost::python::api::object&)". The code in question is object module_prefix() { return object( PyObject_IsInstance(scope().ptr(), upcast<PyObject>(&PyModule_Type)) ? object(scope().attr("__name__")) : api::getattr(scope(), "__module__", str()) <<===== ); } Of course, casting the string constant to (const char*) solves the problem, even though I realize it's not a boost-like solution. The rest of 1.34 compiles perfectly for me (thanks are in order - excellent job!). The exact version of the compiler is $ CC -V CC: Sun C++ 5.8 Patch 121017-07 2006/11/02 Sincerely, Arkadiy Belousov ----------------------------------------- ******************************************************************* * This e-mail is intended only for the addressee named above. As this e-mail may contain confidential or privileged information, if you are not the named addressee, you are not authorized to retain, read, copy or disseminate this message or any part of it. ******************************************************************* *

2 1

unified documentation
by Rob Agar 31 May '07

31 May '07

hi all It seems to me (as a newcomer) that the one thing boost needs is documentation in a unified structure. I'm thinking of something along the lines of the MS .NET class library or the Java class references. The existing documentation for the libraries I have used so far are very hard to navigate - they seem to be more aimed at standards committees than end users. As an end user, the first thing I need is an easily navigated tree just listing all the namepaces, functions, classes, typedefs etc. As a start does anyone have a doxygen config file for generating a simple function list and class hierarchy? cheers Rob Agar

6 12

1_33_1 VC8 crash in program_options::cmdline
by Søren Holstebroe 31 May '07

31 May '07

This problem was found in boost 1.33.1 using VC++ 8.0. I haven't tried 1.34.0, but the cmdline code seems unchanged. from cmdline.cpp -------------------------------------- std::vector<option> cmdline::parse_long_option(std::vector<string>& args) { vector<option> result; const std::string& tok = args[0]; if (tok.size() >= 3 && tok[0] == '-' && tok[1] == '-') { string name, adjacent; string::size_type p = tok.find('='); if (p != tok.npos) { name = tok.substr(2, p-2); adjacent = tok.substr(p+1); if (adjacent.empty()) throw invalid_command_line_syntax(name, invalid_command_line_syntax::empty_adjacent_parameter); } else { name = tok.substr(2); } option opt; opt.string_key = name; if (!adjacent.empty()) opt.value.push_back(adjacent); opt.original_tokens.push_back(tok); result.push_back(opt); args.erase(args.begin()); } return result; } -------------------------------------- The line args.erase(args.begin()); crashes in MS VC++ 8.0 in release optimized configuration, though it works fine in debug mode. Could this be a compiler problem with loop unrolling and the const std::string& tok = args[0]; reference ? As seen in the stack trace, std::vector::erase tries to copy a "Bad Ptr" string and obviously fails miserably. Interestingly the program hangs in std::_Distance2 if I provide no command line arguments (it looks like a very long bad pointer loop, not an infinite loop). I might try recompiling boost with different compile options, but it is quite time consuming to experiment with. best regards Søren Holstebroe Code: namespace po = boost::program_options; po::options_description desc("Allowed options"); desc.add_options() ("help", "produce help message") ; po::variables_map vm; po::store(po::parse_command_line(argc, argv, desc), vm); po::notify(vm); Stack trace: > msvcr80.dll!memcpy(unsigned char * dst=0x00c20048, unsigned char * src=0xabababab, unsigned long count=458755) Line 188 Asm msvcr80.dll!memcpy_s(void * dst=0x00c20048, unsigned int sizeInBytes=458767, const void * src=0xabababab, unsigned int count=458755) Line 67 + 0xc bytes C msvcp80.dll!std::char_traits<char>::_Copy_s(char * _First1=0x00c20048, unsigned int _Size_in_bytes=458767, const char * _First2=0xabababab, unsigned int _Count=458755) Line 576 C++ msvcp80.dll!std::basic_string<char,std::char_traits<char>,std::allocator<char> >::assign(const std::basic_string<char,std::char_traits<char>,std::allocator<char> > & _Right=<Bad Ptr>, unsigned int _Roff=0, unsigned int _Count=4294967295) Line 1059 + 0x2c bytes C++ msvcp80.dll!std::basic_string<char,std::char_traits<char>,std::allocator<char> >::operator=(const std::basic_string<char,std::char_traits<char>,std::allocator<char> > & _Right=<Bad Ptr>) Line 1044 C++ PS.Vision.Console.exe!std::_Copy_opt<std::basic_string<char,std::char_traits<char>,std::allocator<char> > *,std::basic_string<char,std::char_traits<char>,std::allocator<char> > *>() + 0x4a bytes C++ PS.Vision.Console.exe!std::vector<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > >::erase() + 0x2d bytes C++ PS.Vision.Console.exe!boost::program_options::detail::cmdline::parse_long_option() + 0x28e bytes C++ PS.Vision.Console.exe!boost::_mfi::mf1<std::vector<boost::program_options::basic_option<char>,std::allocator<boost::program_options::basic_option<char> > >,boost::program_options::detail::cmdline,std::vector<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > > &>::operator()() + 0x40 bytes C++ PS.Vision.Console.exe!boost::_bi::list2<boost::_bi::value<boost::program_options::detail::cmdline *>,boost::arg<1> >::operator()<std::vector<boost::program_options::basic_option<char>,std::allocator<boost::program_options::basic_option<char> > >,boost::_mfi::mf1<std::vector<boost::program_options::basic_option<char>,std::allocator<boost::program_options::basic_option<char> > >,boost::program_options::detail::cmdline,std::vector<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > > &>,boost::_bi::list1<std::vector<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > > &> >() + 0x22 bytes C++ PS.Vision.Console.exe!boost::_bi::bind_t<std::vector<boost::program_options::basic_option<char>,std::allocator<boost::program_options::basic_option<char> > >,boost::_mfi::mf1<std::vector<boost::program_options::basic_option<char>,std::allocator<boost::program_options::basic_option<char> > >,boost::program_options::detail::cmdline,std::vector<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > > &>,boost::_bi::list2<boost::_bi::value<boost::program_options::detail::cmdline *>,boost::arg<1> > >::operator()<std::vector<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > > >() + 0x2d bytes C++ PS.Vision.Console.exe!boost::detail::function::function_obj_invoker1<boost::_bi::bind_t<std::vector<boost::program_options::basic_option<char>,std::allocator<boost::program_options::basic_option<char> > >,boost::_mfi::mf1<std::vector<boost::program_options::basic_option<char>,std::allocator<boost::program_options::basic_option<char> > >,boost::program_options::detail::cmdline,std::vector<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > > &>,boost::_bi::list2<boost::_bi::value<boost::program_options::detail::cmdline *>,boost::arg<1> > >,std::vector<boost::program_options::basic_option<char>,std::allocator<boost::program_options::basic_option<char> > >,std::vector<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > > &>::invoke() + 0x1d bytes C++ PS.Vision.Console.exe!boost::function1<std::vector<boost::program_options::basic_option<char>,std::allocator<boost::program_options::basic_option<char> > >,std::vector<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > > &,std::allocator<boost::function_base> >::operator()() + 0x5b bytes C++ PS.Vision.Console.exe!boost::program_options::detail::cmdline::run() + 0x371 bytes C++ PS.Vision.Console.exe!boost::program_options::basic_command_line_parser<wchar_t>::run() Line 102 + 0x12 bytes C++ PS.Vision.Console.exe!boost::program_options::parse_command_line<wchar_t>(int argc=5, wchar_t * * argv=0x003b5718, const boost::program_options::options_description & desc={...}, int style=0, boost::function1<std::pair<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::basic_string<char,std::char_traits<char>,std::allocator<char> > >,std::basic_string<char,std::char_traits<char>,std::allocator<char> > const &,std::allocator<boost::function_base> > ext={...}) Line 119 + 0x9d bytes C++

1 0

Building Boost 1.33.1 with different #defines for release and debug
by Ben Pope 31 May '07

31 May '07

Hi all, I'm sure this must have been covered before, but I am completely unable to find what I'm after, so apologies if that is the case. I seem to have a feeling that BBv2 as shipped with 1.33.1 is not completely ready for compiling with msvc 8 on Windows with autolinking, but I'm not sure where I go that from. What I would like to do is build the following configurations with VC8: * debug with shared libraries * release shared and static libraries with _SECURE_SCL=0 defined. Can that be done in a single call of bjam? I don't mind if we get debug static at the same time. And for completeness and the sake of comparison (and for when we move to 1.34) what is the equivalent with BBv2? I've noticed that there is some conditional stuff: <variant>release:<define>_SECURE_SCL=0 But couldn't work out how to do it on the command line, do I need to create some jam config files? Thanks for your time, Ben

1 0

iostreams: stream vs stream_buffer
by Os 31 May '07

31 May '07

Hi, could someone elaborate on when I would use a stream and when I would use a stream_buffer (filtered or otherwise)? They look remarkably similar to me. cheers, os. -- os(a)collective.co.uk http://www.collective.co.uk/ http://www.myspace.com/darkroomtheband

1 0

[boost-1.33.1] broken mmap_file_iterator in spirit implementation details.
by Paweł Sikora 31 May '07

31 May '07

hi all, mmap based file_iterator implementation has a nasty bug. it treats empty files as non-existent. mmap() doesn't map empty files into memory, but boost's implementation omit this little detail of posix specification and return an error. in fact, empty file != doesn't exist. regards, pawel. -- to_be || !to_be == 1, to_be | ~to_be == -1

1 0

Re: [Boost-users] Cross compiling boost
by Peter Poulsen 31 May '07

31 May '07

Has anybody tried compiling boost 1.34 for ARM? /peter >> >> I'm trying to build boost for an arm processor, but all the >> hidden bjam stuff is simply to much, so I have to ask for help :) >> >> All my build tools are in ~/arm-tools/. I'm on a Linux x86 >> and the cross compiler I'm trying to use is a gcc version 3.4.4. >> >> I have tried various build commands. The latest being: >> >> >> ~/boost_1_34_0 $ bjam --build-dir=/tmp/build-boost >> --toolset-gcc-3.4.4 --with-regex -sGXX=arm-wrs-linux-gnueabi-g++ stage >> >> >> But I still get: >> >> >> ~/boost_1_34_0 $ file stage/lib/libboost_regex-gcc34.so >> stage/lib/libboost_regex-gcc34.so: ELF 32-bit LSB shared >> object, Intel 80386, version 1 (SYSV), stripped >> >> Can anybody explain to me what I must do to compile >> boost-regex for arm? >> >> btw I have found others trying to do the same but they seem to end up hacking the >> bjam files, and I have no idea of how to that. >> >> /peter >> >> >> -- >> A: Because it messes up the order in which people normally read text. >> Q: Why is it such a bad thing? >> A: Top-posting. >> Q: What is the most annoying thing on usenet and in e-mail? >> >> >> >> >> _______________________________________________ >> Boost-users mailing list >> Boost-users(a)lists.boost.org >> http://lists.boost.org/mailman/listinfo.cgi/boost-users >> >> > > This message (including any attachments) contains confidential > and/or proprietary information intended only for the addressee. Any unauthorized > disclosure, copying, distribution or reliance on the contents of this information is > strictly prohibited and may constitute a violation of law. If you are not the > intended recipient, please notify the sender immediately by responding to this > e-mail, and delete the message from your system. If you have any questions about > this e-mail please notify the sender immediately. > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users > >

1 0

Wave Driver Program
by ivan＠0x4849.net 31 May '07

31 May '07

Hi, I am using debian linux and wanted to access the Wave Driver program. It seems they have a package for the wave library but that doesnt seem to include the driver binary. I had a look in the code but couldn't find where the driver program's code is either. Is it the intention to release the driver as a C++ pre-processor binary similar to how cpp is used, or is the driver program just meant for one-off testing? In any case could someone point me to the code for the driver within the boost source tree? Thanks, Ivan --------------------- Ivan Novick http://www.0x4849.net

2 1

iostream::mapped_file
by Richard_Morrey＠McAfee.com 31 May '07

31 May '07

A query about the above. I wish to use it to enable us to share memory amongst processes. Whilst it obviously should be possible to do this using CreateFileMapping on Windows and mmap on linux, which the class uses, the documentation is not clear as to whether it is designed be used in this way. Looking at the source code: (a) It does not provide a kernel name to the CreateFileMapping call on Windows. According to the MSDN docs this is the only way to share one mapping amongst multuiple processes, and therefore it is possible that a different mapping, albeit of the same file, is being created for each process. I don't want that as the point is to keep memory usage down. (b) On linux it only uses MEM_SHARED flag if the file is read only. If this flag isnt used, is there the possiblity that more than one copy of each page of the file will be loaded into physical memory too? Clarification on any of these points is most welcome Thanks Richard Morrey.

1 0

iostreams build error in Visual Studio 2005
by Os 31 May '07

31 May '07

In file_descriptor.cpp I get a deprecation warning from line 219: lseek is deprecated in favour of _lseek. I've just patched my local copy, but could this be changed in the official version? cheers, os. -- os(a)collective.co.uk http://www.collective.co.uk/ http://www.myspace.com/darkroomtheband

3 3

[multi_index] MSVC 8.0 visualizer for indexed_by<sequenced<>, ...> containers
by Filip Konvička 31 May '07

31 May '07

Hello all, for those interested, here is an alpha version of a MSVC-8.0 visualizer for multi_index_containers whose first index is sequenced<>. To try it out, insert autoexp.dat.txt contents into your Microsoft Visual Studio 8\Common7\Packages\Debugger\autoexp.dat For your container to be visualized, you need to call the VISUALIZE_MULTI_INDEX_CONTAINER macro at the global namespace level (see the attached example, test2.cpp, and the screenshot of a test2.cpp debugging session, sample.png). Comments / suggestions are welcome! Things that need attention: - of course, containers whose first index is not sequenced<> - maybe there is a better way of enforcing template instantiation...? - possible name conflict issues, you guys probably know better than I do :-) Cheers, Filip P.S.: My colleague says that this is black magic, so beware :-) #include "common.hpp" int wmain() { cont test_cont; test_cont.push_back(test(L"aaa")); test_cont.push_back(test(L"bbb")); test_cont.push_back(test(L"bbbx")); test_cont.push_back(test(L"bbbss")); test_cont.push_back(test(L"ccc", L"ddd")); return 0; // see screenshot } #ifndef MIC_VISUALIZER_HPP #define MIC_VISUALIZER_HPP template<typename T> struct multi_index_helper { }; template<typename T> struct multi_index_helper_2 { }; template<typename T> struct multi_index_helper_3 { }; #define __VISUALIZE_MIC_INDEX_DEF(Type) \ boost::multi_index::detail::multi_index_node_type< \ Type::value_type, \ Type::index_specifier_type_list, \ std::allocator<Type::value_type> >::type /// Enables MSVC visualizers for multi_index_container Type #define VISUALIZE_MULTI_INDEX_CONTAINER(Type) \ template<> \ struct multi_index_helper_2<Type> { \ typedef __VISUALIZE_MIC_INDEX_DEF(Type) index_node_type; \ typedef \ boost::base_from_member< \ boost::detail::allocator::rebind_to< \ std::allocator<Type::value_type>, \ index_node_type \ >::type> \ base_type; \ typedef \ boost::multi_index::detail::header_holder< \ index_node_type, Type> \ header_holder_type; \ typedef \ boost::multi_index::detail::multi_index_base_type< \ Type::value_type, \ Type::index_specifier_type_list, \ std::allocator<Type::value_type> >::type \ index_type; \ /* mimic multi_index_container layout */ \ base_type base; \ header_holder_type header; \ index_type index; \ unsigned int node_count; \ /* ensure that the debugger sees this template instance */ \ static void get() { \ multi_index_helper_2<Type> *ensure_inst=0; \ } \ }; \ template<> \ struct multi_index_helper_3<Type> { \ typedef __VISUALIZE_MIC_INDEX_DEF(Type) index_node_type; \ typedef \ boost::multi_index::detail::header_holder< \ index_node_type, Type> \ header_holder_type; \ typedef \ boost::multi_index::detail::multi_index_base_type< \ Type::value_type, \ Type::index_specifier_type_list, \ std::allocator<Type::value_type> >::type \ index_type; \ /* mimic multi_index_container layout from header field */ \ header_holder_type header; \ index_type index; \ unsigned int node_count; \ /* ensure that the debugger sees this template instance */ \ static void get() { \ multi_index_helper_3<Type> *ensure_inst=0; \ } \ }; \ template<> \ struct multi_index_helper<__VISUALIZE_MIC_INDEX_DEF(Type)> { \ typedef __VISUALIZE_MIC_INDEX_DEF(Type) index_node_type; \ /* mimic index_node_base<Type::value_type> layout */ \ Type::value_type value; \ /* ensure that the debugger sees this template instance */ \ static void get() { \ multi_index_helper<index_node_type> *ensure_inst=0; \ } \ }; #endif ;------------------------------- ; boost::multi_index_container ; boost::multi_index::detail::header_holder<boost::multi_index::detail::sequenced_index_node<*>,*>{ preview(#("multi_index_container data")) children( #( #list( head : *(((boost::multi_index::detail::sequenced_index_node_impl*)(boost::multi_index::detail::sequenced_index_node_trampoline<$T1>*)($c.member))->next_), size : ((multi_index_helper_3<$T2>*)&$c)->node_count, next : next_ ) : *(multi_index_helper<boost::multi_index::detail::sequenced_index_node<$T1> >*)(boost::multi_index::detail::sequenced_index_node<$T1>*)(boost::multi_index::detail::sequenced_index_node_trampoline<$T1>*)(&$e) ) ) } multi_index_helper<*> { preview(#($c.value)) children(#(value:$c.value)) } boost::multi_index::multi_index_container<*,*,*>{ preview(#($c.node_count, " nodes")) children( #( data:((multi_index_helper_2<boost::multi_index::multi_index_container<$T1,$T2,$T3> >*)&$c)->header, original members: [$c,!] ) ) }

1 1

[lambda] return statement wrapper
by Johan Nilsson 31 May '07

31 May '07

Hi, does a return statement wrapper exist in Boost.Lambda? I'd like to be able to do something conceptually similar to the following: -- #include <boost/lambda/bind.hpp> #include <boost/lambda/lambda.hpp> #include <cassert> namespace lambda = boost::lambda; void bar(int) { // whatever } void foo() { int const shouldBe3 = ( lambda::bind(&bar, 1), lambda::bind(&bar, 2), lambda::return(3) // Yes, this conflicts with the regular "return" statement, but you get the idea )(); assert(3 == shouldBe3); } --- I know I can roll my own implementation or work around it, but I was just wondering if something like that already exists. Couldn't locate anything in the docs - did I miss something? / Johan

2 2

unhandled exception (assertion) in Boost.Regexp regex_formatter with VS2005
by Andreas Sedlmeier 31 May '07

31 May '07

Hi. I am a relative newbie to two things: - Boost C++ libraries - Working with the standard C++ libraries and this is my first post on this list. Hello to everyone - I hope you'll forgive me if following question is simply stupid. I cant't even tell that. I currently need to wrap some of the functionality string algorithms and Boost.Regexp offers in Windows DLLs; the developemnt environment I use is VS2005. I started with the samples given in string algorithms which offer a different interface to some of the Boost.Regexp library. I slightly modified the sample and basically now have something like this: using namespace std; using namespace boost; string strInput ("abc__(456)__123__(123)__cde"); regex expression = "[0-9]+" string strReplaceWith("#$1#") string strResult = replace_all_regex_copy(str, expression, strReplaceWith ); This certainly does not make that much sense; its however user input I need to cope with and my problem is that I get an unhandled exception here which I cannot catch. Failure is exactly here (regex_format.hpp): template <class OutputIterator, class Results, class traits> void basic_regex_formatter<OutputIterator, Results, traits>::put(const sub_match_type& sub) { typedef typename sub_match_type::iterator iterator_type; iterator_type i = sub.first; while(i != sub.second) { put(*i); ++i; } } in the line "while(i != sub.second)" I saw that the MS standard C++ libraries compares the iterator types here. And, maybe because in my sample both - i and sub.second - are NULL here, it asserts with "string iterators incompatible". Does anybody know how to solve this problem ? Am I doing something completely wrong or is this maybe a incompatibility of Boost C++ with the MS standard C++ library and other compilers would behave different for my sample ? Any help or insight greatly appreciated. Andreas.

2 1

Specifying library locations for g++
by Scott Meyers 31 May '07

31 May '07

I've built Boost 1.34 for VC8 and g++ 4.1.1 on WinXP. I'm testing my installation with a simple program that uses Boost.FileSystem and Boost.Regex. Compilation is no problem, and for VC8, all I have to do to get things to link is add the location of the Boost binaries to the LIB environment variable. I was hoping that all I had to do for g++ was do the same for the LIBRARY_PATH environment variable (per http://gcc.gnu.org/onlinedocs/gcc/Environment-Variables.html) but I get unresolved symbol errors during linking even after doing that. I played around with the -l option (per http://gcc.gnu.org/onlinedocs/gcc/Link-Options.html#Link-Options) but nothing I tried worked. I have the following relevant binaries in my Boost binary directory: libboost_regex-mgw41-1_34.a libboost_regex-mgw41-d-1_34.a libboost_regex-mgw41-mt-1_34.a libboost_regex-mgw41-mt-d-1_34.a libboost_regex-mgw41-mt-s-1_34.a libboost_regex-mgw41-mt-sd-1_34.a libboost_regex-mgw41-s-1_34.a libboost_regex-mgw41-sd-1_34.a boost_filesystem-mgw41-1_34.a boost_filesystem-mgw41-d-1_34.a boost_filesystem-mgw41-mt-1_34.a boost_filesystem-mgw41-mt-d-1_34.a libboost_filesystem-mgw41-1_34.a libboost_filesystem-mgw41-d-1_34.a libboost_filesystem-mgw41-mt-1_34.a libboost_filesystem-mgw41-mt-d-1_34.a libboost_filesystem-mgw41-mt-s-1_34.a libboost_filesystem-mgw41-mt-sd-1_34.a libboost_filesystem-mgw41-s-1_34.a libboost_filesystem-mgw41-sd-1_34.a Can somebody explain or point me to an explanation of what I need to do to get a program using Boost binaries to link? I'm hoping there's something as simple as with VC8 where I can just specify a directory to look in and have the linker magically figure everything out from there. I'd like to avoid explicitly having to add a new library to link against each time I start using a new compiled Boost library in a project. Incidentally, in the above list of files, I notice that for Boost.FileSystem, there are some archives that start with lib and some that do not, while for regex, all start with lib. Is this meaningful? Thanks, Scott

9 23

Getting a "direct" iterator from Pointer Container
by Lost 30 May '07

30 May '07

Hi I'm using boost pointer container. Is it possible to get a "direct" iterator from Pointer Container? That's the iterator get form a normal stl iterator that points to the pointer? Thanks.

2 1

[UUID] Review results
by Hartmut Kaiser 30 May '07

30 May '07

Hi all, now, as Andy has finished his implementation (here: http://boost-consulting.com/vault/, file: uuid_v8.zip) we can move forward with the results of the review. This review has been kind of special in the sense that - it revealed some serious problems with the library to review (a license incompatibility problem and a security related problem around the random number generator scheme used), - it also spawned lots of dicussions on how to solve these problems. In the end we reached full agreement on what has to be done and Andy agreed to implement the changes. Normally, the mentioned problems would have prevented the acceptance of the library into Boost. OTOH, I think the following facts warrant not to reject the library in the first place: - The issues have already been discussed and a consensus has been reached on how to resolve the problems - Almost all reviewers found the proposed library to be incredibly useful and wanted to see the library accepted given the problems will be resolved - Andy fixed all of the significant problems in a short timeframe The final decision about the acceptance of the library will be made after a mini review of the proposed library (to be scheduled), which should concentrate on the new code presented by Andy and whether the mentioned problems have been appropriately fixed. Regards Hartmut Review Manager

1 0

compiler warnings in boost::serialization
by Os 30 May '07

30 May '07

Hi, I get a huge number of compiler warnings from the serialization and archive libraries. (This is boost 1.34.0 and Visual Studio 2005.) While I can turn them off, I'd rather not have to. The problem ones are: C4100 unreferenced formal parameter C4244 conversion from '...' to '...', possible loss of data C4265 class has virtual functions, but destructor is not virtual and new to 1.34.0 C4189 local variable is initialized but not referenced Can anything be done about this? cheers, os. -- os(a)collective.co.uk http://www.collective.co.uk/ http://www.myspace.com/darkroomtheband

1 0

Re: [Boost-users] [Boost.Test] Embedding unit testing in DLL projects
by Gennadiy Rozental 30 May '07

30 May '07

> "Tanner Davis" <tanner.davis(a)innovision.com> wrote in message > news:6704.32919073409$1180477224@news.gmane.org... > Hello- Hi, Tanner > What is the best practice for embedding test cases into library (versus > executable) projects? I have successfully used the Boost.Test framework > to build and > create EXE targeted, testing specific (MSVS) projects. However, much of > what I need to unit-test is compiled into a Win32 DLLs, and I would much > rather > embed the test cases directly within that DLL project code > (inside define blocks of course), rather than having to define a separate > project to produce an EXE > to execute the tests for each DLL. When I say "I would rather", it > really means my manager demands it. It appears that the boost.test MACROs > nicely > obfuscate the normal main()-ish entry point for the testing. I have > searched for information on overriding or extending the kick-off of > whatever calls the > init_unit_test_suite() so I could write my own custom entry points for > testing the DLL as a post-build step, but have not found what I am looking > for. Boost 1.34.0 introduced new Boost.Test variant usage specifically for this case. It's called "external test runner usage variant". The idea is to build your test module as DLL (define BOOST_TEST_DYN_LINK during compilation). Now you can run the test modult using any external test runner tool. Boost.Test supply simple command line test runner: boost_test_runner utility (it's located in libs/test). What it does essenciallty is it loads DLL dynamically, init the framework and test tree and run all the registerred test cases. > So, my question is this. Is there a provided framework for testing code > within a DLL project? And if not, is there a way to kick start the > testing from a non- > main method (say a custom DLL entry point), and would this strategy work > within the confines of Boost.Test? I believe that other well known unit > testing > framework (which shall remain nameless) supports such a thing, and I would > suspect Boost.Test does also. > > I apologize if this question is often asked or obviously documented > elsewhere. > Thank you for the assistance. The upcoming docs will cover this usage vasriants in more details. HTH, Gennadiy

1 0

[regex] ECMAScript conformance
by Armel Asselin 30 May '07

30 May '07

[boost 1.34.0, with last update to regex sources on 28th february 2007] Hello, first of all I must tell that I am very happy with boost.regex, it's fantastic. though, there are a few inconsistencies though with the ECMAScript spec. 1. it seems that re-matching an atom does not first clear its sub-matches, as "step 4" in page 135 of ECMA 262 3rd edition tells to. that is, it does what is in the 'and not' part here: /(z)((a+)?(b+)?(c))*/.exec("zaacbbbcac") which returns the array ["zaacbbbcac", "z", "ac", "a", undefined, "c"] and not ["zaacbbbcac", "z", "ac", "a", "bbb", "c"] 2. the {n,m} notation should not accept spaces in ECMAScript mode (though it's practical, it's not conformant). I easily admit that its not really important. Best regards Armel

3 2

problem with building program_options (VC8)
by Sergey Skorniakov 30 May '07

30 May '07

I have build boost libraries with command line bjam --toolset=msvc --user-config=config32.jam --stagedir=. debug-symbols=on stage File config32.jam is: using msvc : 8.0 : : <cxxflags>"-wd4996 -wd4103 -Zp4" <define>_CRT_SECURE_NO_DEPRECATE <define>_CRT_NONSTDC_NO_DEPRECATE <define>_SECURE_SCL=0 <define>BOOST_SPIRIT_THREADSAFE <define>BOOST_THREAD_USE_DLL <define>BOOST_THREAD_BUILD_DLL ; The resulting libboost_program_options-vc80-mt-1_34.lib has size 7,420,264 bytes and my program, builded with /D "_CRT_SECURE_NO_DEPRECATE" /D "_CRT_NONSTDC_NO_DEPRECATE" /D "_SECURE_SCL=0" /D "BOOST_THREAD_USE_DLL", crashes. When I changed config32.jam to using msvc : 8.0 : : <cxxflags>"-wd4996 -wd4103 -Zp4 -D_CRT_SECURE_NO_DEPRECATE -D_CRT_NONSTDC_NO_DEPRECATE -D_SECURE_SCL=0 -DBOOST_SPIRIT_THREADSAFE -DBOOST_THREAD_USE_DLL -DBOOST_THREAD_BUILD_DLL " ; The resulting libboost_program_options-vc80-mt-1_34.lib size is 7,233,568 bytes and my program works well. This looks like <define> in config file sometimes has no effect. Furthermore, program options library is alignment-sensitive.

2 2

callbacks to function template (solved)
by Ares Lagae 30 May '07

30 May '07

With the help of the boost lists I finally solved the problem of callbacks to a function template. I will describe what exactly the problem was, and how I have solved it, in the hope that it will be usefull for somebody. I am also open for suggestions and comments. Problem description ------------------- I am building a set of parsers. The parser classes pass data to the application using callbacks. Because there are potentially a lot of callbacks, and some of the callbacks are optional, I wrap each callback into a std::tr1::function object, and then pass it to the parser. The problem I came across can be simplified and abstracted to parsing a format like this one. bool 1 char 2 short 3 int 4 long 5 float 6.0 double 7.0 Each line contains a type and is followed by a value of that type. This data should be parsed and passed to the application. The types are fixed (bool, char, short, int, long, float, double). (In the actual real problem, there are more types, and "declarations" involving several types.) Solution 1 ---------- The first solution (see listing_1.cpp) registers a callback for each data type. Because each data type is handled in a similar way, there is a lot of code repetition. Solution 2 ---------- The second solution (see listing_2.cpp and variable_list.hpp) replaces the callback function by a function template. Instead of having a member variable for the callback for each data type, the member variables are grouped into a "variable_list". This is a class template that, for each type in a type list, keeps a variable. The code repetition in the parser class is eliminated, but the user still has to call "set_callback" to register a callback for each of the data types. Solution 3 ---------- The third solution (see listing_3.cpp) eliminates the similar code at the user side. Instead of calling "set_callback" to register a callback for each of the data types, a functor is constructed, that for each type constructs a std::tr1::function object that wraps the callback. That function object is passed to the parser, and the parser sets all the callbacks. This again results in similar code in the parser "set_callbacks". Solution 4 ---------- The fourth solution (see listing_4.cpp) eliminates the similar code in the parser "set_callbacks" by executing a functor for each type in the type list. This code is approximately equivalent to callbacks to a function template. Best regards, -- Ares Lagae Computer Graphics Research Group, Katholieke Universiteit Leuven http://www.cs.kuleuven.be/~ares/

2 2