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

building regex (extracted with bcp)
by Orhun Birsoy 02 Feb '06

02 Feb '06

I am trying to build the regex library which is extracted by the bcp utility. What I did: - extract the regex library C:\Development\3rdParty\boost_1_33_1>bcp regex c:\development\temp\regex - build it C:\Development\temp\regex\libs\regex\build>bjam "-sTOOLS=vc-8_0" "-sPYTHON_ROOT=C:\Program Files\Python24" "-sPYTHON_VERSION=2.4" --libdir=C:\development\temp\boost80\lib\ --includedir=C:\development\temp\boost80\include\boost80 --builddir=c:\development\temp\boost80\tmp install Unable to load Boost.Build: could not find "boost-build.jam" --------------------------------------------------------------- Attempted search from C:\Development\temp\regex\libs\regex\build up to the root Please consult the documentation at 'http://www.boost.org'. Now it looks like it needs several jam files in order to build. Are the make files only way to build the regex library extracted with bcp? -- Orhun Birsoy

3 2

RE: [Boost-users] BjÃ¶rn Karlsson's Boost Book
by James Hughes 02 Feb '06

02 Feb '06

I agree. I have the book and it has been very useful (although I have not used Boost in anger just yet as project is only just starting). He really needs to do another book that covers the rest of the library! James > -----Original Message----- > From: John Maddock [mailto:john@johnmaddock.co.uk] > Sent: 02 February 2006 10:27 > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] BjÃ¶rn Karlsson's Boost Book > > > > BjÃ¶rn Karlsson has a book out titled "Beyond the C++ Standard > > Library: An Introduction to Boost". Is this book more than just a > > print out of the existing Boost HTML documentation? > > Absolutely, actually it's a very good book IMO (and not just > because I > proofread some of the chapters!). > > Basically, it looks at a selection of core Boost libraries, > and addresses > the following questions: > > What is it? > What's it good for? > How does it make my code better and more robust? > When should I use this? > How do I use it? > > So it's a bit like an extended tutorial, but it addresses the > when and why > questions much better than I've seen anywhere else. > > John. > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users >

1 0

BjÃ¶rn Karlsson's Boost Book
by Merrill Cornish 02 Feb '06

02 Feb '06

BjÃ¶rn Karlsson has a book out titled "Beyond the C++ Standard Library: An Introduction to Boost". Is this book more than just a print out of the existing Boost HTML documentation? Merrill

3 2

[boost][serialization] How to implement serialization classes in two DLLs
by Marc Viala 02 Feb '06

02 Feb '06

Hi, I'm very sorry to post the message hereafter a second time, but I've not received any reply, maybe I've missed it. Any workaround or recommendations will be welcome because we are right now surrounded in our software development. Thanks in advance. Marc VIALA After few hour on the subject, I'm would like to have some explanations & recommendations one the boost serialization library. To explain, my problem, you will find hereafter a VC++ 7.1 project that demonstrates it. Problem Description We have involved in a large project with for example two DLLs libraries: LibA and LibB. These libraries define & implement one class, let's say libA::A and libB::B. These two classes can be serialized through boost serialization engine. The interfaces for the two classes are the same: ---------------------- struct LIBA_API A { std::vector<double> my_vector ; private: friend class boost::serialization::access; template<class Archive> void save(Archive & ar, const unsigned int version) const ; template<class Archive> void load(Archive & ar, const unsigned int version) ; BOOST_SERIALIZATION_SPLIT_MEMBER() }; LIBA_API void save(const libA::A* pObj, std::ostream& os) ; LIBA_API void load(libA::A* &pObj, std::istream& is) ; }; // Namespace libA ---------------------- The two free functions save() and load() are defined to be able to serialize the class libA::A (respectively the class libB::B). When, we try to use these interfaces in an EXE application: ---------------------- #include <LibA/A.h> #include <LibB/B.h> #include <boost/filesystem/path.hpp> #include <boost/filesystem/fstream.hpp> #pragma comment(lib, "liba_d.lib") #pragma comment(lib, "libb_d.lib") int main(int argc, char* argv[]) { libA::A a; libA::save(&a, boost::filesystem::ofstream("a.xml")); libB::B b; libB::save(&b, boost::filesystem::ofstream("b.xml")); // -> Assert in debug mode return 0; } ---------------------- The figure hereafter describes the relationships between LibA, LibB and EXE application: ------------ ------------ | LibA | | LibB | ------------ ------------ \ / \ / Exe Application We have to face to an assert in debug mode generate by the file boost::serialization::extended_type_info.cpp, line#71. This assert happens during the instance serialization of class libB:B. Recently, there are some posts on this subject, but I would like to known how I can deal with this assert? Is it possible to avoid it by a code organisation? Is it possible to comment this assert? To have a concrete answer, I have joined my complete VC++7.1 project. Thanks in advance for your help. Development Platform WindowsXP VC++ 7.1 Boost 1.33.1 Marc Viala mailto:mviala@acticm.com <mailto:mviala@acticm.com>

3 2

Re: [Boost-users] trying to install Boost 1.33.1 on Solaris 5.9 + SunStudio 11
by paul.floyd 02 Feb '06

02 Feb '06

... > If found this in the sun forum. > http://blogs.sun.com/roller/page/sga > Contains a patch to boost 1.33.1 and 1.32.0 to help compiling on sun. Very interesting. Can anyone comment as to whether these changes are going to be integrated to boost? They haven't been yet (at least in the code that I can browse with the web interface). A+ Paul Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,34 /mn) ; tél : 08 92 68 13 50 (0,34/mn)

3 5

[program_options] Uncatchable Errors
by Merrill Cornish 02 Feb '06

02 Feb '06

I have a minimal program below that uses the program_options library. If executed with no options or with --help as an option, it correctly prints "End of option processing" and does nothing else. However, if you give it an unexpected option such as --x, then (in my case) Zone Alert pops up saying that "somone" is trying to launch Dr Watson. If the try/catch is omitted, a message is printed to the console: "This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information." Am I doing something wrong to make unexpected options behave so badly? Merrill ========================================== #include <iostream> #include <stdexcept> #include "boost/program_options.hpp" namespace po = boost::program_options; using namespace std; int main(int argc, char* argv[]) { try { po::options_description general_verbose("Options"); general_verbose.add_options() ("help,h", " Display this help message."); po::variables_map vm; po::store(po::command_line_parser(argc, argv). options(general_verbose).run(), vm); po::notify(vm); }//try catch(std::exception ex) { cout << "Exception: " << ex.what() << endl; } catch(...) { cout << "Unknown exception." << endl; } cout << "End of option processing." << endl; }//main()

1 0

[python] create a custom exception
by boost.users＠cgrealy.mailcan.com 02 Feb '06

02 Feb '06

Is it possible to create a C++ to python exception translator that raises a custom python exception? I know you can use register_exception_translator to translate from a c++ exception to a standard python exception, but is it possible to raise a user-defined exception? Regards, Colin

2 1

Re: [Boost-users] [serialization] compile error
by cheesy4poofs 02 Feb '06

02 Feb '06

> I compiled the following program wiht no errors on my vc 7.1 > system with no errors or warnings > > Robert Ramey I finally solved my problem by commenting out the following include: //#include <boost/serialization/base_object.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/archive/text_oarchive.hpp> #include <boost/serialization/map.hpp> Not sure why it solved it, but I'm glad at least to have put this behind me. Thanks for the help. Scott

3 2

[serialization] Removing empty classes
by Loïc Joly 01 Feb '06

01 Feb '06

Hello, Let's say I have a structure suce as this : class A {}; class B : public A {}; class C : public B {}; Currently, I have some code that looks like this : template<class Archive> void C::serialize(Archive &ar, const unsigned int version) { ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(B); } However, if my class B is "empty", that is it adds no data to A, is this possible as an optimisation to just write : template<class Archive> void C::serialize(Archive &ar, const unsigned int version) { ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(A); } Or will this break something ? -- Loïc

2 1

Re: [Boost-users] [serialization] compile error
by cheesy4poofs 01 Feb '06

01 Feb '06

>Try removing the line > >> #include <boost/serialization/type_info_implementation.hpp> > >And let me know that happens. > >I believe this problem is a remnant of a header depency issue which will be addressed in > the next release. > >Robert Ramey Thanks for the response. I actually didn't have that #include in my original code. I added it in a futile attempt to see if that would fix the issue. I still see the same compile errors when I remove that #include line. Scott

2 1

[Serialization]: bug while serializing a std:string
by RIVASSEAU Jean Noel 01 Feb '06

01 Feb '06

Hello It seems I have come against a bug in the BSL. I am running on Win 2000 Pro, MinGW (gcc 3.4.2), Boost 1.33.1. If I serialize a standard string with 512 or more characters, the save goes ok but a stream error exception occurs while trying to reload it later from archive. Any string with size < 512 is ok. Also this bug is really strange. It does not happen if the string has no line breaks in it (even if it is more than 512 chars). It also happens on my program, but I was unable to reproduce it with a small test program, even using the same string. Could it be a bug in another part of my rather large program? Or is it really a bug in the BSL? Jean-Noël

2 1

Bug with std::string in the BSL
by RIVASSEAU Jean Noel 01 Feb '06

01 Feb '06

Hello Following my previous message, I have not been able to track down the bug. What I noticed is that the stream error occurs after the loading of the std::string (on the next load operation), however the loaded string is not correct (eg, even if the exception is thrown later, the problem lies with the strings of length >= 512). Robert, if you cannot look into that, can you give me some pointers about where should I look to debug this problem? I am using a text archive. Hints about the implementation code would be useful for me. Thank you Jean-Noël

1 0

[date_time] Constructing a ptime with __int64
by Christian Henning 01 Feb '06

01 Feb '06

Hi there, is it possible to construct a ptime with an __int64. The internal representation is of the same type. I couldn't find anything on this issue. Thanks in advance, Christian

2 4

Re: [Boost-users] Using lambda to count elements in list of lists
by Daniel Lidström 01 Feb '06

01 Feb '06

Sebastian Redl scribbled: > Yes, but you need binding syntax: > > typedef list< list< int > > lli; > for_each(ll.begin(), ll.end(), var(count) += bind(&lli::size, _1)); Thanks to both Sebastian and Stuart! Hälsningar, Daniel

1 0

Compiling boost with vacpp 8.0 as 64bit on AIX5.3ml3 of power5
by Kamil Marcinkowski 01 Feb '06

01 Feb '06

Hello, I need to compile boost as a 64 bit program using vacpp 8.0 compiler, on AIX 5.3ml3, power5, p5-550 and p5-595. I can compile boost with vacpp in 32bit mode fine, but all my attempts at compiling it 64 bit have not resulted with any success so far. The vacpp toolset does not offer any options and does not allow for any options or configuration variables. I do not understand the syntax of the vacpp-tools.jam file or (bjam in general) and cannot edit the file with any success. I just need the following flags passed to the compiler: <cxxflags> -q64 <linkflags> -q64 <arflags> -q64 Thanks, Kamil Kamil Marcinkowski Westgrid System Administrator kamil(a)ualberta.ca University of Alberta site Tel.780 492-0354 Research Computing Support Fax.780 492-1729 Academic ICT (formerly CNS) Edmonton, Alberta, CANADA University of Alberta "This communication is intended for the use of the recipient to which it is addressed, and may contain confidential, personal, and/or privileged information. Please contact us immediately if you are not the intended recipient of this communication. If you are not the intended recipient of this communication, do not copy, distribute, or take action on it. Any communication received in error, or subsequent reply, should be deleted or destroyed."

3 2

unresolved program_options::arg
by Matthieu Paindavoine 01 Feb '06

01 Feb '06

Hello, I am compiling a program which uses the program_options library, and I am getting an unresolved symbol (boost::program_options::arg class std::basic_string<char, struct std::traits<char>, class std::allocator<char> > ). This is using the vc-7_1 toolset (boost 1.33.1, bjam --v2). I don't have such problem on Linux g++ 3.4.4 I see it in the value_semantic.cpp. If I play with setting <boost/config/user.hpp : BOOST_ALL_DYN_LINK> I can get it to compile, but it sends a warning 'inconsistent linkage', and later crashes on dbgheap.hpp I have compiled program_options with --v2 -stoolset=vc-7_1 -slink=shared -sthreading=multi -svariant=debug, and the same with my program. I've also added -sruntime-link=dynamic, same problem. Are there other options that need to be set before compiling program_options? Where is arg going to be defined if its external? I know it's something I'm doing wrong, can someone please help. Thanks Matthieu

1 0

Using lambda to count elements in list of lists
by Daniel Lidström 01 Feb '06

01 Feb '06

Hello! I'm trying to use Boost.Lambda to count the total number of elements in a list of lists. This example shows what I'm trying to do: #include <boost/lambda/lambda.hpp> #include <algorithm> #include <list> using namespace std; using namespace boost::lambda; int main() { int count = 0; list<list<int> > ll; for_each(ll.begin(), ll.end(), var(count)+=(_1).size()); } This will not compile: (13): error C2039: 'size': is not a member of 'boost::lambda::lambda_functor<T>' Is this possible to do? Thanks in advance! Hälsningar, Daniel

5 4

Boost Threads documentation
by James Hughes 01 Feb '06

01 Feb '06

Hello all, I am reading thought he thread docs on the Boost site, which are all dated around 2004/2005. Is there any more recent documentation, as this stuff refers to features not yet present, which I think are there now. James

1 0

Re: [Boost-users] trying to install Boost 1.33.1 on Solaris 5.9 + SunStudio 11
by Xavier.Abulker＠fimat.com 01 Feb '06

01 Feb '06

Thank you everybody for you help, The SUN patch solved my problem. Regards Xavier.Abulker(a)fimat.com wrote: > Hello, > I'm trying to install Boost 1.33.1 on a Sun Solaris 5.9 Sunpro 11 and > after the command: > bjam "-sTOOLS=sunpro" install > I receive the error message: > > >>> Assertion: (../lnk/init.cc, line 1032) >>> > while processing /ftx/opt/SUNWspro/prod/include/CC/Cstd/rw/messages.cc > at line 0. > >> Assertion: (../lnk/init.cc, line 1032) > while processing /ftx/opt/SUNWspro/prod/include/CC/Cstd/rw/messages.cc > at line 0. > > Do you know how I can solve this problem? > It looks like Sun has released a patch to solve the error "Assertion: > (../lnk/init.cc, line 1032)" but I can't find it for solaris 5.9 + Studio > 11 > You need the latest set of patches for both the compiler and the back end - you can download those from SUN. I've been experimenting with those with a view to run Boost regression tests on Solaris (10 in my case) and with the latest patchset installed it will still fail to compile about 60 to 80 targets out of the close to 1300 for the 'stage' target. In my experience this is the best result for any Sun compiler so far. As mentioned in the other email it is worth compiling it against stlport and not the older RogueWave library. Regards, Timo _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost ************************************************************************* Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. La FIMAT et ses filiales declinent toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. ******** This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. Neither FIMAT nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified.

1 0

trying to install Boost 1.33.1 on Solaris 5.9 + SunStudio 11
by Xavier.Abulker＠fimat.com 01 Feb '06

01 Feb '06

Hello, I'm trying to install Boost 1.33.1 on a Sun Solaris 5.9 Sunpro 11 and after the command: bjam "-sTOOLS=sunpro" install I receive the error message: >> Assertion: (../lnk/init.cc, line 1032) while processing /ftx/opt/SUNWspro/prod/include/CC/Cstd/rw/messages.cc at line 0. >> Assertion: (../lnk/init.cc, line 1032) while processing /ftx/opt/SUNWspro/prod/include/CC/Cstd/rw/messages.cc at line 0. Do you know how I can solve this problem? It looks like Sun has released a patch to solve the error "Assertion: (../lnk/init.cc, line 1032)" but I can't find it for solaris 5.9 + Studio 11 Regards Xavier ************************************************************************* Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. La FIMAT et ses filiales declinent toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. ******** This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. Neither FIMAT nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified.

3 3

Re: [Boost-users] Getting started with Boost: what did you need to know?
by Merrill Cornish 01 Feb '06

01 Feb '06

David, Having an introductory video to _Boost_ is problematic since there's no one thing called "Boost". Instead, it's a collection of often disparate libraries. Each of the libraries could reasonably be featured in its only "getting started" video. However, if the point is to _sell_ the whole Boost idea, then one alternative would be to bypass the details of syntax and function calls of the various libraries in favor of a "Why do you need Boost" talk/pitch/video. Talk about what kind of everyday problems it solves for you rather than trying to explain the nitty gritty (and 200 levels of nested template declarations) of each library. The pitch would verbally sketch (i.e. probably no code) a real world programming problem, then point out what the Boost library has to help out. A series of problem sketches would allow the pitch to cover a lot of otherwise disjoint Boost functionality and still make sense. Merrill

2 1

[BGL] adjacency_list: OutEdgeList vs EdgeList
by Johan Oudinet 31 Jan '06

31 Jan '06

Hi, I can't understand the difference between the OutEdgeList and EdgeList adjacency_list parameters. I think the documentation is unclear about EdgeList (especialy http://www.boost.org/libs/graph/doc/using_adjacency_list.html which has a section about "Choosing the Edgelist and VertexList" but only OutEdgeList and VertexList are present in this section) I need fast access to edge_properties from edge_descriptor. But I couldn't find if OutEdgeList or EdgeList container is used for the operator[] ? I read that EdgeList doesn't exist in previous version of the BGL and OutEdgeList was called EdgeList. So I suspect their are still mistakes in the adjacency_list documentation. Regards, -- Johan Oudinet

1 0

[filesystem] mistakable documentation
by marcoh77＠freenet.de 31 Jan '06

31 Jan '06

Hello! Is it possible to expand the filesystem documentation? ---8<------------------------ Native paths should be created with the 'native' argument, like this: boost::filesystem::path p("C:/test.txt", native); ---8<------------------------ For a novice it's impossible to create a path objekt with a native syntax because it's missing in the beginner tutorial. I have tried to create a path object and I got only exceptions. After a long journey in google and the boost mailinglists I have found a source example with the native argument. The documentation of boost::filesystem doesn't explain this part in the beginners guide as expected. Of course it is explained in the detailed documentation, but this is to far away. ;-) I hope my suggestion will be accepted. Thanx! :-) Best regards Amin

1 0

Re: [Boost-users] Getting started with Boost: what did you need to know?
by Marco Wahl 31 Jan '06

31 Jan '06

Maybe this is somewhat off topic but I didn't want the idea to get lost. What about having a getting-started-video for Boost. Maybe someone could film Davids 'Getting started with Boost' sessions. -- Marco Wahl icq 284789053

2 1

Compile error with serialization
by cheesy4poofs 31 Jan '06

31 Jan '06

I'm using Windows XP with Visual Studio 2003. I've compiled boost 1.33.1 successfully with bjam and installed the libs and DLLs into my environment. I started playing with the serialization library. I created a win32 console project and copied in the demo.cpp serialization program. It compiles and runs just fine. I then started added serialization to my own project and started running into problem after problem. I've since commented out all my own code except for the following: I copied the gps_position class directly from demo.cpp into my project. At the top of the file, I've included the following files: #include <boost/serialization/type_info_implementation.hpp> #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/serialization/base_object.hpp> #include <boost/serialization/utility.hpp> In my class Manager, I wrote the following method: void Manager::save(const std::string & filename) { boost::recursive_mutex::scoped_lock lock(_nodeMutex); std::ofstream outFile; outFile.open(filename.c_str(), std::ios::binary); boost::archive::text_oarchive archiveFile(outFile); // simple test const gps_position g; archiveFile << g; outFile.close(); } Trying to compile, I get the following errors: ..\API\inc\boost\archive\detail\oserializer.hpp(131) : error C2027: use of undefined type 'boost::serialization::extended_type_info_null<T>' with [ T=gps_position ] ..\API\inc\boost\archive\detail\oserializer.hpp(131) : see reference to class template instantiation 'boost::serialization::extended_type_info_null<T>' being compiled with [ T=gps_position ] ..\API\inc\boost\archive\detail\oserializer.hpp(128) : while compiling class-template member function 'bool boost::archive::detail::oserializer<Archive,T>::is_polymorphic(void) const' with [ Archive=boost::archive::text_oarchive, T=gps_position ] ..\API\inc\boost\archive\detail\oserializer.hpp(264) : see reference to class template instantiation 'boost::archive::detail::oserializer<Archive,T>' being compiled with [ Archive=boost::archive::text_oarchive, T=gps_position ] . . . *snip* As far as my project settings, I'm compiling a win32 DLL, with the Multithread Debug C++ standard library DLL. I have exceptions and RTTI enabled. Basically the same settings I used for compiling demo.cpp. If I comment out the "archiveFile << g;" line, it compiles fine. Any help would be greatly appreciated! Thank you, Scott

2 1

How do i access graph property?
by Jef Driesen 31 Jan '06

31 Jan '06

Suppose I have defined the following graph: typedef boost::adjacency_list< boost::setS, // Adjacency list boost::setS, // Vertex list boost::undirectedS, // Undirected graph unsigned int, // Vertex property (unique label) boost::no_property, // Edge property unsigned int, // Graph property (next unique label) boost::listS // Edge list > graph; How do I access the graph property? For the vertex property this is a very simple operation: graph g = ...; vertex_descriptor u = ...; vertex_property label = g[u]; But I can't find a way to access property associated with my graph. How can I do this?

2 1

Boost Graph Library - heap profile
by Dave 31 Jan '06

31 Jan '06

Hello All, I am looking into heap profiles of some example programs given in Boost Graph Library and I would like to know if there is any garbage collection or memory compaction done by BGL's memory allocator. Thank you. Dave --------------------------------- Bring words and photos together (easily) with PhotoMail - it's free and works with your Yahoo! Mail.

2 1

[serialization] Problem with multiple multi-index keys.
by Toby Smith 31 Jan '06

31 Jan '06

Hi, I'm having a problem serializing a multi-index container. Serialization used to work fine, until I added a second (non-unique) key to the container. I've managed to distill the problem down to a small bit of code, so here it is. Uncomment the #define to see the segfault at serialization time in action, leave it commented and the example code works fine. I'm clearly missing something subtle (or not-so-subtle) here, but I don't have the first clue what it might be. Suggestions are enormously appreciated. Regards, tob ---------------------------------------------------------------------------- // A simple program to illustrate my crazy serialization problem with // multi-index containers. Compiled with: // g++ -I/usr/local/include/boost-1_33_1/ boost_test.c++ \ // -lboost_serialization -o boost_test // // When two keys are specified for FooSet, serialization segfaults. When // only one key is present, we're fine. Uncomment the line below to see // the segfault in action. // #define KILL_SERIALIZATION #include <fstream> #include <string> #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/multi_index_container.hpp> #include <boost/multi_index/member.hpp> #include <boost/multi_index/ordered_index.hpp> struct Foo { Foo() : _id(0) { } Foo(unsigned id) : _id(id) { } unsigned _id; std::string _name; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & _id; ar & _name; } }; // Container for class Foo struct foo_id_tag { }; struct foo_name_tag { }; typedef boost::multi_index_container< Foo, boost::multi_index::indexed_by< boost::multi_index::ordered_unique< boost::multi_index::tag<foo_id_tag>, BOOST_MULTI_INDEX_MEMBER(Foo, unsigned, _id) #if defined(KILL_SERIALIZATION) >, boost::multi_index::ordered_non_unique< boost::multi_index::tag<foo_name_tag>, BOOST_MULTI_INDEX_MEMBER(Foo, std::string, _name) #endif > > > FooSet; void save(const FooSet& fooSet) { std::ofstream ofs("foo"); boost::archive::text_oarchive oa(ofs); oa << fooSet; } int main(int argc, char** argv) { FooSet foo_set; foo_set.insert(Foo(100)); foo_set.insert(Foo(150)); save(foo_set); return 0; }

2 2

Iterators and algorithms
by Jiri Palecek 31 Jan '06

31 Jan '06

Hello, I have recently tried to implement merging of more lists (or union of more sets). The (somewhat silly) approach would be set<X> ret,ret2; for(list<set<X> >::iterator it=sets.begin(),end=sets.end();it!=end;++it) { set_union(ret.begin(),ret.end(),it->begin(),it->end(),inserter(ret2)); ret.clear(); swap(ret,ret2); } and ret is the result. However, it seems to me that these temporaries are unnecessary. So I wonder wheter there could/should be some class of iterators that implemented some STL algorithms. There is already an iterator that could replace the unary version of transform (transform_iterator) In my case, I'm talking about some merge_iterator that would merge two sorted sequences (being an input iterator). That is, copy(merger(a.begin(),a.end(),b.begin(),b.end()),ostream_iterator(cout)) would be equivalent to merge(a.begin(),a.end(),b.begin(),b.end(),ostream_iterator(cout)) and similarly for set_union etc. Is it possible to have such iterators? Sincirely Jiri Palecek

1 0

Re: [Boost-users] Spawning a thread on a member function
by Sliwa, Przemyslaw (London) 31 Jan '06

31 Jan '06

Ok, I am using VC++ 6, SP5. The class has a member function void CDailyReportTree::foo() { } I am trying to spawn a thread from void CDailyReportTree::DrawHistoryTree(HTREEITEM item, const set<pair<string, string>, comp<string, string> >& nodes, const CString& filename) { map<string, pair<CString, HTREEITEM>, comp<string, pair<CString, HTREEITEM> > > localMap; for (set<pair<string, string>, comp<string, string> >::const_iterator i_ptr=nodes.begin(); i_ptr!=nodes.end(); ++i_ptr) { HTREEITEM reportItem = InsertItem(TVIF_IMAGE|TVIF_TEXT|TVIF_SELECTEDIMAGE, i_ptr->first.c_str(), 7,8, TVIS_BOLD, TVIF_TEXT, 0, item, item); localMap.insert(make_pair(i_ptr->first, make_pair(i_ptr->second.c_str(), reportItem))); } boost::bind(foo, this); } And I am getting lots of errors. Can anyone help? The errors are: DailyReportTree.cpp Note: Using precompiled header C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2784: 'class boost::_bi::bind_t<R,class boost::_mfi::dm<R,T>,class boost::_bi::list1<class boost::_bi::value<R> > > __cdecl boost::bind(R T::*,A1)' : could not deduce template argument for 'overloaded function type' from 'overloaded function type' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,struct boost::_mfi::cmf8<R,T,B1,B2,B3,B4,B5,B6,B7,B8>,class boost::_bi::list9<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::valu e<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::bind(R (__thiscall T::*)(B1,B2,B3,B4,B5,B6,B7,B8) const,A1,A2,A 3,A4,A5,A6,A7,A8,A9)' : expects 10 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_mf_cc.hpp(222) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,struct boost::_mfi::mf8<R,T,B1,B2,B3,B4,B5,B6,B7,B8>,class boost::_bi::list9<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value <R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::bind(R (__thiscall T::*)(B1,B2,B3,B4,B5,B6,B7,B8),A1,A2,A3,A4,A5 ,A6,A7,A8,A9)' : expects 10 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_mf_cc.hpp(211) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,struct boost::_mfi::cmf7<R,T,B1,B2,B3,B4,B5,B6,B7>,class boost::_bi::list8<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R >,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::bind(R (__thiscall T::*)(B1,B2,B3,B4,B5,B6,B7) const,A1,A2,A3,A4,A5,A6,A7,A8)' : expects 9 ar guments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_mf_cc.hpp(198) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,struct boost::_mfi::mf7<R,T,B1,B2,B3,B4,B5,B6,B7>,class boost::_bi::list8<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R> ,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::bind(R (__thiscall T::*)(B1,B2,B3,B4,B5,B6,B7),A1,A2,A3,A4,A5,A6,A7,A8)' : expects 9 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_mf_cc.hpp(187) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,struct boost::_mfi::cmf6<R,T,B1,B2,B3,B4,B5,B6>,class boost::_bi::list7<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,c lass boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::bind(R (__thiscall T::*)(B1,B2,B3,B4,B5,B6) const,A1,A2,A3,A4,A5,A6,A7)' : expects 8 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_mf_cc.hpp(174) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,struct boost::_mfi::mf6<R,T,B1,B2,B3,B4,B5,B6>,class boost::_bi::list7<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,cl ass boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::bind(R (__thiscall T::*)(B1,B2,B3,B4,B5,B6),A1,A2,A3,A4,A5,A6,A7)' : expects 8 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_mf_cc.hpp(163) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,struct boost::_mfi::cmf5<R,T,B1,B2,B3,B4,B5>,class boost::_bi::list6<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,clas s boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::bind(R (__thiscall T::*)(B1,B2,B3,B4,B5) const,A1,A2,A3,A4,A5,A6)' : expects 7 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_mf_cc.hpp(150) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,struct boost::_mfi::mf5<R,T,B1,B2,B3,B4,B5>,class boost::_bi::list6<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::bind(R (__thiscall T::*)(B1,B2,B3,B4,B5),A1,A2,A3,A4,A5,A6)' : expects 7 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_mf_cc.hpp(139) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,struct boost::_mfi::cmf4<R,T,B1,B2,B3,B4>,class boost::_bi::list5<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class b oost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::bind(R (__thiscall T::*)(B1,B2,B3,B4) const,A1,A2,A3,A4,A5)' : expects 6 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_mf_cc.hpp(126) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,struct boost::_mfi::mf4<R,T,B1,B2,B3,B4>,class boost::_bi::list5<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class bo ost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::bind(R (__thiscall T::*)(B1,B2,B3,B4),A1,A2,A3,A4,A5)' : expects 6 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_mf_cc.hpp(115) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,struct boost::_mfi::cmf3<R,T,B1,B2,B3>,class boost::_bi::list4<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boos t::_bi::value<R> > > __cdecl boost::bind(R (__thiscall T::*)(B1,B2,B3) const,A1,A2,A3,A4)' : expects 5 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_mf_cc.hpp(102) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,struct boost::_mfi::mf3<R,T,B1,B2,B3>,class boost::_bi::list4<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost ::_bi::value<R> > > __cdecl boost::bind(R (__thiscall T::*)(B1,B2,B3),A1,A2,A3,A4)' : expects 5 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_mf_cc.hpp(91) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,struct boost::_mfi::cmf2<R,T,B1,B2>,class boost::_bi::list3<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl b oost::bind(R (__thiscall T::*)(B1,B2) const,A1,A2,A3)' : expects 4 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_mf_cc.hpp(78) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,struct boost::_mfi::mf2<R,T,B1,B2>,class boost::_bi::list3<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl bo ost::bind(R (__thiscall T::*)(B1,B2),A1,A2,A3)' : expects 4 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_mf_cc.hpp(67) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,struct boost::_mfi::cmf1<R,T,B1>,class boost::_bi::list2<class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::bind(R (__thiscall T::*) (B1) const,A1,A2)' : expects 3 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_mf_cc.hpp(54) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,struct boost::_mfi::mf1<R,T,B1>,class boost::_bi::list2<class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::bind(R (__thiscall T::*)( B1),A1,A2)' : expects 3 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_mf_cc.hpp(43) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2784: 'class boost::_bi::bind_t<R,struct boost::_mfi::cmf0<R,T>,class boost::_bi::list1<class boost::_bi::value<R> > > __cdecl boost::bind(R (__thiscall T::*)(void) const,A1)' : could not deduce template argument for 'overloaded function type' from 'overloaded function type' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2784: 'class boost::_bi::bind_t<R,struct boost::_mfi::mf0<R,T>,class boost::_bi::list1<class boost::_bi::value<R> > > __cdecl boost::bind(R (__thiscall T::*)(void),A1)' : could not deduce template argument for 'overloaded function type' from 'overloaded function type' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::?$bind_t@$DBAB@P6A?AVtemplate-parameter-BAB@Vtemplate-parame ter-BAC@Vtemplate-parameter-BAD@Vtemplate-parameter-BAE@Vtemplate-parame ter-BAF@Vtemplate-parameter-BAG @Vtemplate-parameter-BAH@Vtemplate-parameter-BAI@Vtemplate-parameter-BAJ @Vtemplate-parameter-BAK@@ZV?$list9@V?$value@$DBAB@@_bi@boost@@V123@V123 @V123@V123@V123@V123@V123@V123@@_bi@boost@@ __cdecl boost::bind(R (__cdecl *)(B1,B2,B3,B4,B5,B6,B7,B8,B9) ,A1,A2,A3,A4,A5,A6,A7,A8,A9)' : expects 10 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_cc.hpp(112) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::?$bind_t@$DBAB@P6A?AVtemplate-parameter-BAB@Vtemplate-parame ter-BAC@Vtemplate-parameter-BAD@Vtemplate-parameter-BAE@Vtemplate-parame ter-BAF@Vtemplate-parameter-BAG @Vtemplate-parameter-BAH@Vtemplate-parameter-BAI@Vtemplate-parameter-BAJ @@ZV?$list8@V?$value@$DBAB@@_bi@boost@@V123@V123@V123@V123@V123@V123@V12 3@@_bi@boost@@ __cdecl boost::bind(R (__cdecl *)(B1,B2,B3,B4,B5,B6,B7,B8),A1,A2,A3,A4,A5,A6,A7,A8)' : exp ects 9 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_cc.hpp(101) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::?$bind_t@$DBAB@P6A?AVtemplate-parameter-BAB@Vtemplate-parame ter-BAC@Vtemplate-parameter-BAD@Vtemplate-parameter-BAE@Vtemplate-parame ter-BAF@Vtemplate-parameter-BAG @Vtemplate-parameter-BAH@Vtemplate-parameter-BAI@@ZV?$list7@V?$value@$DB AB@@_bi@boost@@V123@V123@V123@V123@V123@V123@@_bi@boost@@ __cdecl boost::bind(R (__cdecl *)(B1,B2,B3,B4,B5,B6,B7),A1,A2,A3,A4,A5,A6,A7)' : expects 8 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_cc.hpp(90) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::?$bind_t@$DBAB@P6A?AVtemplate-parameter-BAB@Vtemplate-parame ter-BAC@Vtemplate-parameter-BAD@Vtemplate-parameter-BAE@Vtemplate-parame ter-BAF@Vtemplate-parameter-BAG @Vtemplate-parameter-BAH@@ZV?$list6@V?$value@$DBAB@@_bi@boost@@V123@V123 @V123@V123@V123@@_bi@boost@@ __cdecl boost::bind(R (__cdecl *)(B1,B2,B3,B4,B5,B6),A1,A2,A3,A4,A5,A6)' : expects 7 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_cc.hpp(79) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::?$bind_t@$DBAB@P6A?AVtemplate-parameter-BAB@Vtemplate-parame ter-BAC@Vtemplate-parameter-BAD@Vtemplate-parameter-BAE@Vtemplate-parame ter-BAF@Vtemplate-parameter-BAG @@ZV?$list5@V?$value@$DBAB@@_bi@boost@@V123@V123@V123@V123@@_bi@boost@@ __cdecl boost::bind(R (__cdecl *)(B1,B2,B3,B4,B5),A1,A2,A3,A4,A5)' : expects 6 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_cc.hpp(68) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::?$bind_t@$DBAB@P6A?AVtemplate-parameter-BAB@Vtemplate-parame ter-BAC@Vtemplate-parameter-BAD@Vtemplate-parameter-BAE@Vtemplate-parame ter-BAF@@ZV?$list4@V?$value@$DB AB@@_bi@boost@@V123@V123@V123@@_bi@boost@@ __cdecl boost::bind(R (__cdecl *)(B1,B2,B3,B4),A1,A2,A3,A4)' : expects 5 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_cc.hpp(57) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::?$bind_t@$DBAB@P6A?AVtemplate-parameter-BAB@Vtemplate-parame ter-BAC@Vtemplate-parameter-BAD@Vtemplate-parameter-BAE@@ZV?$list3@V?$va lue@$DBAB@@_bi@boost@@V123@V123 @@_bi@boost@@ __cdecl boost::bind(R (__cdecl *)(B1,B2,B3),A1,A2,A3)' : expects 4 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_cc.hpp(46) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::?$bind_t@$DBAB@P6A?AVtemplate-parameter-BAB@Vtemplate-parame ter-BAC@Vtemplate-parameter-BAD@@ZV?$list2@V?$value@$DBAB@@_bi@boost@@V1 23@@_bi@boost@@ __cdecl boost:: bind(R (__cdecl *)(B1,B2),A1,A2)' : expects 3 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_cc.hpp(35) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2784: 'class boost::_bi::?$bind_t@$DBAB@P6A?AVtemplate-parameter-BAB@Vtemplate-parame ter-BAC@@ZV?$list1@V?$value@$DBAB@@_bi@boost@@@_bi@boost@@ __cdecl boost::bind(R (__cdecl *)(B1),A1)' : could not deduce template argument for 'overloaded function type' from 'overloaded function type' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,class boost::_bi::XZVlist0::R (__cdecl*)( ?? ) throw( ?? )> __cdecl boost::bind(R (__cdecl *)(void))' : expects 1 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind/bind_cc.hpp(17) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,F,class boost::_bi::list9<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::va lue<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::bind(struct boost::type<R>,F,A1,A2,A3,A4,A5,A6,A7,A8,A9)' : expects 11 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind.hpp(1380) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,F,class boost::_bi::list8<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::va lue<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::bind(struct boost::type<R>,F,A1,A2,A3,A4,A5,A6,A7,A8)' : expects 10 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind.hpp(1372) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,F,class boost::_bi::list7<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::va lue<R>,class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::bind(struct boost::type<R>,F,A1,A2,A3,A4,A5,A6,A7)' : expects 9 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind.hpp(1364) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,F,class boost::_bi::list6<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::va lue<R>,class boost::_bi::value<R> > > __cdecl boost::bind(struct boost::type<R>,F,A1,A2,A3,A4,A5,A6)' : expects 8 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind.hpp(1356) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,F,class boost::_bi::list5<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::va lue<R> > > __cdecl boost::bind(struct boost::type<R>,F,A1,A2,A3,A4,A5)' : expects 7 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind.hpp(1348) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,F,class boost::_bi::list4<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::b ind(struct boost::type<R>,F,A1,A2,A3,A4)' : expects 6 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind.hpp(1340) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,F,class boost::_bi::list3<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::bind(struct boost::type<R>,F ,A1,A2,A3)' : expects 5 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind.hpp(1332) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,F,class boost::_bi::list2<class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::bind(struct boost::type<R>,F,A1,A2)' : expects 4 argume nts - 2 provided c:\vendor_libs\VC60\include\boost/bind.hpp(1324) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,F,class boost::_bi::list1<class boost::_bi::value<R> > > __cdecl boost::bind(struct boost::type<R>,F,A1)' : expects 3 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind.hpp(1316) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2784: 'class boost::_bi::bind_t<R,F,class boost::_bi::list0> __cdecl boost::bind(struct boost::type<R>,F)' : could not deduce template argument for 'overloaded function type' from 'overloa ded function type' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,F,class boost::_bi::list9<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::va lue<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::bind(F,A1,A2,A3,A4,A5,A6,A7,A8,A9)' : expects 10 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind.hpp(1298) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,F,class boost::_bi::list8<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::va lue<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::bind(F,A1,A2,A3,A4,A5,A6,A7,A8)' : expects 9 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind.hpp(1290) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,F,class boost::_bi::list7<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::va lue<R>,class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::bind(F,A1,A2,A3,A4,A5,A6,A7)' : expects 8 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind.hpp(1282) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,F,class boost::_bi::list6<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::va lue<R>,class boost::_bi::value<R> > > __cdecl boost::bind(F,A1,A2,A3,A4,A5,A6)' : expects 7 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind.hpp(1274) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,F,class boost::_bi::list5<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::va lue<R> > > __cdecl boost::bind(F,A1,A2,A3,A4,A5)' : expects 6 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind.hpp(1266) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,F,class boost::_bi::list4<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::b ind(F,A1,A2,A3,A4)' : expects 5 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind.hpp(1258) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,F,class boost::_bi::list3<class boost::_bi::value<R>,class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::bind(F,A1,A2,A3)' : expects 4 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind.hpp(1250) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,F,class boost::_bi::list2<class boost::_bi::value<R>,class boost::_bi::value<R> > > __cdecl boost::bind(F,A1,A2)' : expects 3 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind.hpp(1242) : see declaration of 'bind' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2783: 'class boost::_bi::bind_t<R,F,class boost::_bi::list1<class boost::_bi::value<R> > > __cdecl boost::bind(F,A1)' : could not deduce template argument for 'R' C:\cfxa_build\FXRiskEngine\DailyReportTree.cpp(699) : error C2780: 'class boost::_bi::bind_t<R,F,class boost::_bi::list0> __cdecl boost::bind(F)' : expects 1 arguments - 2 provided c:\vendor_libs\VC60\include\boost/bind.hpp(1226) : see declaration of 'bind' Error executing cl.exe. DailyReportTree.obj - 49 error(s), 0 warning(s) Kind regards Pshemek Przemyslaw Sliwa Global Foreign Exchange FX Risk Engine Development Merrill Lynch ( +44 (0)20 7995 4182 ) +44 (0)79 6325 2319 * Email: przemyslaw_sliwa(a)ml.com -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Christian Henning Sent: 30 January 2006 19:27 To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] Spawning a thread on a member function Of course, you could start off threads everywhere. The problem might be synchronization and knowing if a thread is terminated or not. The function join() gives you one way to wait for a thread to terminate. I usually do that in a destructor. If you have a problem you work on, I would suggest, that you name it. So, I can help you more specifically. Christian _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users -------------------------------------------------------- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ --------------------------------------------------------

1 0

boost bind logical operators question
by gast128 31 Jan '06

31 Jan '06

Dear all, this new boost bind logical operators is a great enhancement for readability of bind constructions. However I have not found out yet how to deal with e.g. built in types: std::vector<int> vec; std::list<int> lst; //copy_if does not exist in std, I know. std::copy_if(vec.begin(), vec.end(), std::back_inserter(lst), ...); this ... must now boost::bind(std::equal_to<int>(), _1, nNumber), which is quite unreadable, but no such thing like boost::bind::_1 == nNumber (like boost::lambda)? Wkr, me

2 2

lexical_cast memory consuption with VC8
by Josue Gomes 31 Jan '06

31 Jan '06

Hi, I'm experiencing a memory leak while using lexical_cast with VC8. The leak was detected by an end-user in a long-running application and evidenced with GlowCode (a leak detection tool). The origin seems to be an allocation inside ios_base (<xiosbase>). Source code for the test: #include <string> #include <boost/lexical_cast.hpp> int main() { std::string s = "1234"; unsigned u = boost::lexical_cast<unsigned>(s); } GlowCode trace: Handle 0x1555308 (0x1555308 = HeapAlloc( 0x310000, 0x0, 40)) caller(1): malloc_base(); + 236 bytes; module MSVCR80D.dll; 0x1024DB9C caller(2): malloc_dbg(); + 725 bytes; module MSVCR80D.dll; 0x1020FAA5 caller(3): malloc_dbg(); + 105 bytes; module MSVCR80D.dll; 0x1020F839 caller(4): malloc_dbg(); + 31 bytes; module MSVCR80D.dll; 0x1020F7EF caller(5): operator new(); + 30 bytes; module MSVCP80D.dll; 0x104F938E caller(6): std::ios_base::_Init(); + 112 bytes; module MSVCP80D.dll; 0x104877B0 caller(7): std::basic_ios<char,std::char_traits<char> >::init(); + 15 bytes; module MSVCP80D.dll; 0x10497CFF caller(8): std::basic_istream<char,std::char_traits<char> >::basic_istream<char,std::char_traits<char> >(); + 143 bytes; module MSVCP80D.dll; 0x10497F1F caller(9): std::basic_iostream<char,std::char_traits<char> >::basic_iostream<char,std::char_traits<char> >(); + 115 bytes; module MSVCP80D.dll; 0x104C9693 caller(10): std::basic_stringstream<char,std::char_traits<char>,std::allocator<char> >::basic_stringstream<char,std::char_traits<char>,std::allocator<char> >(); + 116 bytes; module MSVCP80D.dll; 0x104CD2A4 caller(11): boost::detail::lexical_stream<unsigned int,std::basic_string<char,std::char_traits<char>,std::allocator<char> > >::lexical_stream<unsigned int,std::basic_string<char,std::char_traits<char>,std::allocator<char> > >(); file e:\projects\libraries\boost_1_33_1\boost\lexical_cast.hpp; line 134 + 81 bytes; module mleak.exe; 0x411A41 caller(12): boost::lexical_cast<unsigned int,std::basic_string<char,std::char_traits<char>,std::allocator<char> > >(); file e:\projects\libraries\boost_1_33_1\boost\lexical_cast.hpp; line 219 + 11 bytes; module mleak.exe; 0x4116BF caller(13): main(); file e:\projects\mleak\mleak.cpp; line 7 + 9 bytes; module mleak.exe; 0x41159E caller(14): __tmainCRTStartup(); file f:\rtm\vctools\crt_bld\self_x86\crt\src\crtexe.c; line 586 + 25 bytes; module mleak.exe; 0x412EA6 caller(15): mainCRTStartup(); file f:\rtm\vctools\crt_bld\self_x86\crt\src\crtexe.c; line 403, module mleak.exe; 0x412CED Regards, Josue Gomes

2 2

Re: [Boost-users] Spawning a thread on a member function
by Sliwa, Przemyslaw (London) 31 Jan '06

31 Jan '06

And what will happen if the member function takes some additional parameters? e.g. one has void run(const std::string& cs) { // thread job goes here } Should I use nested boost::bind calls? Thanks a lot for help. Pshemek Kind regards Pshemek Przemyslaw Sliwa Global Foreign Exchange FX Risk Engine Development Merrill Lynch ( +44 (0)20 7995 4182 ) +44 (0)79 6325 2319 * Email: przemyslaw_sliwa(a)ml.com -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Patrick Sent: 27 January 2006 15:53 To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] Spawning a thread on a member function Hello Sliwa, This should do it. class Simple { Simple() : th(boost::bind(&Simple::run, boost::ref(*this))) {} void run() { for(;;){ //Thread's work goes here. } } private: boost::thread th; }; _____ From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Sliwa, Przemyslaw (London) Sent: Friday, January 27, 2006 4:25 AM To: boost-users(a)lists.boost.org Subject: [Boost-users] Spawning a thread on a member function All, Does anyone know how to spawn a thread on member function of an existing object in its constructor. Clearly simple boost::bind does not work. I do not know how to tell the compiler it must take the member function. Thanks for help, Pshemek Kind regards Pshemek Przemyslaw Sliwa Global Foreign Exchange FX Risk Engine Development Merrill Lynch *** +44 (0)20 7995 4182 * +44 (0)79 6325 2319 *** Email: przemyslaw_sliwa(a)ml.com _____ If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here <http://www.ml.com/email_terms/> for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ _____

1 0

[program_options] Bug in example and documentation
by Peter Gerell 31 Jan '06

31 Jan '06

Hi, I believe the example found in example/response_file.cpp and referenced in the documentation has a bug. In the following code fragment a temporary string object is passed as the first argument to the tokenizer constructor. This string is destroyed before the iteration over the tokens start. /Peter if (vm.count("response-file")) { // Load the file and tokenize it ifstream ifs(vm["response-file"].as<string>().c_str()); if (!ifs) { cout << "Could not open the response file\n"; return 1; } // Read the whole file into a string stringstream ss; ss << ifs.rdbuf(); // Split the file content char_separator<char> sep(" \n\r"); tokenizer<char_separator<char> > tok(ss.str(), sep); vector<string> args; copy(tok.begin(), tok.end(), back_inserter(args)); // Parse the file and store the options store(command_line_parser(args).options(desc).run(), vm); }

1 0

Request help with boost::compose to boost::bind conversion
by gdprosch＠micron.com 30 Jan '06

30 Jan '06

Let me apologize in advance for my ignorance but I have not been able to update the following code successfully in order to migrate from Boost 1_29 to 1_33. Despite reading the boost::bind documentation a few times I am failing to make the necessary connection regarding the use of _1, _2 and handling the use of DeRef in the equal function below. // Unary dereference functor (a functor that returns the value of the specified // parameter, dereferenced via operator*) // (Note: This DeRef code is included in a separate header.) template < class Ptr, class T > struct DeRef : public std::unary_function< Ptr, T > { T & operator()( Ptr & ptr ) const { return *ptr;} }; // --- // Compare LocalStringMap (a custom map container with Tag/Value pair). // A TagValue is a class that contains a tag and a value (both strings) // A TagValuePtr is a custom, dereferencable smart pointer. inline bool LocalStringMap::operator==( const LocalStringMap &that ) const { // Must be same size if( this->size() != that.size() ) { return false;} return equal( this->_list.begin(), this->_list.end(), that._list.begin(), boost::compose_f_gx_hy( equal_to< TagValue >(), DeRef< const TagValuePtr, const TagValue >(), DeRef< const TagValuePtr, const TagValue >() ) ); } Any assistance with this would be most helpful. I get the impression that I do not need to use the DeRef class the original author created given boost:bind's more capable traits identification. Here's what I have so far... return std::equal( this->_list.begin(), this->_list.end(), that._list.begin(), boost::bind<bool>( std::equal_to< TagValue >(), ??? Thank you, Greg Prosch Micron Technology, Inc.

1 0

Re: [Boost-users] Boost shared pointers and MSVC++ 6.0
by Sohail Somani 30 Jan '06

30 Jan '06

> The object is always deleted by the same library that created the > shared_ptr. This is done by instantiating an appropriate deleter at > construction time. You can defeat this by creating the object > in library A > and the shared_ptr in library B, of course. > > Mixing single- and multithreaded libraries might be a problem > for other > reasons, but even that should work on Windows with Boost 1.33 > with the > default configuration. Thanks Peter, please disregard my reply to your other email.

1 0

Re: [Boost-users] Boost shared pointers and MSVC++ 6.0
by Sohail Somani 30 Jan '06

30 Jan '06

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Sohail Somani > Sent: Monday, January 30, 2006 1:06 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] Boost shared pointers and MSVC++ 6.0 > > > -----Original Message----- > > No, this isn't normal. shared_ptr should work even if you > > don't do (1) or > > (2), with one exception: the plugin that created a shared_ptr > > needs to be > > present in memory when the last copy of this shared_ptr is > destroyed > > (because the creator plugin contains the destructor code.) So > > if you don't > > unload plugins dynamically, it _should_ work. If it doesn't, > > try to isolate > > a simple example for us to investigate. > > How will it work if the main program is linked against the > multi-threaded dll and some other library the single-threaded, but the > object that was created in the MT-linked dll is deleted by the one in > the ST-dll? > > Wouldn't different deletes be called? After mulling a bit, I think this is the whole point of shared_ptr. But I am not sure how it works. Is this encapsulated in the check_delete?

1 0

Boost shared pointers and MSVC++ 6.0
by Henri Herscher 30 Jan '06

30 Jan '06

Hi, I'm making heavy use of the boost shared pointers in the open source audio recording (voip and sound devices) project I'm developing (http://www.oreka.org) The software is cross platform (Windowns/Linux) and shared pointers are created in plugins and typically destroyed in other plugins or in the main program. Under linux, I haven't had any kind of problem. On windows however, using MSVC++ 6SP6 I have observed strange crashes that happen only in the release mode. So far I think I have been able to solve that doing two things (both needed or crash !): 1. Make sure all DLLs and the main program are compiled with the same runtime (multithreaded DLL) 2. Make sure all DLLs and the main program are compiled with inline function exapansion disabled My questions: * Is this normal ? What have other people experienced ? * Will this go away if I upgrade to MSVC++ 7 ? Thanks Henri

2 2

Re: [Boost-users] Boost shared pointers and MSVC++ 6.0
by Sohail Somani 30 Jan '06

30 Jan '06

> -----Original Message----- > No, this isn't normal. shared_ptr should work even if you > don't do (1) or > (2), with one exception: the plugin that created a shared_ptr > needs to be > present in memory when the last copy of this shared_ptr is destroyed > (because the creator plugin contains the destructor code.) So > if you don't > unload plugins dynamically, it _should_ work. If it doesn't, > try to isolate > a simple example for us to investigate. How will it work if the main program is linked against the multi-threaded dll and some other library the single-threaded, but the object that was created in the MT-linked dll is deleted by the one in the ST-dll? Wouldn't different deletes be called?

2 1

[thread] Static mutex members
by David A. Greene 30 Jan '06

30 Jan '06

The following single-file testcase fails to link: #include <boost/thread/thread.hpp> #include <boost/thread/recursive_mutex.hpp> #include <iostream> template<typename Type> class singleton { public: typedef boost::recursive_mutex mutex_type; typedef Type * handle; private: typedef mutex_type::scoped_lock lock_type; static mutex_type mutex; static handle inst; public: static Type &instance(void) { lock_type lock(mutex); if (!inst) { inst = new Type; } return(*inst); }; }; class tester { public: void test(void) { std::cerr << "Test" << std::endl; }; }; template<> singleton<tester>::mutex_type singleton<tester>::mutex; template<> singleton<tester>::handle singleton<tester>::inst = 0; int main(void) { singleton<tester>::instance().test(); return(0); } thread.o: In function `singleton<tester>::instance()':/home/greened/projects/apsim/current/apsim/msim/test/thread.cc:21: undefined reference to `singleton<tester>::mutex' collect2: ld returned 1 exit status I was getting undefined references to "inst" before I added the initializer. Is this a new adherance to the standard by g++ 4.0.2? I didn't used to have to add the initializer to get it to link. This is troublesome with boost::recursive_mutex because it is noncopyable. How do I specify an initializer for it? Is it just not possible to have a mutex static member? -Dave

2 1

Re: [Boost-users] Spawning a thread on a member function
by Sliwa, Przemyslaw (London) 30 Jan '06

30 Jan '06

Can I spawn the thread within another member function? I believe it should be not a problem. Thanks Kind regards Pshemek Przemyslaw Sliwa Global Foreign Exchange FX Risk Engine Development Merrill Lynch ( +44 (0)20 7995 4182 ) +44 (0)79 6325 2319 * Email: przemyslaw_sliwa(a)ml.com -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Patrick Sent: 27 January 2006 23:03 To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] Spawning a thread on a member function You are correct the "boost::ref(*this)" is not needed. Simple(boost::bind(&Simple::run, this)) {} -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Christian Henning Sent: Friday, January 27, 2006 4:47 PM To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] Spawning a thread on a member function This is even simpler. Is there is reason for "boost::ref(*this)" ? class Simple { Simple() : th( boost::bind( run, this )) {} void run() { for(;;){ //Thread's work goes here. } } private: boost::thread th; }; _______________________________________________ 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 -------------------------------------------------------- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ --------------------------------------------------------

2 1

problem with include files
by Frank Pleyer 30 Jan '06

30 Jan '06

Hi, Im new to boost and after building the libraries to c:\boost, I wanted to go through the [String Algorithm First Example]. Im using visual c++ 2005 with windows xp SP2 and when I tried to build my project I get the following error: fatal error C1083: Datei (Include) kann nicht geöffnet werden: "boost/algorithm/string.hpp" corrosponding to that line of code: #include <boost/algorithm/string.hpp> All # include calls have a unix like path description and not a common windows path like : c:\boost\include\algorith\string.hpp. That seems to be a general problem with all #include calls in all boost *.hpp files. I have included the the path[c:\boost] and [c:\boost\include] to my VC++ INCLUDE Path. Can somebody please help. -Frank

2 1

Re: [Boost-users] Boost shared pointers and MSVC++ 6.0
by Sohail Somani 30 Jan '06

30 Jan '06

> My questions: > > * Is this normal ? What have other people experienced ? Normal. If you are sharing heaps, data structures across DLLs, you should be sure that you link with the same runtimes. > * Will this go away if I upgrade to MSVC++ 7 ? Maybe not if you're using C++.NET?

1 0

[random] comments on speed?
by Sanyi 30 Jan '06

30 Jan '06

Sorry if double posted... Can anyone who have tried Boost's `random' library have any thoughts on its speed? I looked into its binomial variate function and apparently it actualy flips a (biased) coin countless times to generate it. I am not an expert in this, but this seems awfully slow for high n's. (Not to mention that I could have done it myself.) AFAIK there are fast and good algorithms/approximations for generating some non-uniform variates. Are any of these at least planned to be included? <OT> I've found some papers on fast binomial generators, but that takes some serious time and effort to translate into working code. As I don't want to reinvent the wheel, if you know of any publicly available libraries for it, let me know. </OT> Thanks, Sanyi

3 3

boost::iostream - no way to set failbit or badbit in stream from device?
by Oliver.Kowalke＠infineon.com 30 Jan '06

30 Jan '06

Hallo, how can I set failbit or badbit in boost::iostream::stream if I detect some error in boost::iostream::device::read/write? Is it possible without throwing exceptions? Example: in the write method of a device which models a socket connection an EPIPE error (peer has closed socket) was detected. How can I set the boost::iostream::stream (which uses the device) to be not useable? Regards, Oliver

1 0

Re: [Boost-users] boost::iostream - returning EOF in device::writeand set failbit
by Oliver.Kowalke＠infineon.com 30 Jan '06

30 Jan '06

Hello Petro, >> would the eofbit be set if I return EOF in device::write? >> How can I set failbit from device? >Does it make sense for write to return EOF? >EOF means "no more data". >But writing is inserting data, not requesting it. If you write to a socket and the peer has already closed the socket you get an EPIPE error. How would you propagate this to your application? Oliver

1 0

[boost][serialization] How to implement serialization classes in two DLLs
by jf332-3 29 Jan '06

29 Jan '06

Hi, After few hour on the subject, Im would like to have some explanations & recommendations one the boost serialization library. To explain, my problem, you will find hereafter a VC++ 7.1 project that demonstrates it. Problem Description We have involved in a large project with for example two DLLs libraries: LibA and LibB. These libraries define & implement one class each other, lets say libA::A and libB::B. These two classes can be serialized through boost serialization engine. The interfaces for the two classes are the same: ---------------------- struct LIBA_API A { std::vector<double> my_vector ; private: friend class boost::serialization::access; template<class Archive> void save(Archive & ar, const unsigned int version) const ; template<class Archive> void load(Archive & ar, const unsigned int version) ; BOOST_SERIALIZATION_SPLIT_MEMBER() }; LIBA_API void save(const libA::A* pObj, std::ostream& os) ; LIBA_API void load(libA::A* &pObj, std::istream& is) ; }; // Namespace libA ---------------------- The two free functions save() and load() are defined to be able to serialize the class libA::A (respectively the class libB::B). When, we try to use these interfaces in an EXE application: ---------------------- #include <LibA/A.h> #include <LibB/B.h> #include <boost/filesystem/path.hpp> #include <boost/filesystem/fstream.hpp> #pragma comment(lib, "liba_d.lib") #pragma comment(lib, "libb_d.lib") int main(int argc, char* argv[]) { libA::A a; libA::save(&a, boost::filesystem::ofstream("a.xml")); libB::B b; libB::save(&b, boost::filesystem::ofstream("b.xml")); // -> Assert in debug mode return 0; } ---------------------- The figure hereafter describes the relationships between LibA, LibB and EXE. ------------ ------------ | LibA | | LibB | ------------ ------------ \ / \ / Exe Application We have to face to an assert in debug mode generate by the file boost::serialization::extended_type_info.cpp, line#71. This assert happens during the instance serialization of class libB:B. Recently, there are some posts on this subject, but I would like to known how I can deal with this assert? Is it possible to avoid it by a code organisation? To have a concrete answer, I have joined my complete VC++7.1 project. Thanks in advance for your help. Development Platform WindowsXP VC++ 7.1 Boost 1.33.1 Marc Viala mailto:mviala@acticm.com

1 0

Re: [Boost-users] boost::serialisation - portable_binary_oarchivenotpart of library
by Oliver.Kowalke＠infineon.com 28 Jan '06

28 Jan '06

Hello Robert, I think a 'finished' protable_binary_oarchive/ protable_binary_iarchive would be very useful for network applications (passing message structures -> header, body, trailer). I'm not familiar with boost::serialization (my first look into it) - I see some specializations of load for integral types an a templated member function for all others. Serialisation for std::strings and chars are supported in a portable manner? Only floating point types have to be implemented for portability? Oliver >I made it as an example on how to extend the library by deriving from an >existing >archive. To "finish" it would require implementing serialization of >floating point >types in a portable manner and this turns out to be a non-trivial task. >Implementing >this would be too much work and would sort of compromise illustrative value >of the example.

3 3

Re: [Boost-users] boost::serialisation -Non-default Constructors
by Merrill Cornish 28 Jan '06

28 Jan '06

Yes. Each class you want to serialize needs a default constructor in addition to whatever other constructors your application needs. Merrill

2 1

::spirit, token_node_d
by elviin 28 Jan '06

28 Jan '06

Before I'll investigate more I'd like to know if anybody knows why it is not allowed a rule object inside this directive: token_node_d.

2 2

[statechart] Ready for addition to main CVS
by Andreas Huber 28 Jan '06

28 Jan '06

Dear Boosters I believe I have addressed all the important issues that were reported during formal review of the Boost.Statechart library (then proposed as boost::fsm). Although there's still a lot to do, I think that the current version is stable enough to be added to the main CVS. All reviewers (and anyone else interested) are invited to verify that the issues that have been put forth have been taken care of appropriately: http://boost-sandbox.sf.net/libs/statechart Given Thomas Witt's cutoff date for additions of new libraries (February 8th) and the roughly one week needed to move the statechart directories from the sandbox CVS to the main CVS (can only be done by source forge staff), I must ask people to come forward with their questions/concerns before February 1st. Should anyone need more time, please let me know immediately by following up to this post. Thanks & Regards, -- Andreas Huber When replying by private email, please remove the words spam and trap from the address shown in the header.

1 0

[graph] non-contiguous edges?
by Roman Schindlauer 28 Jan '06

28 Jan '06

Hello, Warning ahead - this is a newbie question. I need to find weak and strong components of a graph. So far, my code is as simple as it could be (edges being a std::vector of std::pair<unsigned,unsigned>): typedef adjacency_list <vecS, vecS, undirectedS> Graph; Graph G; for (Edges::const_iterator ei = edges.begin(); ei != edges.end();++ei) add_edge((*ei).first, (*ei).second, G); std::vector<int> component(num_vertices(G)); int num = connected_components(G, &component[0]); However, my vertices are not contiguously numbered. Hence, the following edges (8, 9) (9, 10) (12, 13) result in these connected components: 0: 0 1: 1 2: 2 3: 3 4: 4 5: 5 6: 6 7: 7 8: 8, 9, 10 9: 11 10: 12, 13 which is not what I want (just two wcc: 8, 9, 10 and 12, 13). I was reading into the property_map stuff, but as far as i understand, that would not help here. Do I have to remap the indices beforehand or is there a way to convince Boost that there are no other nodes than those in the edges? Best regards, Roman

1 0

Warnings and boost
by gast128 27 Jan '06

27 Jan '06

Dear all, Our company makes heavy use of boost libraries. But unfornately some libraries trigger warnings. This is hard to circumvent since we both have level 4 and warnings as error option enabled in Visual Studio 2003. An example is the counting iterator: const std::vector<int> values1(boost::make_counting_iterator(1), boost::make_counting_iterator(10)); gives C4244. This is even harder to supress since the STL is included in the precompiled header. Is it an option to have a good look at this issue for the next release? Note that it is also possible that Plauger's STL is not conforming. Wkr, me

5 5

Spawning a thread on a member function
by Sliwa, Przemyslaw (London) 27 Jan '06

27 Jan '06

All, Does anyone know how to spawn a thread on member function of an existing object in its constructor. Clearly simple boost::bind does not work. I do not know how to tell the compiler it must take the member function. Thanks for help, Pshemek Kind regards Pshemek Przemyslaw Sliwa Global Foreign Exchange FX Risk Engine Development Merrill Lynch ( +44 (0)20 7995 4182 ) +44 (0)79 6325 2319 * Email: przemyslaw_sliwa(a)ml.com -------------------------------------------------------- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ --------------------------------------------------------

4 5

Declaration Terminated Incorrectly
by Deepak Singh 27 Jan '06

27 Jan '06

Hello; I am using Borland C++ 6 Evaluaion Version for making dll. Can You help me out from this error. /*Voice.h*/ //#include "CFeatureMatrix.h" //#include "CVoiceInterface.h" //#include "CVoicePrint.h" BOOL WINAPI DllMain(HINSTANCE hinstDLL, DWORD fwdreason, LPVOID lpvReserved) { return 1; } When I compile to make dll I get "stddef.h:Declaration terminated incorrectly" error and second line shows "stddef.h:Qualifier 'std' is not a class or namespace name". If I remove Comment for including the header file I get "Voice.h:Declaration terminated incorrectly" /*Voice.h*/ #include "CFeatureMatrix.h" #include "CVoiceInterface.h" #include "CVoicePrint.h" BOOL WINAPI DllMain(HINSTANCE hinstDLL, DWORD fwdreason, LPVOID lpvReserved) { return 1; } Regards Deepak ********************************************************* Disclaimer: The contents of this E-mail (including the contents of the enclosure(s) or attachment(s) if any) are privileged and confidential material of MBT and should not be disclosed to, used by or copied in any manner by anyone other than the intended addressee(s). In case you are not the desired addressee, you should delete this message and/or re-direct it to the sender. The views expressed in this E-mail message (including the enclosure(s) or attachment(s) if any) are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of MBT. This e-mail message including attachment/(s), if any, is believed to be free of any virus. However, it is the responsibility of the recipient to ensure that it is virus free and MBT is not responsible for any loss or damage arising in any way from its use ********************************************************

2 1

[lambda] Nesting and temporaries
by EMalenfant＠interstarinc.com 27 Jan '06

27 Jan '06

Hello, Given the following: std::string Cat(const std::string& First, const std::string& Second) { return First + Second; } void Print(const char* S) { std::cout << S << std::endl; } std::string foo("foo"); std::string bar("bar"); The novice Lambda user that I am would have thought that this: using namespace boost::lambda; bind(Print, bind(&std::string::c_str, bind(Cat, _1, _2) ) )(foo, bar); would be roughly equivalent to: Print(Cat(foo, bar).c_str()); But it seems to behave more like: const char* ptr_to_temp = Cat(foo, bar).c_str(); Print(ptr_to_temp); and invokes undefined behavior. This workaround seems to work: var_type<std::string>::type temp(var(std::string())); ( temp = bind(Cat, _1, _2), bind(Print, bind(&std::string::c_str, temp)) ) (foo, bar); this one too: var_type<std::string>::type temp(var(std::string())); bind(Print, bind(&std::string::c_str, (temp = bind(Cat, _1, _2)) ) ) (foo, bar); Could someone comment on this? Are these workarounds correct? Is one better than the other? Is there another solution? Thanks, ----------------------------- Éric Malenfant A conclusion is the place where you got tired of thinking

1 0

boost::iostream - returning EOF in device::write and set failbit
by Oliver.Kowalke＠infineon.com 27 Jan '06

27 Jan '06

Hello, would the eofbit be set if I return EOF in device::write? How can I set failbit from device? Regards, Oliver

2 1

Re: [Boost-users] Version Mgmt classes/algorithms
by Rich Johnson 27 Jan '06

27 Jan '06

On Jan 26, 2006, at 11:58 AM, Noel Yap wrote: > Hmm, I've been thinking about this problem but from a different > perspective. > > First, some definitions: > - patch release: the new component is link and load compatible with > the old one; clients might need to relink or reload > - minor release: the new component is compile compatible with the old > one; clients might need to recompile > - major release: the new component isn't compatible with the old one; > clients might need to modify code > > Given the above, a mapping can be made of changes to source to one of > the above. I suppose if a component developer follows the above, one > could write a class that could easily figure out whether or not a > certain M.m.p update is backwards compatible with another. > > Also, what really counts are changes to header files. More > specifically, changes to published header files (ie header files that > are installed so as to be usable by other components). I LIKE the crispness of your functional definitions. They suggest that there may exist an algorithm determining the ''order'' of a change: - Any change in the interface base class is _at least_ a minor release. - Any change in an implementation derived class is _at most_ a patch release. - Any change in the semantics of the base class interface is _at least_ a major release. - Version stamp can probably be generated by configuration control (i.e. CVS); - Version stamp can probably be used as a _signature_ of the module's interface. FWIW, a "compiler compatibility" is probably required when dealing with separately compiled modules. Applying the definitions to dynamically loaded libraries where we're _always_ relinking; we come up with: - if patch release; accept - if minor release; reject (you _might_ scoot by with some changes; but why risk it?) - if major release; reject - if compiler incompatible; reject (of course). Dynamically loaded modules could supply a ''well known'' C function to access their version stamp (or otherwise determine compatibility) prior to instantiating any dynamically allocated objects. Now you've got me thinking.... --rich

3 3

Re: [Boost-users] Version Mgmt classes/algorithms
by Rich Johnson 27 Jan '06

27 Jan '06

> > For what it's worth, we use namespaces to do version management and > this works quite well for us. This technique may not work for you > but a brief description of it is in Stroustrup's D&E in section > 17.4.4 (Using Namespaces to Manage Releases). We've done a lot of > work in this area, just not sure if it's what you're interested in. Hmm...I'll have to take a look. Do you do use it with dynamically loaded modules--dlopen(), dlsym(), etc.?

2 1

boost::serialisation - portable_binary_oarchive not part of library
by Oliver.Kowalke＠infineon.com 27 Jan '06

27 Jan '06

Hallo, why is portable_binary_oarchive and portable_binary_iarchive only contained in the examples not part of the library interface? Regards, Oliver

2 1

Boost threads- how do I simultaneously check the lock on two or more mutexes?
by Terence Wilson 26 Jan '06

26 Jan '06

boost::try_mutex M1, M2; boost::try_mutex::scoped_try_lock lockx(M1, false); boost::try_mutex::scoped_try_lock locky(M2, false); I would like to be able to atomically check that at least one lock can be made: assert(lockx.try_lock() || locky.try_lock()); In Win32 I would use WaitForMultipleObjects. Thanks in advance.

1 0

Comments on the usability of program_options
by Steve Byan 26 Jan '06

26 Jan '06

First let me mention that I greatly appreciate all the work done by the contributors to Boost. The library has been extremely helpful to me both as a class and template library and as a learning tool for template meta-programming. In the spirit of constructive criticism, I'd like to offer a few usability observations arising from my first attempt to use program_options. I appreciate the flexibility, extensive feature set, and the extensibility of the library. I particularly like the unification of command-line options with configuration files; this is a very handy feature. However, I think the unification of program arguments with program options is less successful. I think the library would be better if arguments were a separate concept. Unifying program arguments with program options has these consequences: 1) The error message produced by an excessive number of arguments is opaque to most users. The error message produced is "Error: unknown option foo", which I think would be better phrased as something along the lines of "Error: too many arguments". Since program_options doesn't distinguish options from arguments, it can't easily produce a better diagnostic message. 2) The usage description by default describes command-line arguments as options. E.g. the usage message is something like this: Supported options: -h [ --help ] produce this help message --device-file arg scsi pass-thru device special file To hide the "argument options" in the help message, program_options supports multiple options_descriptions, but puts the responsibility for hiding the "argument options" on the user of the library, and, unlike normal options, does not automatically provide a description of the argument in the help message. If arguments were instead treated as first-class concept instead of a mutant form of an option, the library could automatically handle these issues. 3) Somewhat related to issue #2, program_options doesn't generate a concise usage description help-message from the grammar. For example, it would be nice if options_desciption could provide a string like this: Usage: scsi_tool [-h | --help] [-v | --verbose] <device-file> [<output-file>] Additionally, it would be nice if program_options handled more of the validation and error reporting. Currently the user is responsible for checking for required arguments and generating an error if they are not supplied, and for coding the generation of a usage message when the options and arguments don't conform to the specified grammar. An example of an alternative design which addresses these concerns (but which lacks many of the more sophisticated features of program_options) is Ole Laursen's commandoptions <http:// www.cs.aau.dk/~olau/commandoptions/> Regards, -Steve -------- Steve Byan <smb(a)egenera.com> Software Architect Egenera, Inc. 165 Forest Street Marlboro, MA 01752 (508) 858-3125

3 2

Re: [Boost-users] program_options requires non-const argv
by Merrill Cornish 26 Jan '06

26 Jan '06

Steve, I ran into the same problem. Once I thought about it, I realized I had _never_ seen a C or C++ main() function prototype defined with a const second argument. I think I remember that one of the traditional C getopt() function variants actually munges the argument list by removing that arguments it recognizes, leaving anything else for direct processing by the program. I'm guessing program_options is therefore tacitly assuming the second argument is non-const also. Merrill

4 3

spirit::, token_node_d, xml-tree
by elviin 26 Jan '06

26 Jan '06

Hello there. I'd like to use non-ast tree. I'm also using the tree_to_xml function to generate xml code. Plus my own grammar. The problem is with the token_node_d directive. I assumed that this directive merge the parsed code to an one node. At this time my parser works for me very fine except the tree because there are missing value objects in xml structure. So it seems that the whole tree is empty:/ I can reproduce that state with the example file parse_tree_calc1.cpp: The correct output from the tree_to_xml function is following when parsing "1": <?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE parsetree SYSTEM "parsetree.dtd">  <parsetree version="1.0"> <parsenode rule="expression"> <parsenode rule="term"> <parsenode rule="factor"> <parsenode rule="integer"> <parsenode rule="integer"> <value>1</value> <<<<======== it's OK here </parsenode> </parsenode> </parsenode> </parsenode> </parsenode> </parsetree> parsing succeeded ... and the corresponfing code/rules: integer = lexeme_d[ token_node_d[ (!ch_p('-') >> +digit_p) ] ]; factor = integer | '(' >> expression >> ')' | ('-' >> factor); term = factor >> *( ('*' >> factor) | ('/' >> factor) ); expression = term >> *( ('+' >> term) | ('-' >> term) ); But if I move the token_node_d directive to another position, so that is similar to the problem with my grammar: integer = lexeme_d[ (!ch_p('-') >> +digit_p) ]; factor = token_node_d[integer] | '(' >> expression >> ')' | ('-' >> factor); term = factor >> *( ('*' >> factor) | ('/' >> factor) ); expression = term >> *( ('+' >> term) | ('-' >> term) ); ... then the XML structure looks like this. The "value" object are missing: <?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE parsetree SYSTEM "parsetree.dtd">  <parsetree version="1.0"> <parsenode rule="expression"> <parsenode rule="term"> <parsenode rule="factor"> <parsenode rule="integer"> <<<<======== it is not OK here </parsenode> </parsenode> </parsenode> </parsenode> </parsetree> parsing succeeded Can anyone explain me why it is not possible to use the directive token_node_d like this token_node_d[integer]? I just want to group all the parsed text (integer) in one node. May I have to change the policy or to create proper typedefs. The problem is with hierarchy, that I want to group the parsed text only in the higher levels of parsing process. Thank you. Elviin

2 2

Weird regex compiler warnings with VC 7.1
by Alan Davies 26 Jan '06

26 Jan '06

Hello. I've come across a weird compiler warning when using the regex library on VC 7.1 (I think the problem also occurs in VC 7.0). I'm using Boost 1.33.1 The code below throws up warnings. Removing the min() call from main, or changing a, b and c's type to anything else (e.g. short) gets rid of the warnings. The offending line is in regex_format.hpp (it appears twice in that file): std::ptrdiff_t len = (std::min)(static_cast<std::ptrdiff_t>(2), ::boost::re_detail::distance(m_position, m_end)); Putting a static cast around the distance() call makes no difference, but splitting it into two lines as follows gets rid of the warning: std::ptrdiff_t distance = ::boost::re_detail::distance(m_position, m_end); std::ptrdiff_t len = (std::min)(static_cast<std::ptrdiff_t>(2), distance); This makes absolutely no sense to me! My code and the warnings are below. #include "boost/regex.hpp" #include <iostream> #include <string> int main(int argc, char *argv[]) { std::string hello = "hello world!"; boost::regex multipleSpacesRegex("([[:space:]]){2,}"); int a=1, b=2; // Remove the next line to get rid of the warnings int c=(std::min)(a,b); hello = boost::regex_replace(hello, multipleSpacesRegex, "$1"); std::cout << hello << std::endl; return 0; } ------ Build started: Project: regex_test, Configuration: Debug Win32 ------ Compiling... main.cpp f:\dev\include\boost\regex\v4\regex_format.hpp(246) : warning C4244: 'argument' : conversion from 'std::iterator_traits<_Iter>::difference_type' to 'const int', possible loss of data with [ _Iter=const char * ] f:\dev\include\boost\regex\v4\sub_match.hpp(130) : while compiling class-template member function 'void boost::re_detail::basic_regex_formatter<OutputIterator,Results,traits>::format_perl(void)' with [ OutputIterator=boost::re_detail::string_out_iterator<std::basic_string<char,std::char_traits<char>,std::allocator<char>>>, Results=boost::match_results<std::basic_string<char,std::char_traits<char>,std::allocator<char>>::const_iterator>, traits=boost::regex_traits_wrapper<boost::regex_traits<char>> ] c:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\vector(152) : while compiling class-template member function 'void boost::re_detail::basic_regex_formatter<OutputIterator,Results,traits>::format_all(void)' with [ OutputIterator=boost::re_detail::string_out_iterator<std::basic_string<char,std::char_traits<char>,std::allocator<char>>>, Results=boost::match_results<std::basic_string<char,std::char_traits<char>,std::allocator<char>>::const_iterator>, traits=boost::regex_traits_wrapper<boost::regex_traits<char>> ] c:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\xstring(542) : while compiling class-template member function 'boost::re_detail::string_out_iterator<S> boost::re_detail::basic_regex_formatter<OutputIterator,Results,traits>::format(const boost::re_detail::basic_regex_formatter<OutputIterator,Results,traits>::char_type *,const boost::re_detail::basic_regex_formatter<OutputIterator,Results,traits>::char_type *,boost::regex_constants::match_flag_type)' with [ S=std::basic_string<char,std::char_traits<char>,std::allocator<char>>, OutputIterator=boost::re_detail::string_out_iterator<std::basic_string<char,std::char_traits<char>,std::allocator<char>>>, Results=boost::match_results<std::basic_string<char,std::char_traits<char>,std::allocator<char>>::const_iterator>, traits=boost::regex_traits_wrapper<boost::regex_traits<char>> ] f:\dev\include\boost\regex\v4\regex_format.hpp(568) : see reference to class template instantiation 'boost::re_detail::basic_regex_formatter<OutputIterator,Results,traits>' being compiled with [ OutputIterator=boost::re_detail::string_out_iterator<std::basic_string<char,std::char_traits<char>,std::allocator<char>>>, Results=boost::match_results<std::basic_string<char,std::char_traits<char>,std::allocator<char>>::const_iterator>, traits=boost::regex_traits_wrapper<boost::regex_traits<char>> ] f:\dev\include\boost\regex\v4\match_results.hpp(170) : see reference to function template instantiation 'OutputIterator boost::re_detail::regex_format_imp<OutputIterator,std::basic_string<_Elem,_Traits,_Ax>::const_iterator,std::vector<_Ty>::allocator_type,_Elem,boost::regex_traits_wrapper<BaseT>>(OutputIterator,const boost::match_results<BidiIterator> &,const charT *,const charT *,boost::regex_constants::match_flag_type,const traits &)' being compiled with [ OutputIterator=boost::re_detail::string_out_iterator<std::basic_string<char,std::char_traits<char>,std::allocator<char>>>, _Elem=char, _Traits=std::char_traits<char>, _Ax=std::allocator<char>, _Ty=boost::sub_match<std::basic_string<char,std::char_traits<char>,std::allocator<char>>::const_iterator>, BaseT=boost::regex_traits<char>, BidiIterator=std::basic_string<char,std::char_traits<char>,std::allocator<char>>::const_iterator, charT=char, traits=boost::regex_traits_wrapper<boost::regex_traits<char>> ] f:\dev\include\boost\regex\v4\regex_replace.hpp(53) : see reference to function template instantiation 'OutputIterator boost::match_results<BidiIterator>::format<OutputIterator,boost::basic_regex<charT,traits>>(OutputIterator,const boost::match_results<BidiIterator>::st std::ptrdiff_t distance = ::boost::re_detail::distance(m_position, m_end); std::ptrdiff_t len = (std::min)(static_cast<std::ptrdiff_t>(2), distance); ring_type &,boost::regex_constants::match_flag_type,const RegexT &) const' being compiled with [ OutputIterator=boost::re_detail::string_out_iterator<std::basic_string<char,std::char_traits<char>,std::allocator<char>>>, BidiIterator=std::basic_string<char,std::char_traits<char>,std::allocator<char>>::const_iterator, charT=char, traits=boost::regex_traits<char>, RegexT=boost::basic_regex<char,boost::regex_traits<char>> ] f:\dev\include\boost\regex\v4\regex_replace.hpp(84) : see reference to function template instantiation 'OutputIterator boost::regex_replace<boost::re_detail::string_out_iterator<S>,std::basic_string<_Elem,_Traits,_Ax>::const_iterator,boost::regex_traits<charT>,char>(OutputIterator,BidirectionalIterator,BidirectionalIterator,const boost::basic_regex<charT,traits> &,const charT *,boost::regex_constants::match_flag_type)' being compiled with [ OutputIterator=boost::re_detail::string_out_iterator<std::basic_string<char,std::char_traits<char>,std::allocator<char>>>, S=std::basic_string<char,std::char_traits<char>,std::allocator<char>>, _Elem=char, _Traits=std::char_traits<char>, _Ax=std::allocator<char>, charT=char, BidirectionalIterator=std::basic_string<char,std::char_traits<char>,std::allocator<char>>::const_iterator, traits=boost::regex_traits<char> ] f:\dev\projects\regex_test\main.cpp(17) : see reference to function template instantiation 'std::basic_string<_Elem,_Traits,_Ax> boost::regex_replace<boost::regex_traits<charT>,char>(const std::basic_string<_Elem,_Traits,_Ax> &,const boost::basic_regex<charT,traits> &,const charT *,boost::regex_constants::match_flag_type)' being compiled with [ _Elem=char, _Traits=std::char_traits<char>, _Ax=std::allocator<char>, charT=char, traits=boost::regex_traits<char> ] f:\dev\include\boost\regex\v4\regex_format.hpp(330) : warning C4244: 'argument' : conversion from 'std::iterator_traits<_Iter>::difference_type' to 'const int', possible loss of data with [ _Iter=const char * ] f:\dev\include\boost\regex\v4\sub_match.hpp(130) : while compiling class-template member function 'void boost::re_detail::basic_regex_formatter<OutputIterator,Results,traits>::format_escape(void)' with [ OutputIterator=boost::re_detail::string_out_iterator<std::basic_string<char,std::char_traits<char>,std::allocator<char>>>, Results=boost::match_results<std::basic_string<char,std::char_traits<char>,std::allocator<char>>::const_iterator>, traits=boost::regex_traits_wrapper<boost::regex_traits<char>> ] f:\dev\include\boost\regex\v4\regex_format.hpp(401) : warning C4244: 'argument' : conversion from 'std::iterator_traits<_Iter>::difference_type' to 'const int', possible loss of data with [ _Iter=const char * ] f:\dev\include\boost\regex\v4\regex_format.hpp(422) : warning C4244: 'argument' : conversion from 'std::iterator_traits<_Iter>::difference_type' to 'const int', possible loss of data with [ _Iter=const char * ] f:\dev\include\boost\regex\v4\sub_match.hpp(130) : while compiling class-template member function 'void boost::re_detail::basic_regex_formatter<OutputIterator,Results,traits>::format_conditional(void)' with [ OutputIterator=boost::re_detail::string_out_iterator<std::basic_string<char,std::char_traits<char>,std::allocator<char>>>, Results=boost::match_results<std::basic_string<char,std::char_traits<char>,std::allocator<char>>::const_iterator>, traits=boost::regex_traits_wrapper<boost::regex_traits<char>> ] Linking... Build log was saved at "file://f:\dev\projects\regex_test\Debug\BuildLog.htm" regex_test - 0 error(s), 4 warning(s) ---------------------- Done ---------------------- Build: 1 succeeded, 0 failed, 0 skipped ___________________________________________________________ Yahoo! Photos NEW, now offering a quality print service from just 8p a photo http://uk.photos.yahoo.com

2 1

Re: [Boost-users] Version Mgmt classes/algorithms
by Rich Johnson 26 Jan '06

26 Jan '06

> I'm looking for a peer-reviewed solutions for managing versions (dll > compatibiity, data formats, etc.). If they exist, they're pretty > hard to find. ( FWIW, searches with the terms "version" or > "versioning" aren't very helpful :-() > [...snip...] > Have there been any discussions on this topic in the boost domain? > If so, how would I find it? > Any one have ideas where else I could look? Or any useful codewords to search > for. Oooh, dead air! Er, would anyone be interested in discussing this issue or reviewing a proposed base class? Feel free to contact me off-list. Thnx, ---rich

1 0

Re: [Boost-users] program_options requires non-const argv
by Sohail Somani 25 Jan '06

25 Jan '06

> I ran into the same problem. Once I thought about it, I realized > I had _never_ seen a C or C++ main() function prototype defined > with a const second argument. I do it too :)

1 0

[ptr_container] Bug in reverse iterators?
by Bill Buklis 25 Jan '06

25 Jan '06

Is this a bug or am I expecting it to do something that it shouldn't? Does anyone know a workaround for this (at least temporarily)? Compiler: VC 7.1 boost: 1.33.0 Description: The "base" function for reverse iterators in the pointer container classes do not return the underlying iterator type as expected. It appears that "base" returns a reverse iterator instead. This is not specific with ptr_vector. All the pointer containers seem to have this problem. #include <boost/ptr_container/ptr_vector.hpp> void sample() { // the type of the vector does not matter for this typedef boost::ptr_vector<DWORD> boostvector; boostvector boostvec; boostvector::reverse_iterator rboostIt = boostvec.rbegin(); // The following line does NOT compile. boostvector::iterator boostIt = rboostIt.base(); // For comparison of code that DOES compile typedef std::vector<DWORD> stdvector; stdvector stdvec; stdvector::reverse_iterator rstdIt = stdvec.rbegin(); // The following line DOES compile. stdvector::iterator stdIt = rstdIt.base(); }

2 4

shared_ptr and typedef
by David A. Greene 25 Jan '06

25 Jan '06

Well, if nothing else, I'm learning lots about the corners of the language! I've got the following testcase: #include <boost/shared_ptr.hpp> #include <iostream> template<typename Base> class Handle { public: typedef boost::shared_ptr<Base> type; }; template<typename Type> void print_shared_ptr(boost::shared_ptr<Type> ptr) { std::cout << "Value is " << *ptr << std::endl; } template<typename Type> void print_handle(typename Handle<Type>::type ptr) { std::cout << "Value is " << *ptr << std::endl; } int main(void) { Handle<int>::type iptr(new int(10)); print_shared_ptr(iptr); print_handle<int>(iptr); print_handle(iptr); return(0); } The calls to print_shared_ptr and the first print_handle resolve just fine but the compiler (g++ 4.0.2) can't seem to resolve the final call to print_handle: shared_ptr.cc: In function 'int main()': shared_ptr.cc:29: error: no matching function for call to 'print_handle(boost::shared_ptr<int>&)' The point of class Handle is to hide the implementation detail that boost::shared_ptr is being used to manage resources. I would like the ability to easily change the type of smart pointer used throughout the application. What's going on here? Is there a way to make this work without having to explicitly specify the type to print_handle? Thanks. -Dave

2 3

Serialization of boost::shared_ptr<int>?
by Joseph Turian 25 Jan '06

25 Jan '06

Hi Robert and everyone, Thank you for explaining to me about BOOST_STRONGTYPE. I'll let you know how that goes for me. And thank you for being so patient and trying to help me get serialization working in my program. In the meantime, I'm experiencing a much simpler problem. Although I can serialize classes of the form boost::shared_ptr<T>, where T is a class I've defined, I get compilation errors if I try to serialize a boost::shared_ptr<int>. How can I resolve this? Code snippet: ----------------------------------------------- #include <iostream> #include <fstream> #include <boost/shared_ptr.hpp> #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/serialization/base_object.hpp> #include <boost/serialization/utility.hpp> #include <boost/serialization/shared_ptr.hpp> int main() { std::ofstream ofs("archive"); boost::archive::text_oarchive oa(ofs); boost::shared_ptr<int> i; oa << i; return 0; } ----------------------------------------------- g++ output: /usr/include/boost/serialization/shared_ptr.hpp: In function `void boost::serialization::serialize(Archive&, boost::shared_ptr&, unsigned int) [with Archive = boost::archive::text_oarchive, T = int]': /usr/include/boost/serialization/serialization.hpp:140: instantiated from `void boost::serialization::serialize_adl(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive, T = boost::shared_ptr<int>]' /usr/include/boost/archive/detail/oserializer.hpp:147: instantiated from `void boost::archive::detail::oserializer<Archive, T>::save_object_data(boost::archive::detail::basic_oarchive&, const void*) const [with Archive = boost::archive::text_oarchive, T = boost::shared_ptr<int>]' /usr/include/boost/mpl/if.hpp:67: instantiated from here /usr/include/boost/serialization/shared_ptr.hpp:227: error: incomplete type ` boost::STATIC_ASSERTION_FAILURE<false>' does not have member `value' /usr/include/boost/serialization/shared_ptr.hpp: In function `void boost::serialization::save(Archive&, const boost::shared_ptr&, unsigned int) [with Archive = boost::archive::text_oarchive, T = int]': /usr/include/boost/serialization/split_free.hpp:45: instantiated from `static void boost::serialization::free_saver<Archive, T>::invoke(Archive&, const T&, unsigned int) [with Archive = boost::archive::text_oarchive, T = boost::shared_ptr<int>]' /usr/include/boost/serialization/split_free.hpp:74: instantiated from `void boost::serialization::split_free(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive, T = boost::shared_ptr<int>]' /usr/include/boost/serialization/shared_ptr.hpp:231: instantiated from `void boost::serialization::serialize(Archive&, boost::shared_ptr&, unsigned int) [with Archive = boost::archive::text_oarchive, T = int]' /usr/include/boost/serialization/serialization.hpp:140: instantiated from `void boost::serialization::serialize_adl(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive, T = boost::shared_ptr<int>]' /usr/include/boost/archive/detail/oserializer.hpp:147: instantiated from `void boost::archive::detail::oserializer<Archive, T>::save_object_data(boost::archive::detail::basic_oarchive&, const void*) const [with Archive = boost::archive::text_oarchive, T = boost::shared_ptr<int>]' /usr/include/boost/mpl/if.hpp:67: instantiated from here /usr/include/boost/serialization/shared_ptr.hpp:183: error: incomplete type ` boost::STATIC_ASSERTION_FAILURE<false>' does not have member `value' /usr/include/boost/serialization/access.hpp: In static member function `static void boost::serialization::access::serialize(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive, T = int]': /usr/include/boost/serialization/serialization.hpp:81: instantiated from `void boost::serialization::serialize(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive, T = int]' /usr/include/boost/serialization/serialization.hpp:140: instantiated from `void boost::serialization::serialize_adl(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive, T = int]' /usr/include/boost/archive/detail/oserializer.hpp:232: instantiated from `boost::archive::detail::pointer_oserializer<T, Archive>::pointer_oserializer() [with T = int, Archive = boost::archive::text_oarchive]' /usr/include/boost/archive/detail/oserializer.hpp:197: instantiated from `const boost::archive::detail::pointer_oserializer<int, boost::archive::text_oarchive> boost::archive::detail::pointer_oserializer<int, boost::archive::text_oarchive>::instance' /usr/include/boost/archive/detail/oserializer.hpp:189: instantiated from `static const boost::archive::detail::pointer_oserializer<T, Archive>& boost::archive::detail::pointer_oserializer<T, Archive>::instantiate() [with T = int, Archive = boost::archive::text_oarchive]' /usr/include/boost/archive/detail/oserializer.hpp:514: instantiated from `const boost::archive::detail::basic_pointer_oserializer& boost::archive::detail::instantiate_pointer_oserializer(Archive*, T*) [with Archive = boost::archive::text_oarchive, T = int]' /usr/include/boost/archive/detail/interface_oarchive.hpp:65: instantiated from `const boost::archive::detail::basic_pointer_oserializer* boost::archive::detail::interface_oarchive<Archive>::register_type(const T*) [with T = int, Archive = boost::archive::text_oarchive]' /usr/include/boost/archive/detail/oserializer.hpp:343: instantiated from `static const boost::archive::detail::basic_pointer_oserializer* boost::archive::detail::save_pointer_type<Archive, TPtr>::non_abstract<T>::register_type(Archive&) [with T = const int, Archive = boost::archive::text_oarchive, TPtr = const int*]' /usr/include/boost/archive/detail/oserializer.hpp:359: instantiated from `static const boost::archive::detail::basic_pointer_oserializer* boost::archive::detail::save_pointer_type<Archive, TPtr>::register_type(Archive&, T&) [with T = const int, Archive = boost::archive::text_oarchive, TPtr = const int*]' /usr/include/boost/archive/detail/oserializer.hpp:459: instantiated from `static void boost::archive::detail::save_pointer_type<Archive, TPtr>::invoke(Archive&, TPtr) [with Archive = boost::archive::text_oarchive, TPtr = const int*]' /usr/include/boost/archive/detail/oserializer.hpp:535: instantiated from `void boost::archive::save(Archive&, const T&) [with Archive = boost::archive::text_oarchive, T = const int*]' /usr/include/boost/archive/basic_text_oarchive.hpp:78: instantiated from `void boost::archive::basic_text_oarchive<Archive>::save_override(T&, int) [with T = const int* const, Archive = boost::archive::text_oarchive]' /usr/include/boost/archive/detail/interface_oarchive.hpp:85: instantiated from `Archive& boost::archive::detail::interface_oarchive<Archive>::operator<<(T&) [with T = const int* const, Archive = boost::archive::text_oarchive]' /usr/include/boost/serialization/nvp.hpp:77: instantiated from `void boost::serialization::nvp<T>::save(Archivex&, unsigned int) const [with Archivex = boost::archive::text_oarchive, T = const int*]' /usr/include/boost/serialization/access.hpp:93: instantiated from `static void boost::serialization::access::member_save(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive, T = const boost::serialization::nvp<const int*>]' /usr/include/boost/serialization/split_member.hpp:43: instantiated from `static void boost::serialization::detail::member_saver<Archive, T>::invoke(Archive&, const T&, unsigned int) [with Archive = boost::archive::text_oarchive, T = boost::serialization::nvp<const int*>]' /usr/include/boost/serialization/split_member.hpp:69: instantiated from `void boost::serialization::split_member(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive, T = boost::serialization::nvp<const int*>]' /usr/include/boost/serialization/nvp.hpp:87: instantiated from `void boost::serialization::nvp<T>::serialize(Archive&, unsigned int) [with Archive = boost::archive::text_oarchive, T = const int*]' /usr/include/boost/serialization/access.hpp:109: instantiated from `static void boost::serialization::access::serialize(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive, T = boost::serialization::nvp<const int*>]' /usr/include/boost/serialization/serialization.hpp:81: instantiated from `void boost::serialization::serialize(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive, T = boost::serialization::nvp<const int*>]' /usr/include/boost/serialization/serialization.hpp:140: instantiated from `void boost::serialization::serialize_adl(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive, T = boost::serialization::nvp<const int*>]' /usr/include/boost/archive/detail/oserializer.hpp:252: instantiated from `static void boost::archive::detail::save_non_pointer_type<Archive, T>::save_only::invoke(Archive&, const T&) [with Archive = boost::archive::text_oarchive, T = boost::serialization::nvp<const int*>]' /usr/include/boost/archive/detail/oserializer.hpp:321: instantiated from `static void boost::archive::detail::save_non_pointer_type<Archive, T>::invoke(Archive&, const T&) [with Archive = boost::archive::text_oarchive, T = boost::serialization::nvp<const int*>]' /usr/include/boost/archive/detail/oserializer.hpp:535: instantiated from `void boost::archive::save(Archive&, const T&) [with Archive = boost::archive::text_oarchive, T = boost::serialization::nvp<const int*>]' /usr/include/boost/archive/basic_text_oarchive.hpp:78: instantiated from `void boost::archive::basic_text_oarchive<Archive>::save_override(T&, int) [with T = const boost::serialization::nvp<const int*>, Archive = boost::archive::text_oarchive]' /usr/include/boost/archive/detail/interface_oarchive.hpp:85: instantiated from `Archive& boost::archive::detail::interface_oarchive<Archive>::operator<<(T&) [with T = const boost::serialization::nvp<const int*>, Archive = boost::archive::text_oarchive]' /usr/include/boost/serialization/shared_ptr.hpp:185: instantiated from `void boost::serialization::save(Archive&, const boost::shared_ptr&, unsigned int) [with Archive = boost::archive::text_oarchive, T = int]' /usr/include/boost/serialization/split_free.hpp:45: instantiated from `static void boost::serialization::free_saver<Archive, T>::invoke(Archive&, const T&, unsigned int) [with Archive = boost::archive::text_oarchive, T = boost::shared_ptr<int>]' /usr/include/boost/serialization/split_free.hpp:74: instantiated from `void boost::serialization::split_free(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive, T = boost::shared_ptr<int>]' /usr/include/boost/serialization/shared_ptr.hpp:231: instantiated from `void boost::serialization::serialize(Archive&, boost::shared_ptr&, unsigned int) [with Archive = boost::archive::text_oarchive, T = int]' /usr/include/boost/serialization/serialization.hpp:140: instantiated from `void boost::serialization::serialize_adl(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive, T = boost::shared_ptr<int>]' /usr/include/boost/archive/detail/oserializer.hpp:147: instantiated from `void boost::archive::detail::oserializer<Archive, T>::save_object_data(boost::archive::detail::basic_oarchive&, const void*) const [with Archive = boost::archive::text_oarchive, T = boost::shared_ptr<int>]' /usr/include/boost/mpl/if.hpp:67: instantiated from here /usr/include/boost/serialization/access.hpp:109: error: request for member ` serialize' in `t', which is of non-aggregate type `int' ----------------------------------------------- Thanks again for being so helpful! Joseph -- http://www.cs.nyu.edu/~turian/

4 12

program_options requires non-const argv
by Steve Byan 25 Jan '06

25 Jan '06

I'm used to declaring main() as int main (int argc, const char * argv[]) Attempting to use boost::program_options with a const char * argv[] results in the compilation errors appended below on SLES 9 with gcc 3.3.3. Similar errors are reported on Mac OS 10.4.4 with gcc 4.0.1. First, I'd consider it an enhancement if program_options were to support a const char * argv[]. Second, is program_options actually modifying argv? Note the last error: "/usr/include/g++/bits/basic_string.tcc:160: error: assignment of read-only location" Regards, -Steve /usr/bin/g++ -c -UNDEBUG -DDEBUG -Dpowerpc -Ddarwin6_0 -I/home/smb/ boston/HEAD/boston/common/iscsi/src -I/home/smb/boston/HEAD/boston/ common/iscsi/share/include -g -O0 -L/home/smb/boston/HEAD/boston/ common/iscsi/share/lib -MD -o iscsi_dvd_targetd.o iscsi_dvd_targetd.cpp iscsi_dvd_targetd.cpp: In function `int main(int, const char**)': iscsi_dvd_targetd.cpp:31: error: no matching function for call to `store( boost::program_options::basic_parsed_options<const char>, boost::program_options::variables_map&)' /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/variables_map.hpp:138: error: candidates are: void boost::program_options::store(const boost::program_options::basic_parsed_options<char>&, boost::program_options::variables_map&, bool) /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/variables_map.hpp:146: error: void boost::program_options::store(const boost::program_options::basic_parsed_options<wchar_t>&, boost::program_options::variables_map&) /usr/include/g++/bits/stl_alloc.h: At global scope: /usr/include/g++/bits/stl_alloc.h: In instantiation of `std::allocator<const char>': /usr/include/g++/bits/basic_string.h:116: instantiated from `std::basic_string<const char, std::char_traits<const char>, std::allocator<const char> >' /usr/include/g++/bits/stl_vector.h:162: instantiated from `std::_Vector_base<_Tp, _Alloc>::~_Vector_base() [with _Tp = std::basic_string<const char, std::char_traits<const char>, std::allocator<const char> >, _Alloc = std::allocator<std::basic_string<const char, std::char_traits<const char>, std::allocator<const char> > >]' /usr/include/g++/bits/stl_vector.h:229: instantiated from `std::vector<_Tp, _Alloc>::vector(typename std::_Vector_base<_Tp, _Alloc>::allocator_type&) [with _Tp = std::basic_string<const char, std::char_traits<const char>, std::allocator<const char> >, _Alloc = std::allocator<std::basic_string<const char, std::char_traits<const char>, std::allocator<const char> > >]' /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/parsers.hpp:18: instantiated from `std::vector<std::basic_string<_CharT, std::char_traits<_CharT>, std::allocator<_CharT> >, std::allocator<std::basic_string<_CharT, std::char_traits<_CharT>, std::allocator<_CharT> > > > boost::program_options::detail::make_vector(Iterator, Iterator) [with charT = const char, Iterator = const char**]' /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/parsers.hpp:42: instantiated from `boost::program_options::basic_command_line_parser<charT>::basic_command _line_parser(int, charT**) [with charT = const char]' /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/parsers.hpp:118: instantiated from `boost::program_options::basic_parsed_options<charT> boost::program_options::parse_command_line(int, charT**, const boost::program_options::options_description&, int, boost::function1<std::pair<std::string, std::string>, const std::string&, std::allocator<boost::function_base> >) [with charT = const char]' iscsi_dvd_targetd.cpp:31: instantiated from here /usr/include/g++/bits/stl_alloc.h:662: error: `const _Tp* std::allocator<_Alloc>::address(const _Tp&) const [with _Tp = const char]' and `_Tp* std::allocator<_Alloc>::address(_Tp&) const [with _Tp = const char]' cannot be overloaded /usr/include/g++/bits/basic_string.tcc: In instantiation of `std::basic_string<const char, std::char_traits<const char>, std::allocator<const char> >': /usr/include/g++/bits/stl_vector.h:162: instantiated from `std::_Vector_base<_Tp, _Alloc>::~_Vector_base() [with _Tp = std::basic_string<const char, std::char_traits<const char>, std::allocator<const char> >, _Alloc = std::allocator<std::basic_string<const char, std::char_traits<const char>, std::allocator<const char> > >]' /usr/include/g++/bits/stl_vector.h:229: instantiated from `std::vector<_Tp, _Alloc>::vector(typename std::_Vector_base<_Tp, _Alloc>::allocator_type&) [with _Tp = std::basic_string<const char, std::char_traits<const char>, std::allocator<const char> >, _Alloc = std::allocator<std::basic_string<const char, std::char_traits<const char>, std::allocator<const char> > >]' /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/parsers.hpp:18: instantiated from `std::vector<std::basic_string<_CharT, std::char_traits<_CharT>, std::allocator<_CharT> >, std::allocator<std::basic_string<_CharT, std::char_traits<_CharT>, std::allocator<_CharT> > > > boost::program_options::detail::make_vector(Iterator, Iterator) [with charT = const char, Iterator = const char**]' /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/parsers.hpp:42: instantiated from `boost::program_options::basic_command_line_parser<charT>::basic_command _line_parser(int, charT**) [with charT = const char]' /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/parsers.hpp:118: instantiated from `boost::program_options::basic_parsed_options<charT> boost::program_options::parse_command_line(int, charT**, const boost::program_options::options_description&, int, boost::function1<std::pair<std::string, std::string>, const std::string&, std::allocator<boost::function_base> >) [with charT = const char]' iscsi_dvd_targetd.cpp:31: instantiated from here /usr/include/g++/bits/basic_string.h:307: error: `static void std::basic_string<_CharT, _Traits, _Alloc>::_S_copy_chars(_CharT*, __gnu_cxx::__normal_iterator<typename _Alloc::const_pointer, std::basic_string<_CharT, _Traits, _Alloc> >, __gnu_cxx::__normal_iterator<typename _Alloc::const_pointer, std::basic_string<_CharT, _Traits, _Alloc> >) [with _CharT = const char, _Traits = std::char_traits<const char>, _Alloc = std::allocator<const char>] ' and `static void std::basic_string<_CharT, _Traits, _Alloc>::_S_copy_chars(_CharT*, __gnu_cxx::__normal_iterator<typename _Alloc::pointer, std::basic_string<_CharT, _Traits, _Alloc> >, __gnu_cxx::__normal_iterator<typename _Alloc::pointer, std::basic_string<_CharT, _Traits, _Alloc> >) [with _CharT = const char, _Traits = std::char_traits<const char>, _Alloc = std::allocator<const char>] ' cannot be overloaded /usr/include/g++/bits/basic_string.h:315: error: `static void std::basic_string<_CharT, _Traits, _Alloc>::_S_copy_chars (_CharT*, const _CharT*, const _CharT*) [with _CharT = const char, _Traits = std::char_traits<const char>, _Alloc = std::allocator<const char>]' and ` static void std::basic_string<_CharT, _Traits, _Alloc>::_S_copy_chars(_CharT*, _CharT*, _CharT*) [with _CharT = const char, _Traits = std::char_traits<const char>, _Alloc = std::allocator<const char>] ' cannot be overloaded /usr/include/g++/bits/basic_string.h:636: error: `std::basic_string<_CharT, _Traits, _Alloc>& std::basic_string<_CharT, _Traits, _Alloc>::replace(__gnu_cxx::__normal_iterator<typename _Alloc::pointer, std::basic_string<_CharT, _Traits, _Alloc> >, __gnu_cxx::__normal_iterator<typename _Alloc::pointer, std::basic_string<_CharT, _Traits, _Alloc> >, const _CharT*, const _CharT*) [with _CharT = const char, _Traits = std::char_traits<const char>, _Alloc = std::allocator<const char>]' and `std::basic_string<_CharT, _Traits, _Alloc>& std::basic_string<_CharT, _Traits, _Alloc>::replace(__gnu_cxx::__normal_iterator<typename _Alloc::pointer, std::basic_string<_CharT, _Traits, _Alloc> >, __gnu_cxx::__normal_iterator<typename _Alloc::pointer, std::basic_string<_CharT, _Traits, _Alloc> >, _CharT*, _CharT*) [with _CharT = const char, _Traits = std::char_traits<const char>, _Alloc = std::allocator<const char>]' cannot be overloaded /usr/include/g++/bits/basic_string.h:647: error: `std::basic_string<_CharT, _Traits, _Alloc>& std::basic_string<_CharT, _Traits, _Alloc>::replace(__gnu_cxx::__normal_iterator<typename _Alloc::pointer, std::basic_string<_CharT, _Traits, _Alloc> >, __gnu_cxx::__normal_iterator<typename _Alloc::pointer, std::basic_string<_CharT, _Traits, _Alloc> >, __gnu_cxx::__normal_iterator<typename _Alloc::const_pointer, std::basic_string<_CharT, _Traits, _Alloc> >, __gnu_cxx::__normal_iterator<typename _Alloc::const_pointer, std::basic_string<_CharT, _Traits, _Alloc> >) [with _CharT = const char, _Traits = std::char_traits<const char>, _Alloc = std::allocator<const char>] ' and `std::basic_string<_CharT, _Traits, _Alloc>& std::basic_string<_CharT, _Traits, _Alloc>::replace(__gnu_cxx::__normal_iterator<typename _Alloc::pointer, std::basic_string<_CharT, _Traits, _Alloc> >, __gnu_cxx::__normal_iterator<typename _Alloc::pointer, std::basic_string<_CharT, _Traits, _Alloc> >, __gnu_cxx::__normal_iterator<typename _Alloc::pointer, std::basic_string<_CharT, _Traits, _Alloc> >, __gnu_cxx::__normal_iterator<typename _Alloc::pointer, std::basic_string<_CharT, _Traits, _Alloc> >) [with _CharT = const char, _Traits = std::char_traits<const char>, _Alloc = std::allocator<const char>] ' cannot be overloaded /usr/include/g++/bits/basic_string.h: In member function ` std::basic_string<_CharT, _Traits, _Alloc>::_Rep* std::basic_string<_CharT, _Traits, _Alloc>::_M_rep() const [with _CharT = const char, _Traits = std::char_traits<const char>, _Alloc = std::allocator<const char>]': /usr/include/g++/bits/basic_string.h:355: instantiated from `std::basic_string<_CharT, _Traits, _Alloc>::~basic_string() [with _CharT = const char, _Traits = std::char_traits<const char>, _Alloc = std::allocator<const char>]' /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/parsers.hpp:22: instantiated from `std::vector<std::basic_string<_CharT, std::char_traits<_CharT>, std::allocator<_CharT> >, std::allocator<std::basic_string<_CharT, std::char_traits<_CharT>, std::allocator<_CharT> > > > boost::program_options::detail::make_vector(Iterator, Iterator) [with charT = const char, Iterator = const char**]' /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/parsers.hpp:42: instantiated from `boost::program_options::basic_command_line_parser<charT>::basic_command _line_parser(int, charT**) [with charT = const char]' /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/parsers.hpp:118: instantiated from `boost::program_options::basic_parsed_options<charT> boost::program_options::parse_command_line(int, charT**, const boost::program_options::options_description&, int, boost::function1<std::pair<std::string, std::string>, const std::string&, std::allocator<boost::function_base> >) [with charT = const char]' iscsi_dvd_targetd.cpp:31: instantiated from here /usr/include/g++/bits/basic_string.h:257: error: reinterpret_cast from `const char*' to `std::basic_string<const char, std::char_traits<const char>, std::allocator<const char> >::_Rep*' casts away const (or volatile) /usr/include/g++/bits/basic_string.tcc: In member function `_CharT* std::basic_string<_CharT, _Traits, _Alloc>::_Rep::_M_clone(const _Alloc&, typename _Alloc::size_type) [with _CharT = const char, _Traits = std::char_traits<const char>, _Alloc = std::allocator<const char>]': /usr/include/g++/bits/basic_string.h:195: instantiated from `_CharT* std::basic_string<_CharT, _Traits, _Alloc>::_Rep::_M_grab (const _Alloc&, const _Alloc&) [with _CharT = const char, _Traits = std::char_traits<const char>, _Alloc = std::allocator<const char>]' /usr/include/g++/bits/basic_string.tcc:195: instantiated from `std::basic_string<_CharT, _Traits, _Alloc>::basic_string(const std::basic_string<_CharT, _Traits, _Alloc>&) [with _CharT = const char, _Traits = std::char_traits<const char>, _Alloc = std::allocator<const char>]' /usr/include/g++/bits/stl_construct.h:78: instantiated from `void std::_Construct(_T1*, const _T2&) [with _T1 = std::basic_string<const char, std::char_traits<const char>, std::allocator<const char> >, _T2 = std::basic_string<const char, std::char_traits<const char>, std::allocator<const char> >]' /usr/include/g++/bits/stl_vector.h:599: instantiated from `void std::vector<_Tp, _Alloc>::push_back(const _Tp&) [with _Tp = std::basic_string<const char, std::char_traits<const char>, std::allocator<const char> >, _Alloc = std::allocator<std::basic_string<const char, std::char_traits<const char>, std::allocator<const char> > >]' /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/parsers.hpp:22: instantiated from `std::vector<std::basic_string<_CharT, std::char_traits<_CharT>, std::allocator<_CharT> >, std::allocator<std::basic_string<_CharT, std::char_traits<_CharT>, std::allocator<_CharT> > > > boost::program_options::detail::make_vector(Iterator, Iterator) [with charT = const char, Iterator = const char**]' /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/parsers.hpp:42: instantiated from `boost::program_options::basic_command_line_parser<charT>::basic_command _line_parser(int, charT**) [with charT = const char]' /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/parsers.hpp:118: instantiated from `boost::program_options::basic_parsed_options<charT> boost::program_options::parse_command_line(int, charT**, const boost::program_options::options_description&, int, boost::function1<std::pair<std::string, std::string>, const std::string&, std::allocator<boost::function_base> >) [with charT = const char]' iscsi_dvd_targetd.cpp:31: instantiated from here /usr/include/g++/bits/basic_string.tcc:596: error: assignment of read- only location /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/convert.hpp: In function `std::vector<std::string, std::allocator<std::string> > boost::program_options::to_internal(const std::vector<T, std::allocator<_CharT> >&) [with T = std::basic_string<const char, std::char_traits<const char>, std::allocator<const char> >]': /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/parsers.hpp:42: instantiated from `boost::program_options::basic_command_line_parser<charT>::basic_command _line_parser(int, charT**) [with charT = const char]' /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/parsers.hpp:118: instantiated from `boost::program_options::basic_parsed_options<charT> boost::program_options::parse_command_line(int, charT**, const boost::program_options::options_description&, int, boost::function1<std::pair<std::string, std::string>, const std::string&, std::allocator<boost::function_base> >) [with charT = const char]' iscsi_dvd_targetd.cpp:31: instantiated from here /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/convert.hpp:79: error: no matching function for call to `to_internal(const std::basic_string<const char, std::char_traits<const char>, std::allocator<const char> >&)' /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/convert.hpp:70: error: candidates are: std::string boost::program_options::to_internal(const std::string&) /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/convert.hpp:72: error: std::string boost::program_options::to_internal(const std::wstring&) /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/parsers.hpp: In member function `boost::program_options::basic_parsed_options<charT> boost::program_options::basic_command_line_parser<charT>::run() [with charT = const char]': /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/parsers.hpp:118: instantiated from `boost::program_options::basic_parsed_options<charT> boost::program_options::parse_command_line(int, charT**, const boost::program_options::options_description&, int, boost::function1<std::pair<std::string, std::string>, const std::string&, std::allocator<boost::function_base> >) [with charT = const char]' iscsi_dvd_targetd.cpp:31: instantiated from here /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/parsers.hpp:106: error: no matching function for call to ` boost::program_options::basic_parsed_options<const char>:: basic_parsed_options (boost::program_options::basic_parsed_options<char>&)' /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/parsers.hpp:118: error: candidates are: boost::program_options::basic_parsed_options<const char>::basic_parsed_options(const boost::program_options::basic_parsed_options<const char>&) /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/parsers.hpp:35: error: boost::program_options::basic_parsed_options<charT>::basic_parsed_option s(const boost::program_options::options_description*) [with charT = const char] /usr/include/g++/bits/basic_string.tcc: In static member function `static _CharT* std::basic_string<_CharT, _Traits, _Alloc>::_S_construct (_InIter, _InIter, const _Alloc&, std::forward_iterator_tag) [with _FwdIter = const char*, _CharT = const char, _Traits = std::char_traits<const char>, _Alloc = std::allocator<const char>]': /usr/include/g++/bits/basic_string.h:670: instantiated from `static _CharT* std::basic_string<_CharT, _Traits, _Alloc>::_S_construct_aux (_InIter, _InIter, const _Alloc&, __false_type) [with _InIter = const char*, _CharT = const char, _Traits = std::char_traits<const char>, _Alloc = std::allocator<const char>]' /usr/include/g++/bits/basic_string.h:687: instantiated from `static _CharT* std::basic_string<_CharT, _Traits, _Alloc>::_S_construct (_InIter, _InIter, const _Alloc&) [with _InIter = const char*, _CharT = const char, _Traits = std::char_traits<const char>, _Alloc = std::allocator<const char>]' /usr/include/g++/bits/basic_string.tcc:229: instantiated from `std::basic_string<_CharT, _Traits, _Alloc>::basic_string(const _CharT*, const _Alloc&) [with _CharT = const char, _Traits = std::char_traits<const char>, _Alloc = std::allocator<const char>]' /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/parsers.hpp:22: instantiated from `std::vector<std::basic_string<_CharT, std::char_traits<_CharT>, std::allocator<_CharT> >, std::allocator<std::basic_string<_CharT, std::char_traits<_CharT>, std::allocator<_CharT> > > > boost::program_options::detail::make_vector(Iterator, Iterator) [with charT = const char, Iterator = const char**]' /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/parsers.hpp:42: instantiated from `boost::program_options::basic_command_line_parser<charT>::basic_command _line_parser(int, charT**) [with charT = const char]' /home/smb/boston/HEAD/boston/common/iscsi/share/include/boost/ program_options/detail/parsers.hpp:118: instantiated from `boost::program_options::basic_parsed_options<charT> boost::program_options::parse_command_line(int, charT**, const boost::program_options::options_description&, int, boost::function1<std::pair<std::string, std::string>, const std::string&, std::allocator<boost::function_base> >) [with charT = const char]' iscsi_dvd_targetd.cpp:31: instantiated from here /usr/include/g++/bits/basic_string.tcc:160: error: assignment of read- only location make: *** [iscsi_dvd_targetd.o] Error 1 -------- Steve Byan <smb(a)egenera.com> Software Architect Egenera, Inc. 165 Forest Street Marlboro, MA 01752 (508) 858-3125

1 0

Re: [Boost-users] shared_ptr and typedef
by Sohail Somani 25 Jan '06

25 Jan '06

> > Why is there a need? Presumably you're potential surrogate > for shared_ptr > > will also support operator *, and that's all you use in > your function. > > Why is there a need to do what? I'm not following you here. I've > gone through and specified Type everywhere in my application. It's > ugly but it works. Would the upcoming template typedef feature > avoid the need to specify Type in the call? I think what Jens is getting at is that you should use the duck-typing that C++ templating affords you: #include <boost/smart_ptr.hpp> #include <iostream> using namespace std; template<typename Handle> void print_handle(Handle p) { cout << *p << endl; } int main() { int * a = new int(5); boost::shared_ptr<int> b(new int(6)); print_handle(a);print_handle(b); } $ ./a.out 5 6

2 1

[spirit] "parseable" foo_thing with Boost.Spirit pattern
by Pedro Lamarão 25 Jan '06

25 Jan '06

Here follows a simple pattern to use Boost.Spirit to create a "parseable" object, with a bonus formatted input operator, allowing you quick access to formatter input for your type. (Yeah, this stuff needs tweaking for better error handling, etc.) class foo_thing { public: /* Other methods and stuff. */ template <typename ForwardIterator> boost::spirit::parse_info<IteratorT> parse (ForwardIterator begin, ForwardIterator end); private: class grammar; /* Data members, etc. */ }; template <typename CharT, typename TraitsT> std::basic_istream<CharT, TraitsT>& operator>> (std::basic_istream<CharT, TraitsT>& i, foo_thing& thing) { using namespace std; using namespace boost::spirit; typedef multi_pass<istreambuf_iterator<CharT> > iterator_t; iterator_t begin(i); iterator_t end = make_multi_pass(istreambuf_iterator<CharT>()); /* What if thing.parse() throws? */ parse_info<iterator_t> info = thing.parse(begin, end); if (!info.hit) i.setstate(ios_base::failbit); return i; } class foo_thing::grammar : public boost::spirit::grammar<foo_thing::grammar> { public: grammar (foo_thing& thing) : _M_thing(thing) {} template <typename ScannerT> class definition; private: foo_thing mutable& _M_thing; }; template <typename ScannerT> class foo_thing::grammar::definition { public: /* Define this one; your parser ultimately writes to self._M_thing. */ definition (foo_thing::grammar const& self); boost::spirit::rule<ScannerT> const& start () const; private: /* Populate with rules. */ }; template <typename IteratorT> boost::spirit::parse_info<IteratorT> foo_thing::parse (IteratorT begin, IteratorT end) { namespace s = boost::spirit; grammar g(*this); s::parse_info<IteratorT> r = s::parse(begin, end, g); return r; } -- Pedro Lamarão Desenvolvimento Intersix Technologies S.A. SP: (55 11 3803-9300) RJ: (55 21 3852-3240) www.intersix.com.br Your Security is our Business

1 0

Re: [Boost-users] Weird cross compiling issue
by James Hughes 25 Jan '06

25 Jan '06

> From: Rene Rivera [mailto:grafik.list@redshift-software.com] > Sent: 23 January 2006 16:21 > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] Weird cross compiling issue > > > James Hughes wrote: > > Hello all, > > > > I am cross compiling Boost to an embedded Linux Arm > architecture. I reported > > a problem a week or so ago with failures in some of the > libraries which I > > was unable to solve, and have a bit more information. > > > > One of the issues appears with the serialisation library. > Although I am > > compiling for Arm, the serialisation libs end up as Intel > X86 binaries, even > > though all the other successfully compiled libs are ARM. > This then leads to > > problems elsewhere with libraries that appear to need the > serialisation > > libs. > > > > I can only think that there is an issue with the make > system to do with > > serialisation area. > > > > Anyone have any comments/thoughts? > > Well I don't see anything that would make it not build with the same > compiler as the others. Are you sure it's not just a leftover > from some > previous build? Could you do a build with the "-d+2" option > to see which > commands it's invoking to compile? To verify that it's always > using the > cross compiler. I thought it odd too. I manually deleted all the files flagged as Intel binaries, then re-did the build, and hey presto, they reappeared - as Intel binaries!! I will try the debug option you suggest. > > > In addition, when I do a build to a particular directory: > > > > bjam > "-sGCC_ROOT_DIRECTORY=/opt/montavista/mobilinux/devkit/arm/iwmmxt_le" > > "-sGCC=iwmmxt_le-gcc" "-sGXX=iwmmxt_le-g++" stage > > > > the stage folder is created, in which is a lib folder, in > which are all the > > binaries (including the defective Intel ones). However, I > would also expect > > some header files somewhere - should there also be a h (or > header) folder > > next to lib? If not where are the headers I need to include > in my apps using > > Boost? > > The includes only show up if you do "install". Since you > obviously don't > want to obliterate your system Boost install you'll also have > to specify > the "--prefix" of where to install :-) Thanks - that's what I needed to know. I pressume I could simply copy the headers from the boost directory to where I need them - is this all the build/install does? James

2 1

shared_ptr and typedef
by David A. Greene 25 Jan '06

25 Jan '06

Well, if nothing else, I'm learning lots about the corners of the language! I've got the following testcase: #include <boost/shared_ptr.hpp> #include <iostream> template<typename Base> class Handle { public: typedef boost::shared_ptr<Base> type; }; template<typename Type> void print_shared_ptr(boost::shared_ptr<Type> ptr) { std::cout << "Value is " << *ptr << std::endl; } template<typename Type> void print_handle(typename Handle<Type>::type ptr) { std::cout << "Value is " << *ptr << std::endl; } int main(void) { Handle<int>::type iptr(new int(10)); print_shared_ptr(iptr); print_handle<int>(iptr); print_handle(iptr); return(0); } The calls to print_shared_ptr and the first print_handle resolve just fine but the compiler (g++ 4.0.2) can't seem to resolve the final call to print_handle: shared_ptr.cc: In function 'int main()': shared_ptr.cc:29: error: no matching function for call to 'print_handle(boost::shared_ptr<int>&)' The point of class Handle is to hide the implementation detail that boost::shared_ptr is being used to manage resources. I would like the ability to easily change the type of smart pointer used throughout the application. What's going on here? Is there a way to make this work without having to explicitly specify the type to print_handle? Thanks. -Dave

1 0

[BGL] Help with initialization of graph from image
by Jef Driesen 25 Jan '06

25 Jan '06

I'm trying to create a graph from an image, where pixel values are regions labels. I have defined my graph to use lists instead of the vectors (because I need to add/remove vertices and edges) and one extra property for the vertex (the region label): typedef boost::adjacency_list< boost::listS, // Adjacency list boost::listS, // Vertex list boost::undirectedS, // Undirected graph unsigned int, // Vertex property (=label) boost::no_property, // Edge property boost::no_property, // Graph property boost::listS // Edge list > graph; typedef boost::graph_traits<graph>::vertex_descriptor vertex_t; typedef boost::graph_traits<graph>::edge_descriptor edge_t; I have the following pseudo code to populate the graph: graph g; for each pixel (i,j) { unsigned int u_label = image[i][j]; for each neighbourhood pixel (k,l) { unsigned int v_label = image[k][l]; if (u_label != v_label) { // Find/add both vertices vertex_t u = boost::add_vertex(u_label,g); vertex_t v = boost::add_vertex(v_label, g); // Find/add edge boost::add_edge(u, v, g); } } } But this creates many duplicates (with regard to the label) for both vertices and edges. How can i prevent this? Would using a set for the edges solves my problem? And how can I add a vertex only if it does not exist already?

2 3

[serialization] How to serializa reference counted C arrays?
by Lukasz Dobrek 25 Jan '06

25 Jan '06

Basically can anybody give me a hint how to properly serialize this class, using boost serialization library? Regards Lukasz class A { public: A( int size ) : m_size( size ) { m_ref_count = new int; *m_ref_count = 1; m_vec = new double [ m_size ]; } ~A(){ (*m_ref_count)--; if ( *m_ref_count == 0 ){ delete m_vec; } } A( const A & a ) : m_size ( a.m_size ) , m_ref_count( a.m_ref_count ) , m_vec( a.m_vec ) { (*m_ref_count)++; } int * m_ref_count; double * m_vec; int m_size; };

1 0

Re: [Boost-users] thread library
by Sohail Somani 24 Jan '06

24 Jan '06

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Jens Theisen > Sent: Tuesday, January 24, 2006 10:33 AM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] thread library > > monade wrote: > > > Ok, it may be no memory leak, but only a harmless resource leak (as > > Alexandrescu calls it in his singleton chapter), but I don't like it > > anyway (my own singletons does not leak). > > If there would be a delete in the destructor, you would not > gain anything: > The destructor of a singleton is conceptually called on program > termination and that's also where all resources are freed by > the operating > system anyway. So it's perfectly reasonable to not free it. I could've sworn we just went through this a few months back. Perhaps its time to put a comment that links to the appropriate boost mailing thread. http://lists.boost.org/boost-users/2005/08/13538.php Might be related?

3 2

[GRAPH] How to use an external edge weight map in dijkstra_shortest_paths
by rohit wadhwa 24 Jan '06

24 Jan '06

Hi, I am a newbie and have been struggling over the past couple of days with dijkstra_shortest_paths. I want to use WeightMap as an external property. I create the Graph as follows typedef boost::adjacency_list<boost::vecS,boost::vecS, boost::directedS,boost::no_property, boost::property<boost::edge_index_t, std::size_t> > Graph; I added edges using add_edge(fromVertex, toVertex, edge_index, Graph); My edge_index can have any long value and they are not necessarily in sequence. Also, I want to create the weight map on the fly and want to use a std::map. I have tried all sorts of things but to no avail. Any help will be appreciated. Thanks, Rohit.

1 0

[iostreams] non-copyable device with Boost.Ref pattern
by Pedro Lamarão 24 Jan '06

24 Jan '06

Here follows a simple pattern to use Boost.IOstreams with your non-copyable Device, allowing you quick access to formatted input and output: #include <boost/iostreams/stream.hpp> #include <boost/ref.hpp> #include "foo_device.hpp" /* Don't; just to make lines shorter. */ using boost::iostreams; using boost; class foo_device; class foo_stream_base { public: /* Define constructor forwarding to foo_device. */ foo_stream_base (...) : _M_device(...) {} protected: foo_device _M_device; }; class foo_stream : private foo_stream_base, public stream<reference_wrapper<foo_device> > { public: /* Define constructor forwarding to foo_device. */ foo_stream (...) : foo_stream_base(...), stream<reference_wrapper<foo_device> >(ref(_M_device)) {} }; -- Pedro Lamarão Desenvolvimento Intersix Technologies S.A. SP: (55 11 3803-9300) RJ: (55 21 3852-3240) www.intersix.com.br Your Security is our Business

1 1

boost::iostreams - access object 'below' the stream
by Leon Mergen 24 Jan '06

24 Jan '06

Hello, Little question: I'm toying around to replace my socket_stream class with a boost::iostreams::stream class to implement a more generic approach... now, I use the socket file descriptor/handle as a unique identifier in my application, and so far this could easily be retrieved; however, when the boost::iostreams::stream "layer" is on top of my socket class, this is pretty much inaccessable. What is the most common approach to handle this problem ? I really don't want to resort to some kind of tuple which describes the stream and the handle, but at the moment, a construction like that is the only thing my mind can come up with... any suggestions ? Thanks in advance for any reactions. Regards, Leon Mergen

2 1

[lambda] "Invalid use of void expression"
by David A. Greene 24 Jan '06

24 Jan '06

I'm having some trouble with BLL and Boost.Function in this simple testcase: #include <boost/lambda/bind.hpp> #include <boost/function.hpp> #include <iostream> class Test { public: void foo(int a) { std::cout << "a is " << a << std::endl; }; }; template<typename Function> class Caller { private: Function func; public: Caller(Function f) : func(f) {}; void bar(void) { func(); }; }; int main(void) { Test tester; int value = 10; Caller<boost::function<void (void)> > printer(boost::lambda::bind(boost::lambda::bind(&Test::foo, tester, boost::lambda::_1), value)); printer.bar(); return(0); } The g++ 4.0.3 compiler complains (full trace below): /usr/include/boost/lambda/detail/lambda_functor_base.hpp:408: error: invalid use of void expression Is it not legal to bind a lambda-bound function? -Dave ---------------------- /usr/include/boost/lambda/detail/lambda_functor_base.hpp: In member function 'RET boost::lambda::lambda_functor_base<boost::lambda::action<2, Act>, Args>::call(A&, B&, C&, Env&) const [with RET = boost::tuples::null_type, A = const boost::tuples::null_type, B = const boost::tuples::null_type, C = const boost::tuples::null_type, Env = const boost::tuples::null_type, Act = boost::lambda::function_action<2, boost::lambda::detail::unspecified>, Args = boost::tuples::tuple<const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<3, boost::lambda::function_action<3, boost::lambda::detail::unspecified> >, boost::tuples::tuple<void (Test::* const)(int), const Test, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, const int, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type>]': /usr/include/boost/lambda/detail/lambda_functors.hpp:140: instantiated from 'typename T::sig<boost::tuples::null_type>::type boost::lambda::lambda_functor<Base>::operator()() const [with T = boost::lambda::lambda_functor_base<boost::lambda::action<2, boost::lambda::function_action<2, boost::lambda::detail::unspecified> >, boost::tuples::tuple<const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<3, boost::lambda::function_action<3, boost::lambda::detail::unspecified> >, boost::tuples::tuple<void (Test::* const)(int), const Test, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, const int, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >]' /usr/include/boost/function/function_template.hpp:136: instantiated from 'static void boost::detail::function::void_function_obj_invoker0<FunctionObj, R>::invoke(boost::detail::function::any_pointer) [with FunctionObj = boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<2, boost::lambda::function_action<2, boost::lambda::detail::unspecified> >, boost::tuples::tuple<const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<3, boost::lambda::function_action<3, boost::lambda::detail::unspecified> >, boost::tuples::tuple<void (Test::* const)(int), const Test, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, const int, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, R = void]' /usr/include/boost/function/function_template.hpp:479: instantiated from 'void boost::function0<R, Allocator>::assign_to(FunctionObj, boost::detail::function::function_obj_tag) [with FunctionObj = boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<2, boost::lambda::function_action<2, boost::lambda::detail::unspecified> >, boost::tuples::tuple<const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<3, boost::lambda::function_action<3, boost::lambda::detail::unspecified> >, boost::tuples::tuple<void (Test::* const)(int), const Test, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, const int, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, R = void, Allocator = std::allocator<void>]' /usr/include/boost/function/function_template.hpp:430: instantiated from 'void boost::function0<R, Allocator>::assign_to(Functor) [with Functor = boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<2, boost::lambda::function_action<2, boost::lambda::detail::unspecified> >, boost::tuples::tuple<const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<3, boost::lambda::function_action<3, boost::lambda::detail::unspecified> >, boost::tuples::tuple<void (Test::* const)(int), const Test, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, const int, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, R = void, Allocator = std::allocator<void>]' /usr/include/boost/function/function_template.hpp:294: instantiated from 'boost::function0<R, Allocator>::function0(Functor, typename boost::enable_if_c<boost::type_traits::ice_not<boost::is_integral<Functor>::value>::value, int>::type) [with Functor = boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<2, boost::lambda::function_action<2, boost::lambda::detail::unspecified> >, boost::tuples::tuple<const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<3, boost::lambda::function_action<3, boost::lambda::detail::unspecified> >, boost::tuples::tuple<void (Test::* const)(int), const Test, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, const int, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, R = void, Allocator = std::allocator<void>]' /usr/include/boost/function/function_template.hpp:637: instantiated from 'boost::function<R ()(), Allocator>::function(Functor, typename boost::enable_if_c<boost::type_traits::ice_not<boost::is_integral<Functor>::value>::value, int>::type) [with Functor = boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<2, boost::lambda::function_action<2, boost::lambda::detail::unspecified> >, boost::tuples::tuple<const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<3, boost::lambda::function_action<3, boost::lambda::detail::unspecified> >, boost::tuples::tuple<void (Test::* const)(int), const Test, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, const int, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, R = void, Allocator = std::allocator<void>]' lambda3.cc:27: instantiated from here /usr/include/boost/lambda/detail/lambda_functor_base.hpp:408: error: invalid use of void expression /usr/include/boost/lambda/detail/actions.hpp: In static member function 'static RET boost::lambda::function_action<3, T>::apply(A1&, A2&, A3&) [with RET = void, A1 = void (Test::* const)(int), A2 = const Test, A3 = const boost::tuples::null_type, T = boost::lambda::detail::unspecified]': /usr/include/boost/lambda/detail/lambda_functor_base.hpp:425: instantiated from 'RET boost::lambda::lambda_functor_base<boost::lambda::action<3, Act>, Args>::call(A&, B&, C&, Env&) const [with RET = void, A = const boost::tuples::null_type, B = const boost::tuples::null_type, C = const boost::tuples::null_type, Env = const boost::tuples::null_type, Act = boost::lambda::function_action<3, boost::lambda::detail::unspecified>, Args = boost::tuples::tuple<void (Test::* const)(int), const Test, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type>]' /usr/include/boost/lambda/detail/select_functions.hpp:61: instantiated from 'static RET boost::lambda::detail::r_select<RET>::go(const boost::lambda::lambda_functor<Arg>&, A&, B&, C&, Env&) [with Arg = boost::lambda::lambda_functor_base<boost::lambda::action<3, boost::lambda::function_action<3, boost::lambda::detail::unspecified> >, boost::tuples::tuple<void (Test::* const)(int), const Test, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >, A = const boost::tuples::null_type, B = const boost::tuples::null_type, C = const boost::tuples::null_type, Env = const boost::tuples::null_type, RET = void]' /usr/include/boost/lambda/detail/lambda_functor_base.hpp:408: instantiated from 'RET boost::lambda::lambda_functor_base<boost::lambda::action<2, Act>, Args>::call(A&, B&, C&, Env&) const [with RET = boost::tuples::null_type, A = const boost::tuples::null_type, B = const boost::tuples::null_type, C = const boost::tuples::null_type, Env = const boost::tuples::null_type, Act = boost::lambda::function_action<2, boost::lambda::detail::unspecified>, Args = boost::tuples::tuple<const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<3, boost::lambda::function_action<3, boost::lambda::detail::unspecified> >, boost::tuples::tuple<void (Test::* const)(int), const Test, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, const int, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type>]' /usr/include/boost/lambda/detail/lambda_functors.hpp:140: instantiated from 'typename T::sig<boost::tuples::null_type>::type boost::lambda::lambda_functor<Base>::operator()() const [with T = boost::lambda::lambda_functor_base<boost::lambda::action<2, boost::lambda::function_action<2, boost::lambda::detail::unspecified> >, boost::tuples::tuple<const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<3, boost::lambda::function_action<3, boost::lambda::detail::unspecified> >, boost::tuples::tuple<void (Test::* const)(int), const Test, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, const int, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >]' /usr/include/boost/function/function_template.hpp:136: instantiated from 'static void boost::detail::function::void_function_obj_invoker0<FunctionObj, R>::invoke(boost::detail::function::any_pointer) [with FunctionObj = boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<2, boost::lambda::function_action<2, boost::lambda::detail::unspecified> >, boost::tuples::tuple<const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<3, boost::lambda::function_action<3, boost::lambda::detail::unspecified> >, boost::tuples::tuple<void (Test::* const)(int), const Test, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, const int, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, R = void]' /usr/include/boost/function/function_template.hpp:479: instantiated from 'void boost::function0<R, Allocator>::assign_to(FunctionObj, boost::detail::function::function_obj_tag) [with FunctionObj = boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<2, boost::lambda::function_action<2, boost::lambda::detail::unspecified> >, boost::tuples::tuple<const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<3, boost::lambda::function_action<3, boost::lambda::detail::unspecified> >, boost::tuples::tuple<void (Test::* const)(int), const Test, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, const int, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, R = void, Allocator = std::allocator<void>]' /usr/include/boost/function/function_template.hpp:430: instantiated from 'void boost::function0<R, Allocator>::assign_to(Functor) [with Functor = boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<2, boost::lambda::function_action<2, boost::lambda::detail::unspecified> >, boost::tuples::tuple<const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<3, boost::lambda::function_action<3, boost::lambda::detail::unspecified> >, boost::tuples::tuple<void (Test::* const)(int), const Test, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, const int, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, R = void, Allocator = std::allocator<void>]' /usr/include/boost/function/function_template.hpp:294: instantiated from 'boost::function0<R, Allocator>::function0(Functor, typename boost::enable_if_c<boost::type_traits::ice_not<boost::is_integral<Functor>::value>::value, int>::type) [with Functor = boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<2, boost::lambda::function_action<2, boost::lambda::detail::unspecified> >, boost::tuples::tuple<const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<3, boost::lambda::function_action<3, boost::lambda::detail::unspecified> >, boost::tuples::tuple<void (Test::* const)(int), const Test, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, const int, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, R = void, Allocator = std::allocator<void>]' /usr/include/boost/function/function_template.hpp:637: instantiated from 'boost::function<R ()(), Allocator>::function(Functor, typename boost::enable_if_c<boost::type_traits::ice_not<boost::is_integral<Functor>::value>::value, int>::type) [with Functor = boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<2, boost::lambda::function_action<2, boost::lambda::detail::unspecified> >, boost::tuples::tuple<const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<3, boost::lambda::function_action<3, boost::lambda::detail::unspecified> >, boost::tuples::tuple<void (Test::* const)(int), const Test, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, const int, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >, R = void, Allocator = std::allocator<void>]' lambda3.cc:27: instantiated from here /usr/include/boost/lambda/detail/actions.hpp:96: error: no matching function for call to 'boost::lambda::function_adaptor<void (Test::*)(int)>::apply(void (Test::* const&)(int), const Test&, const boost::tuples::null_type&)' /usr/include/boost/lambda/detail/function_adaptors.hpp:245: note: candidates are: static Result boost::lambda::function_adaptor<Result (Object::*)(Arg1)>::apply(Result (Object::*)(Arg1), Object*, A1&) [with RET = void, A1 = const boost::tuples::null_type, Object = Test, Arg1 = int, Result = void] /usr/include/boost/lambda/detail/function_adaptors.hpp:249: note: static Result boost::lambda::function_adaptor<Result (Object::*)(Arg1)>::apply(Result (Object::*)(Arg1), Object&, A1&) [with RET = void, A1 = const boost::tuples::null_type, Object = Test, Arg1 = int, Result = void] /usr/include/boost/lambda/detail/actions.hpp:96: error: return-statement with a value, in function returning 'void'

2 5

thread library
by Robert Hanson 24 Jan '06

24 Jan '06

I'm looking at porting a windows (win32) app to linux. Is there a good reason to consider the boost thread library over the linux thread library? Does boost provide a wrapper for threads, so that I won't need to change my source code when porting between the two?

7 13

How to reduce the boost library size
by Jianhong Wang 24 Jan '06

24 Jan '06

Hi I compiled version 1.33.1 under a Windows XP machine with MingW (gcc 3.4.2). The compiling is very smoothing. However the size of directory "boost" is around 1.27 GB. I believe there is some command to clean the building lib, but I could not find it. Any suggestion? thanks!

2 1

Tokenizer usage, combining escaped_list_ and char_?
by Jeremy Tudisco 24 Jan '06

24 Jan '06

I'm attempting to process a scripting language from a file through tokenizer (only recently found out about Spirit, more on that later), and am having difficulties, namely, in processing input like this: "[ ExampleRoutine input; switch( input.messageNumber ) { 1: "Number 1"; 2: "Stand. On one foot (and jump around)"; 3: ! a comment to be ignored input.messageNumber = 1; break; } ];" The ending quotes mark the input as a string literal, the internal are part of the file. The problem comes from the fact that I need to process certain separators as tokens, such as braces, parentheses, periods, end lines, etc, but also allow escape characters in the case of the quotes, which should be treated as one returned token. My current method of processing this is: typedef char_separator<char> CharSep; typedef tokenizer<CharSep> CharTokenizer; typedef CharTokenizer::iterator CTokenIter; const CharSep g_RoutineSep(" \t\n,", "\"';[]{}()<>.!"); #define S_QUOTE "\"" ... // meanwhile, inside a function body CharTokenizer tok( getRoutineFromFile(), g_RoutineSep ); CTokenIter curTok( tok.begin() ); for(; ( curTok != tok.end() ) && ( *curTok != S_CBRACKET ); ++curTok ) { string curWord; if( ( *curTok == S_QUOTE ) { for(++curTok; ( *curTok != S_QUOTE ) && ( curTok != tok.end() ); ++curTok) { curWord += *curTok + ' '; // sure, we could check to see if *curTok is a punctation mark, and if so // not include that last space, but a better way must exist! } } else { // assume it's a command word, and process it here } } Of course, this is prone to gross misinterpretation, as "switch( input.messageNumber )" would be handled in each iteration as "switch", "(", "input", ".", "messageNumber", ")". Yet, this same functionality breaks the string literal into unnatural spacings, as the above code would turn it into "Stand . On one foot ( and jump around ) ", which isn't desired. However, as it stands, escape_list_separator doesn't return the separators, it just acts upon them, so all that fancy operator parsing isn't possible out of the box, requiring breaking things like "switch(" and "input.messageNumber" into separate things. Possible, yes, but extra work. So, the question. Could my needs be satisfied by defining my own TokenizerFunction, and if so, is there a simpler/more exhaustive reference besides the page? Or, conversely, is it time to look into Spirit? - Veni, Vidi, Vemaili. I came, I saw, I replied. -- Jeremy Tudisco, circa now.

2 1

Re: [Boost-users] How to reduce the boost library size
by Merrill Cornish 24 Jan '06

24 Jan '06

Jianhong, If you did a simple Boost build without restricting the output, then your Boost output directory will have many variants of each library. For example, you will have static and dynamic libraries; libraries with and without debug information, libraries with and without threading. And, for each of the above, you will have a two copies of the library named with and without the Boost version number (e.g., -1_31_1) as a suffix. If you decided what combination of debug/threading/static/version you want, you can delete the others, or at least move them elsewhere. Merrill

1 0

Re: [Boost-users] boost::serialization stream exception
by Adrian Grigore 24 Jan '06

24 Jan '06

Jeff Flinn Wrote: >Open your streams with 'binary' mode. Thanks, Jeff! And sorry for the obvious blunder :-) Best Regards, -- Adrian Grigore -- Adrian Grigore adrian(a)lobstersoft.com Lobstersoft - Fun Brain-Bending Games For All Ages http://www.lobstersoft.com Member of the Association of Shareware Professionals

1 0

boost thread does not honour BOOST_ALL_DYN_LINK
by Inge Norum 24 Jan '06

24 Jan '06

The boost thread library does not honour the BOOST_ALL_DYN_LINK setting in config/user.hpp. Thread used to be only available as a dynamically linked library in version 1.31, and I see a note about this in the comment for BOOST_ALL_DYN_LINK. I guess that it now ought to honour this general setting, to avoid defaulting to static linkage even when this is defined? Regards, Inge Norum thread/detail/config.hpp: #if defined(BOOST_THREAD_BUILD_DLL) //Build dll #elif defined(BOOST_THREAD_BUILD_LIB) //Build lib #elif defined(BOOST_THREAD_USE_DLL) //Use dll #elif defined(BOOST_THREAD_USE_LIB) //Use lib #else //Use default # if defined(BOOST_HAS_WINTHREADS) # if defined(BOOST_MSVC) || defined(BOOST_INTEL_WIN) //For compilers supporting auto-tss cleanup //with Boost.Threads lib, use Boost.Threads lib # define BOOST_THREAD_USE_LIB # else //For compilers not yet supporting auto-tss cleanup //with Boost.Threads lib, use Boost.Threads dll # define BOOST_THREAD_USE_DLL # endif # else # define BOOST_THREAD_USE_LIB # endif #endif

2 1

Re: [Boost-users] Multi-Index compound key synthesis via MPL
by Joaquín Mª López Muñoz 24 Jan '06

24 Jan '06

[Luke, this message from you shows up at Google Groups frontend, but somehow it hasn't really made it to the users list. Responding to the list in the hope that at least this answer gets properly processed.] Luke Meyers ha escrito: > The indexed_by construct for a multi_index_container can be replaced by > an mpl::vector, so that the list can be synthesized. I would like to > do the same thing with compound_key, to synthesize such a key based on > a list of types. Can I do this? Alas there's no version of composite_key accepting an MPL sequence instead of the direct enumeration of the constituent key extractors. But with a little MPL and preprocessor stuff, however, you can do what you want, see the attached snippet. HTH, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

[Boost][Bind] How to bind template function member
by Marc Viala 24 Jan '06

24 Jan '06

Hi, I would like to know how I can use boost::bind with template function member? To explain my problem, you will find hereafter an example code that demonstrates it. In this code, when we try to bind the function member X::g the compiler failed with tons of error message. Am I doing something wrong? Best regards, Marc Viala mailto:mviala@acticm.com ----------------------------------- Platform: VC++ 7.1 Boost 1.33.1 ----------------------------------- #include <boost/bind.hpp> #include <boost/function.hpp> struct X { template<typename A, typename B> void g(A& a, B& b) { std::cout << a << " " < void e(A& a, B& b) { std::cout << a << " " < pe = boost::bind(&e<int,int>, a, b) ; // <- OK pe() ; boost::function<void (void)> pg = boost::bind(&X::g<int,int>, &x, a, b) ; // <- Don't compile? pg() ; boost::function<void (void)> pf = boost::bind(&X::f, &x, a) ; // <- OK pf() ; }

3 4

beginners problems linking serialization library
by Michael Shapiro 24 Jan '06

24 Jan '06

I am having problems linking a program using the serialization library. I have made a small program, considerably simpler than the demo.cpp listed at http://www.boost.org/libs/serialization/doc/tutorial.html and I have also tried linking demo.cpp itself. My hpp files are in /home/mshapiro.local/boost/include/boost-1_32/boost/ My libraries are in /home/mshapiro.local/boost/lib/ I have tried linking this code with gcc 3.4.5 on a linux machine using gcc -I/home/mshapiro.local/boost/include/boost-1_32/ \ -L/home/mshapiro.local/boost/lib/ \ -lboost_serialization-gcc \ demo.cpp I have tried many variations on this! (For example, I have tried g++ instead of gcc, I have tried all variations on the serialization library, such as boost_serialization-gcc-d-1_32, etc, I have tried turning off warnings as suggested in the compiler specific issues.) I can compile using the -c flag, but I cannot link it. I get a large number of error messages all of which look much like /tmp/ccuSnkzu.o(.gnu.linkonce.t._ZN5boost7archive18text_oarchive_implINS0_13text_oarchiveEED1Ev+0x51): In function `boost::archive::text_oarchive_impl<boost::archive::text_oarchive>::~text_oarchive_impl()': : undefined reference to `boost::archive::basic_text_oprimitive<std::basic_ostream<char, std::char_traits<char> > >::~basic_text_oprimitive()' I can find various references to this exact problem in the newsgroups, but can find no solution to it. Your help would be greatly appreciated. Many thanks in advance, Michael Shapiro

4 4

Re: [Boost-users] [tuple] no easy access to get function
by JOAQUIN LOPEZ MU?Z 23 Jan '06

23 Jan '06

----- Mensaje original ----- De: François Duranleau <duranlef(a)iro.umontreal.ca> Fecha: Domingo, Enero 22, 2006 6:08 am Asunto: Re: [Boost-users] [tuple] no easy access to get function > On Sat, 21 Jan 2006, JOAQUIN LOPEZ MU?Z wrote: > > > ----- Mensaje original ----- > > De: Frank Birbacher <bloodymir.crap(a)gmx.net> > > Fecha: Sábado, Enero 21, 2006 2:29 am > > Asunto: [Boost-users] [tuple] no easy access to get function > > > >> Today I wanted to std::transform a range of tuples into a > sequence of > >> one element. I thought I could just take the address of some > >> tuple::get<N> function. Maybe also specify the Tuple type as > template>> parameter [...] > >> I'd rather want to take the address of boost::tuple::get<N,Tuple>, > >> but the template parameters won't match. > > > > Maybe you forgot the final s in "tuples" when > > writing > > > > boost::tuples::get<N,Tuple> > > There is a thin wrapper declared in the boost namespace as well. > The > probleme is elsewhere. The argument to the get function is not a > boost::tuple<>, but some base class template. Thus the template > arguments > of the function are not and an integer and a tuple, but an integer > and > something else (actually, a cons<HT,TT> if you look in the code). > To take > the address of such a function, you need to bind the integer, as > well as > HT and TT, not a tuple. Yep, I see. You're right. Well, you can refer to get<> as follows boost::tuples::get<N,typename Tuple::inherited> Note that this is not relying on undocumented implementation, so called "const lists" are explained and made public at http://boost.org/libs/tuple/doc/tuple_advanced_interface.html So I'd say you can use the former reference to get safely. > > However, I am wondering if there would be a problem to declare the > thin > wrapper simply like this (example with the const version): > > template< int N , > typename Tuple > > inline > typename tuples::access_traits< > typename tuples::element< N , Tuples >::type > >::const_type > get( const Tuple& t ) > { > return tuples::get< N >( c ) ; > } > > ? That would also work, but my proposal above is simpler. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

3 2

BUG: example boost_file_dependencies.cpp does not compile.
by Robert McCullough 23 Jan '06

23 Jan '06

Hi, I have tried to compile the example boost_file_dependencies.cpp using version 1.33.1 under Linux (gcc) and Windows XP (VC 7.1) and get the same errors. It does not like the following call to dijkstra_shortest_paths_no_init(). If I commit this function out it compiles fine. Any ideas on how to fix this? // Run best-first-search from each vertex with zero in-degree. for (tie(i, iend) = vertices(g); i != iend; ++i) { if (in_degree[*i] == 0) { std::vector<graph_traits<Graph>::vertex_descriptor> pred(num_vertices(g)); property_map<Graph, vertex_index_t>::type indexmap = get(vertex_index, g); dijkstra_shortest_paths_no_init (g, *i, &pred[0], &time[0], weight, indexmap, compare, combine, 0, // Since we are using > instead of >, we (std::numeric_limits<int>::max)(), // flip 0 and inf. default_dijkstra_visitor()); } } List of some of the output. Compiling... boost_file_dependencies.cpp c:\Boost\include\boost-1_33_1\boost\property_map.hpp(25) : error C2039: 'key_type' : is not a member of 'boost::dijkstra_visitor<>' c:\Boost\include\boost-1_33_1\boost\graph\breadth_first_search.hpp(61) : see reference to class template instantiation 'boost::property_traits<PA>' being compiled with [ PA=boost::dijkstra_visitor<> ] c:\Boost\include\boost-1_33_1\boost\graph\dijkstra_shortest_paths.hpp(207) : see reference to function template instantiation 'void boost::breadth_first_visit<VertexListGraph,MutableQueue,boost::detail::dijks tra_bfs_visitor<UniformCostVisitor,UpdatableQueue,WeightMap,PredecessorMap,D istanceMap,BinaryFunction,BinaryPredicate>,ColorMap>(const IncidenceGraph &,boost::graph_traits<G>::vertex_descriptor,Buffer &,BFSVisitor,ColorMap)' being compiled with [ VertexListGraph=Graph, UniformCostVisitor=std::numeric_limits<int>::_Ty, UpdatableQueue=MutableQueue, WeightMap=boost::property_map<Graph,boost::edge_weight_t>::type, PredecessorMap=__w64 unsigned int *__w64 , DistanceMap=int *__w64 , BinaryFunction=boost::closed_plus<int>, BinaryPredicate=std::greater<int>, ColorMap=boost::dijkstra_visitor<>, IncidenceGraph=Graph, G=Graph, Buffer=MutableQueue, BFSVisitor=boost::detail::dijkstra_bfs_visitor<std::numeric_limits<int>::_Ty ,MutableQueue,boost::property_map<Graph,boost::edge_weight_t>::type,__w64 unsigned int *__w64 ,int *__w64 ,boost::closed_plus<int>,std::greater<int>> ] c:\Visual Studio Projects\boost_file_dependencies\boost_file_dependencies\boost_file_dependen cies.cpp(178) : see reference to function template instantiation 'void boost::dijkstra_shortest_paths_no_init<Graph,std::numeric_limits<int>::_Ty,s td::allocator<_Ty>::value_type*__w64 ,std::allocator<int>::value_type*__w64 ,boost::property_map<Graph,Property>::type,boost::property_map<Graph,boost:: vertex_index_t>::type,std::greater<int>,boost::closed_plus<T>,int,boost::dij kstra_visitor<>>(const VertexListGraph &,boost::graph_traits<G>::vertex_descriptor,PredecessorMap,DistanceMap,Weigh tMap,IndexMap,Compare,Combine,DistZero,DijkstraVisitor,ColorMap)' being compiled with [ _Ty=Vertex, Graph=Graph, Property=boost::edge_weight_t, T=int, VertexListGraph=Graph, G=Graph, PredecessorMap=std::allocator<Vertex>::value_type *__w64 , DistanceMap=std::allocator<int>::value_type *__w64 , WeightMap=boost::property_map<Graph,boost::edge_weight_t>::type, IndexMap=boost::property_map<Graph,boost::vertex_index_t>::type, Compare=std::greater<int>, Combine=boost::closed_plus<int>, DistZero=int, DijkstraVisitor=std::numeric_limits<int>::_Ty, ColorMap=boost::dijkstra_visitor<> ] c:\Boost\include\boost-1_33_1\boost\property_map.hpp(25) : error C2146: syntax error : missing ';' before identifier 'key_type' c:\Boost\include\boost-1_33_1\boost\property_map.hpp(26) : error C2039: 'value_type' : is not a member of 'boost::dijkstra_visitor<>' c:\Boost\include\boost-1_33_1\boost\property_map.hpp(26) : error C2146: syntax error : missing ';' before identifier 'value_type' c:\Boost\include\boost-1_33_1\boost\property_map.hpp(27) : error C2039: 'reference' : is not a member of 'boost::dijkstra_visitor<>' c:\Boost\include\boost-1_33_1\boost\property_map.hpp(27) Best regards, Robert McCullough ------------------------------ Software Engineer Promess Incorporated 11429 E. Grand River Brighton, MI. 48116 Phone: 810-229-9334 Fax: 810-229-8125 Email: rob(a)promessdev.com URL: www.promessinc.com <http://www.promessinc.com/> "Get your facts first and then you can distort them as much as you wish." --- Mark Twain

2 1

trouble building bgl-viz
by VP of Communciations 23 Jan '06

23 Jan '06

I have successfully installed boost with VC express (windows), but am having trouble getting the DOT reader going. I don't seem to have the bgl-viz library. I have followed the directions on the "getting started" page and the read_graphviz page, but I must be doing something wrong, because I am not getting the bgl-viz library. I'm new to boost and C++, so please forgive me if these are elementary questions. How do I build the bgl-viz library? Thanks.

2 1

graph compile error with gcc3.3 when edge container is slist
by Weiqing Guo 23 Jan '06

23 Jan '06

Hi, the attached source code is copied from boost_1_33_0/libs/graph/example/adjacency_list.cpp, I only changed the edge container to be slist, and include <slist.h> I compiled it on linux with AMD opteron 844 processor. gcc2.95.3 works fine, but gcc3.3 doesn't compile. I think the reason is slist is not in std namespace in gcc3.3, and adjacency_list.hpp doesn't handle this correctly for slist. > grep BOOST_STD_EXTENSION_NAMESPACE adjacency_list.hpp adjacency_list.hpp: typedef BOOST_STD_EXTENSION_NAMESPACE::slist<ValueType> type; adjacency_list.hpp: typedef BOOST_STD_EXTENSION_NAMESPACE::hash_set<ValueType> type; adjacency_list.hpp: typedef BOOST_STD_EXTENSION_NAMESPACE::hash_set<ValueType> type; adjacency_list.hpp: struct bind_ { typedef BOOST_STD_EXTENSION_NAMESPACE::hash_set<T, std::less<T> > type; }; adjacency_list.hpp: struct bind_ { typedef BOOST_STD_EXTENSION_NAMESPACE::hash_set<T, std::less<T> > type; }; should slist be handled the same way as hash_set ? thanks weiqing //======================================================================= // Copyright 1997, 1998, 1999, 2000 University of Notre Dame. // Authors: Andrew Lumsdaine, Lie-Quan Lee, Jeremy G. Siek // // Distributed under the Boost Software License, Version 1.0. (See // accompanying file LICENSE_1_0.txt or copy at // http://www.boost.org/LICENSE_1_0.txt) //======================================================================= #include <boost/config.hpp> #include <iostream> #include <vector> #include <slist.h> #include <utility> #include <string> #include <boost/graph/adjacency_list.hpp> #include <boost/graph/graph_utility.hpp> #include <boost/property_map.hpp> /* Sample Output graph name: foo 0 --joe--> 1 1 --joe--> 0 --curly--> 2 --dick--> 3 2 --curly--> 1 --tom--> 4 3 --dick--> 1 --harry--> 4 4 --tom--> 2 --harry--> 3 (0,1) (1,2) (1,3) (2,4) (3,4) removing edge (1,3): 0 --joe--> 1 1 --joe--> 0 --curly--> 2 2 --curly--> 1 --tom--> 4 3 --harry--> 4 4 --tom--> 2 --harry--> 3 (0,1) (1,2) (2,4) (3,4) */ struct EdgeProperties { EdgeProperties(const std::string& n) : name(n) { } std::string name; }; struct VertexProperties { std::size_t index; boost::default_color_type color; }; int main(int , char* []) { using namespace boost; using namespace std; typedef adjacency_list<slistS, listS, undirectedS, VertexProperties, EdgeProperties> Graph; const int V = 5; Graph g(V); property_map<Graph, std::size_t VertexProperties::*>::type id = get(&VertexProperties::index, g); property_map<Graph, std::string EdgeProperties::*>::type name = get(&EdgeProperties::name, g); boost::graph_traits<Graph>::vertex_iterator vi, viend; int vnum = 0; for (boost::tie(vi,viend) = vertices(g); vi != viend; ++vi) id[*vi] = vnum++; add_edge(vertex(0, g), vertex(1, g), EdgeProperties("joe"), g); add_edge(vertex(1, g), vertex(2, g), EdgeProperties("curly"), g); add_edge(vertex(1, g), vertex(3, g), EdgeProperties("dick"), g); add_edge(vertex(2, g), vertex(4, g), EdgeProperties("tom"), g); add_edge(vertex(3, g), vertex(4, g), EdgeProperties("harry"), g); graph_traits<Graph>::vertex_iterator i, end; graph_traits<Graph>::out_edge_iterator ei, edge_end; for (boost::tie(i,end) = vertices(g); i != end; ++i) { cout << id[*i] << " "; for (boost::tie(ei,edge_end) = out_edges(*i, g); ei != edge_end; ++ei) cout << " --" << name[*ei] << "--> " << id[target(*ei, g)] << " "; cout << endl; } print_edges(g, id); cout << endl << "removing edge (1,3): " << endl; remove_edge(vertex(1, g), vertex(3, g), g); ei = out_edges(vertex(1, g), g).first; cout << "removing edge (" << id[source(*ei, g)] << "," << id[target(*ei, g)] << ")" << endl; remove_edge(ei, g); for(boost::tie(i,end) = vertices(g); i != end; ++i) { cout << id[*i] << " "; for (boost::tie(ei,edge_end) = out_edges(*i, g); ei != edge_end; ++ei) cout << " --" << name[*ei] << "--> " << id[target(*ei, g)] << " "; cout << endl; } print_edges(g, id); return 0; }

2 1

Signature of files saved by boost::serialization
by Bo Peng 23 Jan '06

23 Jan '06

Dear list, What would be a good way to tell if a file is saved by boost::serialization? I notice that the first several characters of binary_oarchive saved files are "\026 \0 \0 \0 \0 \0 \0 serialization" and are "22 serialization" for text_oarchive saved files. Are they reliable signatures? Many thanks in advance. Bo

2 3

Boost Graph library
by Olga Gerchikov 23 Jan '06

23 Jan '06

Hi, Does anyone know if there is a Java port of Boost Graph library? Thank you.

2 1

Boost Graph: problems using add_edge()
by João Orvalho 23 Jan '06

23 Jan '06

Hi, I am using boost 1.33.1 with Visual C++ 2002 (v 7.0.9466) and Windows XP (no service pack). I was doing some experiments with boost Graph library . When running the program i get the following error on add_edge(): ---------------------------------------------------------------------- An unhandled exception of type 'System.TypeLoadException' occurred in test.exe Additional information: Could not load type std._Ptrit<boost::detail::adj_list_gen<boost::adjacency_list<boost::vecS,boost::vecS,boost::bidirectionalS,boost::no_property,boost::no_property,boost::no_property,boost::listS>,boost::vecS,boost::vecS,boost::bidirectionalS,boost::no_property,boost::no_property,boost::no_property,boost::listS>::config::stored_vertex,int,boost::detail::adj_list_gen<boost::adjacency_list<boost::vecS,boost::vecS,boost::bidirectionalS,boost::no_property,boost::no_property,boost::no_property,boost::listS>,boost::vecS,boost::vecS,boost::bidirectionalS,boost::no_property,boost::no_property,boost::no_property,boost::listS>::config::stored_vertex *,boost::detail::adj_list_gen<boost::adjacency_list<boost::vecS,boost::vecS,boost::bidirectionalS,boost::no_property,boost::no_property,boost::no_property,boost::listS>,boost::vecS,boost::vecS,boost::bidirectionalS,boost::no_property,boost::no_property,boost::no_property,boost::listS>::config::stored_vertex &,boost::detail::adj_list_gen<boost::adjacency_list<boost::vecS,boost::vecS,bo0a748880 from assembly test, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null. ---------------------------------------------------------------------- The program is: ---------------------------------------------------------------------- #include <iostream> // for std::cout #include <utility> // for std::pair #include <algorithm> // for std::for_each #include <boost/graph/graph_traits.hpp> #include <boost/graph/adjacency_list.hpp> #include <boost/graph/dijkstra_shortest_paths.hpp> using namespace boost; int main(int,char*[]) { // create a typedef for the Graph type typedef adjacency_list<vecS, vecS, bidirectionalS> Graph; // Make convenient labels for the vertices enum { A, B, C, D, E, N }; const int num_vertices = N; const char* name = "ABCDE"; // writing out the edges in the graph typedef std::pair<int, int> Edge; Edge edge_array[] = { Edge(A,B), Edge(A,D), Edge(C,A), Edge(D,C), Edge(C,E), Edge(B,D), Edge(D,E) }; const int num_edges = sizeof(edge_array)/sizeof(edge_array[0]); // declare a graph object Graph g(num_vertices); // add the edges to the graph object for (int i = 0; i < num_edges; ++i) { add_edge(edge_array[i].first, edge_array[i].second, g); } //// get the property map for vertex indices typedef property_map<Graph, vertex_index_t>::type IndexMap; IndexMap index = get(vertex_index, g); std::cout << "vertices(g) = "; typedef graph_traits<Graph>::vertex_iterator vertex_iter; std::pair<vertex_iter, vertex_iter> vp; for (vp = vertices(g); vp.first != vp.second; ++vp.first) std::cout << index[*vp.first] << " "; std::cout << std::endl; float finish; std::cin >> finish; return 0; } ---------------------------------------------------------------------- Thanks, João Orvalho

2 1

Weird cross compiling issue
by James Hughes 23 Jan '06

23 Jan '06

Hello all, I am cross compiling Boost to an embedded Linux Arm architecture. I reported a problem a week or so ago with failures in some of the libraries which I was unable to solve, and have a bit more information. One of the issues appears with the serialisation library. Although I am compiling for Arm, the serialisation libs end up as Intel X86 binaries, even though all the other successfully compiled libs are ARM. This then leads to problems elsewhere with libraries that appear to need the serialisation libs. I can only think that there is an issue with the make system to do with serialisation area. Anyone have any comments/thoughts? In addition, when I do a build to a particular directory: bjam "-sGCC_ROOT_DIRECTORY=/opt/montavista/mobilinux/devkit/arm/iwmmxt_le" "-sGCC=iwmmxt_le-gcc" "-sGXX=iwmmxt_le-g++" stage the stage folder is created, in which is a lib folder, in which are all the binaries (including the defective Intel ones). However, I would also expect some header files somewhere - should there also be a h (or header) folder next to lib? If not where are the headers I need to include in my apps using Boost? James Info : Boost 1.33.1. gcc : 3.4.3 (iwmmxt_le-gcc)

2 1

Version Mgmt classes/algorithms
by Rich Johnson 23 Jan '06

23 Jan '06

Today 09:06:47 am Hi folks-- I'm looking for a peer-reviewed solutions for managing versions (dll compatibiity, data formats, etc.). If they exist, they're pretty hard to find. ( FWIW, searches with the terms "version" or "versioning" aren't very helpful :-() To date all I've been able to find are ad hoc discussions on matching a specific version. Ultimately, I _think_ I'm looking for 1) a base class for a version specification 2) a range for version compatibility 3)a mixin class (with compatibility check methods) for objects requiring version compatibility. The two use cases I have in mind are: 1) - an application wishes to verify compatibility of a dlopen()'d module as well as the compatibility of its separately compiled objects. 2) - a decoder wishes to verify compatibility with a data file being decoded. Have there been any discussions on this topic in the boost domain? If so, how would I find it? Any one have ideas where else I could look? Or any useful codewords to search for. Thnx --rich

1 0