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

Boost License Question
by Glenn Thorne 03 Mar '06

03 Mar '06

I want to use several of the Boost libraries in a project I'm working on and am a little concerned over a potential conflict between the website information and the Boost license language. On the website it mentions that the license is "not viral" but the language in the Boost license states that ".. and to permit third-parties to whom the Software is furnished to do so, all subject to the following: The copyright notices in the Software and this entire statement, including the above license grant, this restriction and the following disclaimer, must be included in all copies of the Software, in whole or in part, and all derivative works of the Software, unless such copies or derivative works are solely in the form of machine-executable object code generated by a source language processor." It seems to me that since derivative works must be subject to the license, any code I link with the Boost libraries would also be subject to the Boost license. Am I reading this correctly or is there a different interpretation? Thanks! Glenn

3 3

Re: [Boost-users] serialization: again a problem, failing to serializea std::vector of pointers
by RIVASSEAU Jean Noel 03 Mar '06

03 Mar '06

Hello Jean-Noël, maybe you can try using the proposed patch at http://lists.boost.org/Archives/boost/2006/02/101539.php and report your results. I've got the hunch your problem might be related to the issue dealt with at that post. At this url, I have found two hpp files. I replaced the ones that originally came with the Boost 1.3.1 distribution with these ones. I still have an error, at the same line, however it is: C:/Boost/include/boost-1_33_1/boost/archive/detail/iserializer.hpp:115: error: no type named `type' in `struct boost::serialization::type_info_implementation<std::vector<MemberVariableSpecification*, std::allocator<MemberVariableSpecification*> > >' C:/Boost/include/boost-1_33_1/boost/archive/detail/iserializer.hpp:115: error: `get_instance' is not a member of `<declaration error>' While it was: C:/Boost/include/boost-1_33_1/boost/archive/detail/iserializer.hpp:115: error: incomplete type `boost::serialization::extended_type_info_null<std::vector<MemberVariableSpecification*, std::allocator<MemberVariableSpecification*> > >' used in nested name specifier with the original code from Boost 1.33.1. So this patch effectively changed something, but it still not working. I've not read the entire thread at your url since I did not understand it (it was about a specific compiler issue ??). Any ideas? Jean-Noël

1 0

Assigning smart/shared_ptr pointer to C struct
by adharankar＠verizon.net 03 Mar '06

03 Mar '06

Greetings... What is wrong in assigning a smart/shared_ptr pointer in C++ code to a struct which may then be passed to a C code? Consider the sample source towards the end of this email. When I run this through valgrind (memory debugger, see http://www.valgrind.org) it points out potential problem (also listed after the sample code). It also seems to cause memory corruption. What may be a better way of saving/storing a smart/shared_ptr pointer in a C struct (and yet have the reference counter in the smart/shared_ptr pointer increment)? Best regards, -Arun. --------------------- The sample program -------------------- #include <boost/shared_ptr.hpp> class A { public: int val; }; typedef boost::shared_ptr<A> APtr; struct S { public: APtr aptr; }; struct S *func(void) { A *a = new A; a->val = 12; APtr aptr(a); struct S *s = (struct S *)malloc(sizeof(struct S)); s->aptr = aptr; return s; } int main(int ac, char *av[]) { struct S *s; s = func(); APtr aptr = s->aptr; } ------------------------------------------------------ Output from valgrind: Conditional jump or move depends on uninitialised value(s) at 0x8048A20: boost::detail::shared_count::operator= (boost::detail::shared_count const&) (shared_count.hpp:179) by 0x80487FD: boost::shared_ptr<A>::operator= (boost::shared_ptr<A> const&) (shared_ptr.hpp:148) by 0x80486E8: func() (c.cpp:22) by 0x8048742: main (c.cpp:30)

4 3

Re: [Boost-users] is_polymorphic addition please
by Ray Hilton 03 Mar '06

03 Mar '06

>I'm not entirely sure what you mean here: do you mean "if class X is only >polymorphic because of base class Y, then don't count X as polymorphic"? >If so then I don't see any way to implement that, anyone else? >John. Yes, that is what i meant. A lot of stuff that is inherited will never be used polymorphically, like boost::noncopyable, binary_funciton<> type classes that only bring in typedefs etc. It would we be of great help im sure. Anyway, sorry for hijacking a thread. Ray Hilton, _________________________________________________________________ Dont just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/

3 2

Re: [Boost-users] serialization: again a problem, failing to serializea std::vector of pointers
by Joaquín Mª López Muñoz 03 Mar '06

03 Mar '06

RIVASSEAU Jean Noel ha escrito: > Sorry, I removed the QString stuff, so it should make more sense to you now. I have attached the cleaned up code. If you try to compile it, it will fail on the file > > ClassSpecification_serialization.cc > > with a message saying that there is a problem with the extended_type_info of std::vector< MemberVariableSpecification *> (since a member of ClassSpecification, which I serialize, is of this type). > > Don't pay attention as to what are my real intentions on this example code, this comes from my real project, and it would be long to explain. Just let's say that, no, I am not trying to store class id information into the archive, it is just that one data member of one of object that I need to serialize has the name class_id (but it could be named "walnut_field", the code would be the same). > > This small example code is just there to show you the bug that occurs. > > As for the mixing of type systems (no_rtti and type_id), it was just a test to see if that would change things. I have reverted it back in the attached code (only no_rtti used) but it still does not work. > Jean-Noël, maybe you can try using the proposed patch at http://lists.boost.org/Archives/boost/2006/02/101539.php and report your results. I've got the hunch your problem might be related to the issue dealt with at that post. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

Can I use STL transform and lambda to add 2 int vector?
by Meryl Silverburgh 03 Mar '06

03 Mar '06

Hi, I would like to know if I can use transform and lambda to add 2 int vector and save the result into a third int vector vector<int> src1; vector<int> src2; vector<int> result // put the value of src1 and src2

4 4

New User With Busted Compiler
by V. Thane Norton III 03 Mar '06

03 Mar '06

I have just started using Boost, and am really enjoying using it, especially uBLAS. Unfortunately, my production code needs to use GCC 3.3 (for marketing reasons) which the Boost 1.33.1 uBLAS does not support. What is the latest version of Boost that I can use for uBLAS on GCC 3.3? Is there some hackery that I can perform to get 1.33.1 working? ----------------------------------------- V. Thane Norton III Macintosh Software Engineer Wacom Technology Corporation phone: 360.896.9833 x172 mailto:tnorton@wacom.com

1 0

Re: [Boost-users] [multi_index] Trouble using MultiIndex with VisualStudio 2005
by JOAQUIN LOPEZ MU?Z 02 Mar '06

02 Mar '06

----- Mensaje original ----- De: Andrew Holden <aholden(a)charteroaksystems.com> Fecha: Jueves, Marzo 2, 2006 9:50 pm Asunto: [Boost-users] [multi_index] Trouble using MultiIndex with VisualStudio 2005 > I am trying to compile a program using MultiIndex from Boost 1.33.1 > using Visual Studio 2005 (MSVC8). So far, I can not get it to compile > with fewer than 100 errors. Does anyone know what I might be doing > wrong? > > I have attached the source file I am using to test, as well as the > output from my compiler. Hello Andrew, You have to add #include <boost/multi_index/ordered_index.hpp> so as to bring ordered indices in. Other than this, a visual inspection of your code does not reveal further problems, please let me know otherwise. If this is any consolation to you, you're not the first one stumbling into this problem, thus I've explicitly added the necessary #includes in the main snippets of the documentation for the next release, as can be seen for instance in the preview link: http://boost- consulting.com/boost/libs/multi_index/doc/tutorial/basics.html#multiple _sort Thanks for trying Boost.MultiIndex, 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

1 0

Questions about boost with a vector of pair
by yinglcs2＠yahoo.com 02 Mar '06

02 Mar '06

I am trying to write a function with takes a vector of pair and an key (integer). it should return true if the input key matches the FIRST value of the map. bool containsPair(vector< pair<int, int> >& aMap, int key ) { return ( find_if ( aMap.begin(), aMap.end(), bind( equal_to<int>(), boost::lambda::bind( &pair< int, int>::first_type::first, boost::lambda::_1) , key ) ) != aMap.end()); } But i cant' get the code to compile. I have this error: ../RowColumn1_4PatternMatcherHelper.h: In function bool containsPair(std::vector<std::pair<int, int>, std::allocator<std::pair<int, int> > >&, int): ../RowColumn1_4PatternMatcherHelper.h:62: error: struct std::pair<int, int>::first_type is not a class or namespace ../RowColumn1_4PatternMatcherHelper.h:62: error: first was not declared in this scope make: *** [TestDriver.o] Error 1 any help is appreciated. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

BGL connected_components for directed graphs
by Gavin Band 02 Mar '06

02 Mar '06

Dear boosters, I am trying to compile a program which is identical to the example http://www.boost.org/libs/graph/example/connected_components.cpp given in the docs, except that in the graph typedef I changed undirectedS to directedS. However, I get a compilation error: g++ -o test_c++.o -I/usr/include/boost -c test_c++.cpp /usr/include/boost/graph/connected_components.hpp: In function `typename boost::property_traits<IndexMap>::value_type boost::connected_components(const Graph&, ComponentMap) [with Graph = main(int, char**)::Graph, ComponentMap = int*]': test_c++.cpp:45: instantiated from here /usr/include/boost/graph/connected_components.hpp:87: error: incomplete type `boost::STATIC_ASSERTION_FAILURE< false>' used in nested name specifier /usr/include/boost/graph/connected_components.hpp:87: error: size of array has non-integral type `<type error>' Presumably this is some meta-program's way of telling me that my graph isn't undirected. Is there any way to make this work for an directed graph? (I am using gcc 3.4.4 and boost 1.33.0) Thanks, Gavin Band.

2 1

[multi_index] Trouble using MultiIndex with Visual Studio 2005
by Andrew Holden 02 Mar '06

02 Mar '06

I am trying to compile a program using MultiIndex from Boost 1.33.1 using Visual Studio 2005 (MSVC8). So far, I can not get it to compile with fewer than 100 errors. Does anyone know what I might be doing wrong? I have attached the source file I am using to test, as well as the output from my compiler. Andrew Holden Charter Oak Investment Systems, Inc.

1 0

FW: adjacency_list remove_edge
by Sean Kelly 02 Mar '06

02 Mar '06

Hi All, I have observed the following behavior using the remove_edge function and am curious if anyone else has seen this. remove_edge(edge_descriptor, graph) // occasionally fails in a seemingly indeterminant way remove_edge(source(edge_descriptor, graph), target(edge_descriptor, graph), graph) // works fine The adjacency list I am using is listS listS, and this is not an issue with invalid edge_iterators, i.e. I collect all the edge_descriptors to be removed before removing them. I can provide more detailed info upon request. thanks for any input Sean Kelly Sean Kelly Ph.D. Staff Software Engineer Xilinx Inc. ph: 720-652-3919 fax: 720-652-3434

2 1

Re: [Boost-users] Can't statically link demo program with Boost.Serialization 1.33
by Demos Rali 02 Mar '06

02 Mar '06

On Wed, 1 Mar 2006, Robert Ramey wrote: > I'm not an expert in gcc command line switches. But it seems odd > to me that you don't have to specify the full library name with the > -L switch. There are several verasions of the library built and I > don't see how the proper one can be select without explicitly > specifying it. gcc doesn't implemant autolink as far as I know. > I traced the linker (ld) and it autolinks against the dynamic libraries when I dont specify -static on the command line and against the static libraries (libboost_serialization.a) when I do specify -static, which is what I intended. If I specify the name of the library on the command line, as you suggest, this doesn't solve the problem (same results). Therefore, an incorrect library selection doesn't seem to be the problem by the linker. Thank you. > > Robert Ramey > > >> Hello, >> >> I am having difficulties statically compiling the demo program at >> http://www.boost.org/libs/serialization/example/demo.cpp >> on Linux (Linux 2.6.15-1.1831_FC4 #1 SMP Tue Feb 7 13:37:59 EST 2006 >> x86_64 GNU/Linux) with gcc version 4.0.2 20051125. >> [snip] >> Fabrizio

1 0

serialization: again a problem, failing to serialize a std::vector of pointers
by RIVASSEAU Jean Noel 02 Mar '06

02 Mar '06

Hello This is my last problem with the BSL but the most important one (because there is no workaround). I am trying to serialize a class (whose name is "ClassSpecification") which has a std::vector of pointers. The code for serializing the class the pointer refer to (MemberVariableSpecification) is written and instantiated correctly. However I cannot correctly serialize the std::vector. It fails with a message complaining about: C:/Boost/include/boost-1_33_1/boost/archive/detail/iserializer.hpp:115: error: incomplete type `boost::serialization::extended_type_info_null<std::vector<MemberVariableSpecification*, std::allocator<MemberVariableSpecification*> > >' used in nested name specifier I do not understand why I need an extended_type_info for this vector. I sure need it for the class the pointers refer to (and I did specify it), but the std::vector itself is serialized as such, not as a pointer. Why do I get this error ??? Can you please check the attached code and help me? Thanks Jean-Noël Ps: using gcc 3.4.2

2 2

[serialization] non-intrusive serialization problem
by Federico Feller 02 Mar '06

02 Mar '06

Hi. I have problems defining a non-instrusive serialization of a class. Ive defined the following functions: namespace boost { namespace serialization { template<class Archive> inline void save( Archive & ar, const CLITimeStamp & t, const unsigned int /* file_version */ ){ std::string aux = std::string(t.get14LengthRepresentation()); ar & aux; } template<class Archive> inline void load( Archive & ar, const CLITimeStamp & t, const unsigned int /* file_version */ ){ std::string aux; ar & aux; t = CLITimeStamp((char*)aux.c_str()); } template<class Archive> inline void serialize( Archive & ar, const CLITimeStamp & t, const unsigned int file_version ){ split_free(ar, t, file_version); } }} According to the doc Ive read, this is the way to declare that the class 'CLITimeStamp' can be serialized. Howerver, when I try to do this: template<class Archive> void load(Archive & ar, const unsigned int version){ ar & minDate }; where minDate is a CLITimeStamp pointer, i get the follwing error: <'serialize' is not a Member of CLITimeStamp> Any ideas of what i could be doing wrong? Thanks Federico __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

Boost can't build with Intel C++ Compiler 9.0
by Yoshihiro ISHIKAWA 02 Mar '06

02 Mar '06

Hello everyone I could not build all boost-1.33.1 libraries using Intel C++ Compiler 9.0.0.32. I tried following steps. # export INTEL_PATH=/opt/intel/cc/9.0 # export INTEL_CXX="icpc -cxxlib-icc" # ./configure --with-toolset=intel-linux # make My environment Fedora Core 4 i386 Intel C++ Compiler version 9.0.0.32 Boost version 1.33.1 How can I build all libraries ? Please Help. Yoshihiro Ishikawa

2 1

newbie question
by Lucio Flores 02 Mar '06

02 Mar '06

Just trying to use mpl::transform on a vector of int's and I can't seem to get it working properly. Can anyone see what's wrong?? I'm trying to perform vector_c<int, 1, 2, 3> + vector_c<int, 1, 1, 1> = vector_c<int, 2, 3 ,4> The is_same function always returns false when I compile and run it. ------------------- typedef mpl::vector_c<int, 1, 2, 3> type_a; typedef mpl::vector_c<int, 1, 1, 1> type_b; struct plus_f { template<class A, class B> struct apply { typedef typename mpl::plus<A, B>::type type; }; }; typedef mpl::transform<type_a, type_b, plus_f >::type result_type; std::cerr << "True " << boost::is_same<result_type, mpl::vector_c<int, 2, 3, 4> >::value << std::endl; __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

13 55

Re: [Boost-users] Boost can't build with Intel C++ Compiler 9.0
by Ormond, Randy (Mission Systems) 02 Mar '06

02 Mar '06

I'm in the middle of building on an Altix (Itanium, Linux) with Intel 9.0 also. Still checking but this looks like it's working for me: bjam -sTOOLS=intel-linux "-sINTEL_CC=icc -cxxlib-icc" -sINTEL_PATH=/opt/intel/cc/9.0 But I guess you have a reason for not wanting to use bjam. Hope this helps. Randy Ormond -----Original Message----- From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Yoshihiro ISHIKAWA Sent: Thursday, March 02, 2006 5:56 AM To: boost-users(a)lists.boost.org Subject: [Boost-users] Boost can't build with Intel C++ Compiler 9.0 Hello everyone I could not build all boost-1.33.1 libraries using Intel C++ Compiler 9.0.0.32. I tried following steps. # export INTEL_PATH=/opt/intel/cc/9.0 # export INTEL_CXX="icpc -cxxlib-icc" # ./configure --with-toolset=intel-linux # make My environment Fedora Core 4 i386 Intel C++ Compiler version 9.0.0.32 Boost version 1.33.1 How can I build all libraries ? Please Help. Yoshihiro Ishikawa _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Re: [Boost-users] Using multiple versions/targets of Boost
by Staal, J.J. (Joes) 02 Mar '06

02 Mar '06

> > It should... Did you use "-sTOOLS=vc-8_0" both times? As that's what > > it uses to determine the "vc80" tag. I had a similar problem, until I found out that I made an error. I used -"sTOOLS=vc-8_0" instead of "-sTOOLS=vc-8_0" (notice the location of the first minus sign). Joes. This e-mail and its contents are subject to the DISCLAIMER at http://www.tno.nl/disclaimer/email.html

2 1

Using multiple versions/targets of Boost
by Mateusz Łoskot 02 Mar '06

02 Mar '06

Hi, I have VC++ 7.1 and VC++ 8.0 installed on my laptop. I'd like to use Boost with both VC++. So, as I understand I need to build Boost twice, with VC++ 7.1 and with VC++ 8.0. Documentation does not say anything about such case. Now, the question is, should I install both targets to separate directories (different --prefix, e.g. C:\Boost-vc-8.0 and C:\Boost-vc-7.1) or can I install then in common dir C:\Boost ? AFAIK, libs names include toolset name e.g. libboost_date_time-vc71-mt-gdp.lib ^^^^^ So, I suppose I can install both targets into common place and I'll have following files in C:\Boost\lib: libboost_date_time-vc71-mt-gdp.lib and libboost_date_time-vc80-mt-gdp.lib Are my assumptions correct? Or it's more recommended to install separate targets (builds made with different toolsets) to separate folders? Thanks in advance Best regards -- Mateusz Łoskot http://mateusz.loskot.net

4 6

Re: [Boost-users] Serialization: docs regarding abstract base class
by RIVASSEAU Jean Noel 02 Mar '06

02 Mar '06

Since the demo doesn't use BOOST_EXPORT, I suspect that that there is some sort of problem related to instantiation of abstract base class code for exported types. I'lll look into it. If you can look into it, thank you, Robert. I have finished the organization of my (big) project serialization into separate files for each class, and now everything is working fine ! :) However, I still have the problem that every time I use a std::vector of pointers, and serialize it as such, there is a compile time error, since extended_type_info for the std::vector is not defined. This is a bug since type info should not matter here. My workaround was to use a BOOST_CLASS_TYPE_INFO(std::vector< ClassPointedTo *>, extended_type_info_no_rtti< std::vector< ClassPointedTo *> >) everytime such a vector occurs. However, if you can look into this problem and fix it, Robert, this would appreciated. I could then remove my workaround code, which makes my code ugly :) Jean-Noël -----Message d'origine----- De : boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] De la part de Robert Ramey Envoyé : jeudi 2 mars 2006 03:49 À : boost-users(a)lists.boost.org Objet : Re: [Boost-users] Serialization: docs regarding abstract base class Note that the tutorial programs do use BOOST_IS_ABSTRACT so I've always assumed that it functions as advertised. Since the demo doesn't use BOOST_EXPORT, I suspect that that there is some sort of problem related to instantiation of abstract base class code for exported types. I'lll look into it. Robert Ramey "RIVASSEAU Jean Noel" <JN.RIVASSEAU(a)oberthurcs.com> wrote in message news:87F60F7FA02FF749AFB02BD9FCAA6B04DE1BE3@naserv31.nanterre.oberthurcs.com... I quote the Boost serialization docs: When serializing an object through a pointer to its base class and that base class is abstract (i.e. has at least one virtual function assigned a value of 0), A compile error will be emitted. This is addressable in one over several ways: remove the =0 in the base classes so that the base class is no longer abstract. implement is_abstract for your compiler. (code written according to the C++ standard is included with this library. But it is known to fail on several compilers. If the compiler suports "is_abstract" type trait - use that. Otherwise assume a class is NOT abstract unless BOOST_IS_ABSTRACT has been set for the class. use the macro BOOST_IS_ABSTRACT(my_class) to indicate that the class is an abstract base class. This will cause the compiler to avoid generating code that causes this error. I still do not understand part 2 of this advice, Robert. Could you explain? Jean-Noël Ps: as already mentioned, part 3 does not change anything for me, and I'd like to avoid the solution of part 1 since I do want the base class to be abstract. _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Can't statically link demo program with Boost.Serialization 1.33
by Demos Rali 02 Mar '06

02 Mar '06

Hello, I am having difficulties statically compiling the demo program at http://www.boost.org/libs/serialization/example/demo.cpp on Linux (Linux 2.6.15-1.1831_FC4 #1 SMP Tue Feb 7 13:37:59 EST 2006 x86_64 GNU/Linux) with gcc version 4.0.2 20051125. When I try: g++ -o demo -I /path/boost/ -L /path/boost/ -lboost_serialization demo.cpp it works fine, but I get a program which needs dynamic versions of the serialization library. However, I would like to compile against the static versions of the Boost.Serialization library. If I try g++ -static -o demo -I /path/boost/ -L /path/boost/ -lboost_serialization demo.cpp the linker complains of a lot of undefined references, like /tmp/ccFAJsqB.o(.gnu.linkonce.r._ZTIN5boost13serialization16void_cast_detail21void_caster_primitiveIK20bus_stop_destinationK8bus_stopEE[typeinfo for boost::serialization::void_cast_detail::void_caster_primitive<bus_stop_destination const, bus_stop const>]+0x10): undefined reference to `typeinfo for boost::serialization::void_cast_detail::void_caster' ... I have no difficulties when statically linking against other boost libraries. I built the librairies with gcc, with no exotic options. Any suggestions would be greatly appreciated. Thanks a lot. Fabrizio

2 1

Serialization: docs regarding abstract base class
by RIVASSEAU Jean Noel 02 Mar '06

02 Mar '06

I quote the Boost serialization docs: When serializing an object through a pointer to its base class and that base class is abstract (i.e. has at least one virtual function assigned a value of 0), A compile error will be emitted. This is addressable in one over several ways: * remove the =0 in the base classes so that the base class is no longer abstract. * implement is_abstract for your compiler. (code written according to the C++ standard is included with this library. But it is known to fail on several compilers. * use the macro BOOST_IS_ABSTRACT(my_class) to indicate that the class is an abstract base class. This will cause the compiler to avoid generating code that causes this error. I still do not understand part 2 of this advice, Robert. Could you explain? Jean-Noël Ps: as already mentioned, part 3 does not change anything for me, and I'd like to avoid the solution of part 1 since I do want the base class to be abstract.

3 2

Re: [Boost-users] Boost thread questions
by Merrill Cornish 01 Mar '06

01 Mar '06

Hector, >>> how to lock a file (fstream) for reading/writing Are you trying to lock the _file_ on disk for all applications running on the system? Or, are you trying to lock a stream opened to that file for different threads in your application? In the first case, you need to use an OS-level lock, not Boost. In the second case, use a mutex as someone else suggested. Merrill

1 0

[statechart] Template States, Compile Error
by David Greene 01 Mar '06

01 Mar '06

The attached testcase doesn't compile with g++ 4.0.2 or g++ 3.2.3. The compiler generates a series of error messages like this: boost/statechart/simple_state.hpp:189: error: no type named 'inner_context_type' in 'struct Test::NormalMode<int>' I hastily sketched this out based on a larger code. If there are typos or other mistakes, let me know but the main problem I'm trying to solve is the "no type named" problem. I typedef it right in the template definition for NormalMode! This is using the current CVS for statechart, 1.33.1 for mpl. Is it possibly a compiler bug? Thanks! -Dave ---------------- Testcase #include <boost/statechart/state_machine.hpp> #include <boost/statechart/simple_state.hpp> #include <boost/statechart/event.hpp> #include <boost/statechart/custom_reaction.hpp> #include <boost/statechart/state.hpp> #include <boost/statechart/transition.hpp> #include <boost/mpl/list.hpp> #include <iostream> // Switch finite state machine for multiplexor schedule policy namespace Test { namespace sc = boost::statechart; namespace mpl = boost::mpl; // Inner states template <typename Type> struct On; template <typename Type> struct Off; template <typename Type> struct Error; // Outer states template <typename Type> struct NormalMode; template <typename Type> struct ErrorMode; // Events struct End : public sc::event<End> {}; struct UnconsumedEvent : public sc::event<UnconsumedEvent> { std::string st; UnconsumedEvent(const std::string &s) : st(s) {}; const std::string &state(void) const { return(st); }; }; template<typename Derived, typename Type> struct SwitchEvent : public sc::event<Derived> { typedef Type value_type; value_type ev; SwitchEvent(value_type e) : ev(e) {}; value_type value(void) const { return(ev); } }; template<typename Type> struct TurnOn : public SwitchEvent<TurnOn<Type>, Type> { TurnOn(Type value) : SwitchEvent<TurnOn<Type>, Type>(value) {}; }; template<typename Type> struct TurnOff : public SwitchEvent<TurnOff<Type>, Type> { TurnOff(Type value) : SwitchEvent<TurnOff<Type>, Type>(value) {}; }; template<typename Type> struct Switch; namespace detail { template<typename Type> struct typedefs { typedef Type value_type; typedef Switch<value_type> switch_context; typedef TurnOn<value_type> turn_on; typedef TurnOff<value_type> turn_off; typedef On<value_type> on; typedef Off<value_type> off; }; }; // The state machine template<typename Type> struct Switch : public sc::state_machine<Switch<Type>, NormalMode<Type> >, public detail::typedefs<Type> { typedef sc::state_machine<Switch<Type>, NormalMode<Type> > Base; typedef Switch<Type> This; std::string state(void) const { if (this->template state_cast<const typename This::on *>()) { return("ON"); } else if (this->template state_cast<const typename This::off *>()) { return("OFF"); } else { std::cerr << "Unknown state" << std::endl; std::abort(); return("ERROR"); } }; // Abort on unexpected events void unconsumed_event(const sc::event_base &event) { std::cerr << "Unexpected event in state " << state() << std::endl; std::abort(); this->post_event(new UnconsumedEvent(state())); }; }; // Define states // Outer template<typename Type> struct NormalMode : public sc::simple_state<NormalMode<Type>, Switch<Type>, Off<Type> >, public detail::typedefs<Type> { typedef sc::simple_state<NormalMode<Type>, Switch<Type>, Off<Type> > state_base; typedef typename state_base::inner_context_type inner_context_type; }; template<typename Type> struct ErrorMode : public sc::simple_state<ErrorMode<Type>, Switch<Type>, Error<Type> >, public detail::typedefs<Type> { typedef sc::simple_state<ErrorMode<Type>, Switch<Type>, Error<Type> > state_base; typedef typename state_base::inner_context_type inner_context_type; }; // Inner template<typename Type> struct Off : public sc::simple_state<Off<Type>, NormalMode<Type> >, public detail::typedefs<Type> { typedef Off<Type> This; typedef mpl::list< sc::custom_reaction<typename This::on>, sc::custom_reaction<End> > reactions; sc::result react(const typename This::on &) { this->template context<typename This::switch_context>().transit("OFF", "ON"); return(this->template transit<typename This::on>()); }; sc::result react(const End &) { this->terminate(); }; }; template<typename Type> struct On : public sc::simple_state<On<Type>, NormalMode<Type> >, public detail::typedefs<Type> { typedef On<Type> This; typedef mpl::list< sc::custom_reaction<typename This::off>, sc::custom_reaction<End> > reactions; sc::result react(const typename This::off &) { this->template context<typename This::switch_context>().transit("ON", "OFF"); return(this->template transit<typename This::off>()); }; sc::result react(const End &) { this->terminate(); }; }; template<typename Type> struct Error : sc::simple_state<Error<Type>, ErrorMode<Type> >, public detail::typedefs<Type> { }; }; int main(void) { Test::Switch<int> machine; machine.initiate(); machine.process_event( Test::TurnOn<int>(0) ); std::cout << "Now in state " << machine.state() << std::endl; machine.process_event( Test::TurnOff<int>(0) ); std::cout << "Now in state " << machine.state() << std::endl; machine.process_event( Test::TurnOff<int>(0) ); // Should produce error std::cout << "Now in state " << machine.state() << std::endl; machine.process_event( Test::End() ); }

3 8

Re: [Boost-users] [iostreams] array_sink
by EMalenfant＠interstarinc.com 01 Mar '06

01 Mar '06

From: Jeff Flinn [mailto:TriumphSprint2000@hotmail.com] > > My reading of the docs states that array_sink models the > concept sink, meaning that the following should compile: > [snip] > > io::array_sink lSink(x,4); > > const char* y = "abc"; > > io::write( lSink, y, 4 ); [snip] > > I must be doing something obviously wrong, on VC7.1 I get: > > c:\boost\boost_1_33_1\boost\iostreams\write.hpp(118) : error > C2039: 'write' > : is not a member of 'boost::iostreams::basic_array_sink<Ch>' [snip] Hi Jeff, I think this is related to the fact that array_sink is a "direct" sink. At the bottom of this page: http://www.boost.org/libs/iostreams/doc/?path=4.1.1.7 there is mention that "io::write()" is subject the the precondition that the sink is *not* convertible to "direct_tag". BTW, in the "details" of the iostreams library, there is a "direct_adapter" which seems to allow one to expose a "direct" Device as an "indirect" one. HTH, Éric Malenfant

2 1

Re: [Boost-users] [mpl] newbie question
by james.jones＠firstinvestors.com 01 Mar '06

01 Mar '06

Andy Little wrote: > Of course If anyone can implement the dimensional-analysis part of pqs > (in the Boost vault in The Physical Quantities Units directory) , such > that it compiles faster than it does currently, by using mpl, then I > will be happy to re-implement it using mpl. If I recall previous posts correctly, the compile-time using MPL was 30 seconds, and using your own code 4 seconds. Is this really a good reason not to use MPL? I would understand if it were 30 *minutes* versus 4 seconds. But in this case you're gaining 26 seconds per compile at the price of writing some custom code that may or may not be as maintainable as MPL (not saying it isn't - I haven't looked at pqs). I think in general it's understood that C++ in general, and BOOST in particular, can tend to increase compile times, because they heavily invest in compile-time template logic. But as I see it, an extra 26 seconds per compile times, say, 1000 compilations (to be generous) on a given project, is about one man-day (really less: it's 7-1/4 hours; how many of us put in only that much in a given workday?). Do you think it takes less than a man-day to come up with an MPL replacement, even one that only handles a subset of the functionality? Maybe, but I think there's reason to be skeptical. Also, if MPL resulted in a 7-times slower *runtime* than custom code, then choosing not to use might make more sense. Is that the case? If so, I missed it. Anyway, not saying you made the wrong decision, just offering a possible alternative way to think about this. - James

2 1

Re: [Boost-users] [BGL] Dijkstra Shortest Paths
by Michael Kettner 01 Mar '06

01 Mar '06

Hi Marcio! On Wednesday 29 March 2006 14:43, Marcio Paim de Aquino wrote: > Hello all, > > does anyone know how to make a custom dijkstra visitor that ends the > algorithm when > it finds the path between two especified vertexes? You might read the manual. This is from http://www.boost.org/libs/graph/doc/faq.html How do I perform an early exit from an algorithm such as BFS? Create a visitor that throws an exception when you want to cut off the search, then put your call to breadth_first_search inside of an appropriate try/catch block. This strikes many programmers as a misuse of exceptions, however, much thought was put into the decision to have exceptions has the preferred way to exit early. See boost email discussions for more details. Regards, Michael > Thanks, > > Marcio

2 1

[BGL] Dijkstra Shortest Paths
by Marcio Paim de Aquino 01 Mar '06

01 Mar '06

Hello all, does anyone know how to make a custom dijkstra visitor that ends the algorithm when it finds the path between two especified vertexes? Thanks, Marcio

1 0

Re: [Boost-users] problem with serialization of pure virtual
by Nat Goodspeed 01 Mar '06

01 Mar '06

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org [mailto:boost-users- > bounces(a)lists.boost.org] On Behalf Of Tobias Combe > Sent: Tuesday, February 28, 2006 7:18 AM > To: boost-users(a)lists.boost.org > Subject: [Boost-users] problem with serialization of pure virtual > > When i use "ar.register<derived>();" in the template of the base-class > to register the derived classes, i get a syntax error. [Nat] What compiler are you using?

2 1

serialization: found a (satisfactory) way to avoid the abstract class problem linking problem
by RIVASSEAU Jean Noel 01 Mar '06

01 Mar '06

Hello Robert, I found a way to avoid the link problem when dealing with a base abstract class, that maintains the base class abstract : I just manually instantiated the save/load functions for the abstract base class. They should have been instantiated by BOOST_CLASS_EXPORT, but this apparently does not work with abstract base classes; however manual instantiation works just fine. So I now have only one more problem (unfortunately, very serious), that happens with the serialization of std::vector containing pointers. Jean-Noël

1 0

What can I do after I finished all the steps of "getting started" ?
by 郭华长 01 Mar '06

01 Mar '06

thanks _________________________________________________________________ 与联机的朋友进行交流，请使用 MSN Messenger: http://messenger.msn.com/cn

1 0

Re: [Boost-users] serialization: errata: even manual instantiationisimpossible
by RIVASSEAU Jean Noel 01 Mar '06

01 Mar '06

// my_class_serialization.cpp or my_class.cpp or .. *.cpp #include <boost/archive/xml_iarchive.hpp> .... // all archives you might whant to use here. template<class Archive> serialize(Archive &ar, my_class &t....){ ... serialization for class my_class } #include "my_class.hpp" // explict instantiation here for all the archives which interest me template void serialize<boost::archive::xml_iarchive, my_class>; ... // explicit instantiation for all other archives you might use here. I notice you still include the archive headers in my_class_serialization.cpp. In that case, you do not have in fact to manually instantiate templates, since my_class_serialization.cpp includes "my_class.hpp" which includes export.hpp and maybe BOOST_CLASS_EXPORT after the archive headers included in class_serialization.cpp, so template instantiation will occure anyway. Anyway let's close this topic. I understood what the point was. Jean-Noël

1 0

Re: [Boost-users] Serialization : unregistered_cast & otherquestions
by RIVASSEAU Jean Noel 01 Mar '06

01 Mar '06

This is true. But this is a minor in my opinion. The root cause of this situation is that linkers complain about multiply defined functions - even when those functions are identical. Maybe someday we'll have smarter linkers - but until then this works quite well. It does require that one spend a little time explicitly considering code instantiation. But this isn't necessarily bad. Letting the compile/linker do all the work will lead to code bloat and compilation time problems. I definitely agree with you - smarter linkers would be a big gift. Right now dealing with templates is generally a pain because of linker issues, and requires that one takes a lot of precaution to insure everything compiles/links smoothly. I had the same problems when using the BGL last year, and also had to resort to manual template instantiation in the end. Jean-Noël

1 0

[iostreams] array_sink
by Jeff Flinn 28 Feb '06

28 Feb '06

My reading of the docs states that array_sink models the concept sink, meaning that the following should compile: #include <boost/iostreams/device/array.hpp> #include <boost/iostreams/operations.hpp> namespace io = boost::iostreams; int main( int argc, char* argv[] ) { char x[4] = {}; io::array_sink lSink(x,4); const char* y = "abc"; io::write( lSink, y, 4 ); return 0; } I must be doing something obviously wrong, on VC7.1 I get: c:\boost\boost_1_33_1\boost\iostreams\write.hpp(118) : error C2039: 'write' : is not a member of 'boost::iostreams::basic_array_sink<Ch>' with [ Ch=char ] c:\boost\boost_1_33_1\boost\iostreams\write.hpp(52) : see reference to function template instantiation 'std::streamsize boost::iostreams::detail::write_device_impl<boost::iostreams::output>::write<boost::unwrap_reference<T>::type>(T &,const boost::iostreams::detail::member_char_type<T>::type *,std::streamsize)' being compiled with [ T=boost::iostreams::array_sink ] c:\dev\AAA - Advantage New\DasNew\DasClientTest\DasClientTest.cpp(36) : see reference to function template instantiation 'std::streamsize boost::iostreams::write<boost::iostreams::array_sink>(T &,const boost::iostreams::detail::member_char_type<T>::type *,std::streamsize)' being compiled with [ T=boost::iostreams::array_sink ] Any thoughts are appreciated. Thanks, Jeff

1 0

Re: [Boost-users] [mpl] newbie question
by Gottlob Frege 28 Feb '06

28 Feb '06

Top posting because I'm going to remark about this thread in general, but this message is a fine example. Andy seems to be speaking (mostly) about int_<>, integral_c, etc (I'll just say the incorrect 'int<>') and plus; David is talking about transform. I think, but can't say for sure, that Andy wants plus to work 'as expected' and always return int<>, not just 'concept-identical' to int. Maybe it does, I'm not sure. And/or he wants transform ***when applied to int<> with plus, etc*** to return int<>. David, says, that ***in general*** transform can't make the return type "match" (in Andy's stricter sense) the inputs. Maybe it could for the special case of int<>? IMO, that would be quite hard, as the point of the templates is to be general. Do I have this right, in any sense? P.S. for David, below: Date: Sat, 25 Feb 2006 10:22:57 -0500 > From: David Abrahams <dave(a)boost-consulting.com> > Subject: Re: [Boost-users] [mpl] newbie question > To: boost-users(a)lists.boost.org > Message-ID: <uoe0v799q.fsf(a)boost-consulting.com> > Content-Type: text/plain; charset=us-ascii > > "Andy Little" <andy(a)servocomm.freeserve.co.uk> writes: > > > I think we need a little bit more context here. > > > >> > > OP > >>> David Abrahams > >> > >> Andy Little (me) > >> > >> > > Just trying to use mpl::transform on a vector of int's and I can't > seem to > >> > > get > >> > > it working properly. Can anyone see what's wrong?? I'm trying to > perform > >> > > > >> > > vector_c<int, 1, 2, 3> + vector_c<int, 1, 1, 1> = vector_c<int, 2, > 3 ,4> > >> > > > >> > > The is_same function always returns false when I compile and run > it. > >> > > >> > The result of the transform is only required to be > "concept-identical" the line above says "the transform" >> > to the result you're looking for. > >> > > >> IMO that behaviour is sloppy. I see no reason why (at least) > >> > >> boost::is_same < plus< int_<1> ,int_<1> >::type, int_<2> > shouldnt > >> be true. > > > > Your change from "the transform" to "being about transform" above is > > problematic for me. I don't know what you mean. Nobody wrote "the transform" above. as mentioned, he did, but that doesn't mean I understand the point he is trying to make. Don't make this complicated. It is very simple: I made a statemnt > *about the behavior of transform*, and you replied "that behavior is > sloppy," and then proceeded to go on about something only distantly > related (the type of results of arithmetic operations). > > The behavior I was describing is not sloppy. To make the library > behave differently would introduce a huge overhead in implementation > code that is more likely than not to slow down compilation of user > programs. > > Let me be a little more explicit: > > transform<vector_c<int, ...> >::type > > is likely to be a specialization of vectorN where N is a numeral. > Therefore, testing it against a vector_c specialization using is_same > will always fail. That is the behavior I was referring to. > > I wouldn't care much what you said, except for that you're doing this > in a thread where impressionable "newbies" are reading, and I don't > want them to misunderstand the library design or the implementation > decisions and their costs/benefits. Your statement above not only > unfairly maligns Aleksey's work, it is misleading. > > -- > Dave Abrahams > Boost Consulting > www.boost-consulting.com > >

3 7

Re: [Boost-users] problem with serialization of pure virtual
by RIVASSEAU Jean Noel 28 Feb '06

28 Feb '06

You should send a code snippet. What are the syntax error you get, and the error you get when doing a "BOOST_CLASS_EXPORT(derived);" ? I also have a problem with an abstract base class (although at link time, not compile time). Try removing the pure virtual function (just to see if it works). Another hint too would be to try to serialize a constant member; sometimes I had strange ASSERTION_FAILURE related to serialization of non-constants (this is also explained in the docs). Jean-Noël -----Message d'origine----- De : boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] De la part de Tobias Combe Envoyé : mardi 28 février 2006 13:18 À : boost-users(a)lists.boost.org Objet : [Boost-users] problem with serialization of pure virtual Hello I read the documention and some prior postings to related topics. But none of the proposed solutions seems to work for me. My problem: I have an abstarct base class(with pure vitual function) and several derived from that. All are written in the same source/header -file. I want to serialize an object via a pointer to the base-class. When i use "ar.register<derived>();" in the template of the base-class to register the derived classes, i get a syntax error. When i export them with "BOOST_CLASS_EXPORT(derived);" or BOOST_CLASS_EXPORT_GUID(derived,"derived") it doesn't work (i think because they are all in the same file). I'm also using "BOOST_IS_ABSTRACT(base);" When i comment "oa << object;" ervything compiles fine. Uncommented i get a: boost/archive/detail/oserializer.hpp:567: error: incomplete type ` boost::STATIC_ASSERTION_FAILURE<false>' does not have member `value' error... So is there a solution (without seperating the derived classes into different files) for this problem? _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

3 2

[serialization] problem building libs
by Federico Feller 28 Feb '06

28 Feb '06

Hi, I am trying to use the serialization library with borland 6, but when i try to link a program that uses it, the linking fails to find the libboost_serialization-bcb-mt-d-1_33_1.lib file. I checked the libraries generated when i built the library (using bjam) and i found out that the 'mt' version of the library wasnt there. I generated the files ejecuting 'bjam -sTOOLS=borland' under the serialization/build directory. How can i get the mt libraries generated? thanks Federico __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

problem with serialization of pure virtual
by Tobias Combe 28 Feb '06

28 Feb '06

Hello I read the documention and some prior postings to related topics. But none of the proposed solutions seems to work for me. My problem: I have an abstarct base class(with pure vitual function) and several derived from that. All are written in the same source/header -file. I want to serialize an object via a pointer to the base-class. When i use "ar.register<derived>();" in the template of the base-class to register the derived classes, i get a syntax error. When i export them with "BOOST_CLASS_EXPORT(derived);" or BOOST_CLASS_EXPORT_GUID(derived,"derived") it doesn't work (i think because they are all in the same file). I'm also using "BOOST_IS_ABSTRACT(base);" When i comment "oa << object;" ervything compiles fine. Uncommented i get a: boost/archive/detail/oserializer.hpp:567: error: incomplete type ` boost::STATIC_ASSERTION_FAILURE<false>' does not have member `value' error... So is there a solution (without seperating the derived classes into different files) for this problem?

2 1

Re: [Boost-users] problem with serialization of pure virtual
by RIVASSEAU Jean Noel 28 Feb '06

28 Feb '06

>From the code snippet, I can say that you are not serializing via a pointer to base class, since you serialize tmp which is an object, not a pointer (by the way, tmp is just an object of the base class... you would lose the information of *event if event pointed to a derived class). Try changing: SENSOR_Event tmp = *event; oa << tmp; to just: oa << event; And also, include the BOOST_CLASS_EXPORT macro for the base class. Or, you can try doing (to see what it does): const SENSOR_Event tmp = *event; oa << tmp; but there, you are serializing a pointer, not an object. Jean-Noël -----Message d'origine----- De : boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] De la part de Tobias Combe Envoyé : mardi 28 février 2006 16:51 À : boost-users(a)lists.boost.org Objet : Re: [Boost-users] problem with serialization of pure virtual Jean Noel wrote: >You should send a code snippet. > Event.h: #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include <boost/serialization/base_object.hpp> #include <boost/serialization/vector.hpp> #include <boost/serialization/shared_ptr.hpp> #include <boost/serialization/export.hpp> #include <fstream> class SENSOR_Event{ friend class Sensor; friend class AODVRTSensor; friend class OLSRRTSensor; private: friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar.register<NodeEvent>(); ""// for each derived class ar & time; ar & sourceId; ar & sourceType; ar & eventType; ar & *data; } protected: double time; int sourceId; std::string sourceType; std::string eventType; DataNode *data; public: ... }; class NodeEvent : public SENSOR_Event{ private: friend class boost::serialization::access; template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & boost::serialization::base_object<SENSOR_Event>(*this); } public: NodeEvent(); NodeEvent(double nodeId, double x, double y, double z, double speed); }; ...//other derived Events BOOST_CLASS_EXPORT(NodeEvent); ""// for each derived class BOOST_IS_ABSTRACT(SENSOR_Event); Sensor.cc: #include "Event.h" void Sensor::send(const SENSOR_Event *event){ ... // serialize to string std::stringstream s; boost::archive::text_oarchive oa(s); SENSOR_Event tmp = *event; oa << tmp; std::string p = s.str(); ... } Error: ... boost/archive/detail/oserializer.hpp: In function `void boost::archive::save(Archive&, T&) [with Archive = boost::archive::text_oarchive, T = SENSOR_Event]': boost/archive/basic_text_oarchive.hpp:78: instantiated from `void boost::archive::basic_text_oarchive<Archive>::save_override(T&, int) [with T = SENSOR_Event, Archive = boost::archive::text_oarchive]' boost/archive/detail/interface_oarchive.hpp:78: instantiated from `Archive& boost::archive::detail::interface_oarchive<Archive>::operator<<(T&) [with T = SENSOR_Event, Archive = boost::archive::text_oarchive]' IDSNet/Sensor.cc:24: instantiated from here boost/archive/detail/oserializer.hpp:567: error: incomplete type ` boost::STATIC_ASSERTION_FAILURE<false>' does not have member `value' >What are the syntax error you get, and the error you get when doing a "BOOST_CLASS_EXPORT(derived);" ? > "syntax error before `;' token" for that line >I also have a problem with an abstract base class (although at link time, not compile time). Try removing the pure virtual function (just to see if it works). > this doesn't help >Another hint too would be to try to serialize a constant member; sometimes I had strange ASSERTION_FAILURE related to serialization of non-constants (this is also explained in the docs) > I'm serializing a constant member... _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

serialization: errata: even manual instantiation is impossible
by RIVASSEAU Jean Noel 28 Feb '06

28 Feb '06

Hello : Regarding my last post : Even a manual template instantiation is in fact impossible since it would require including the necessary archive headers (else, the boost ::archive ::xml_iarchive is not recognized). Since you forbid to include any archive headers in the classes, I do not understand how you can follow your own advice. This seems impossible to me. Would you have code to illustrate ? Jean-Noël

2 1

Re: [Boost-users] Serialization : unregistered_cast & otherquestions
by RIVASSEAU Jean Noel 28 Feb '06

28 Feb '06

Hello, CommonSerialize.h - remove the following #include <boost/archive/xml_oarchive.hpp> #include <boost/archive/xml_iarchive.hpp> and add the following: #include <boost/serialization/export.hpp> test_independent.cc - change the top to look like the following: // INDEPENDENT TEST #include <boost/archive/xml_oarchive.hpp> #include <boost/archive/xml_iarchive.hpp> #include <MObject.h> #include <MObject_serialization.hh> #include <MemberVariableSpecification.h> #include <MemberVariableSpecification_serialization.hh> #include <fstream> This won't work. Since you now have the archive headers in only one place, there is no multiple definition problem. However serialization code is *not* instantiated for MObject or MemberVariableSpecification. This is normal since when compiling the .cc that contains this code, there is no archive header included and so the export.hpp has no effect. The code is here but is not instantiated. So in order to follow this advice: a) include all boost/serialization/.. headers in each class file. b) include NO boost/archive/... headers in any class file c) make a "template instantiation module" which instanticiates code for all archives I plan to use. This can be either in the app or in a library. d) lihk and execute without problem. I have to explicitly instantiate the serialization code for the needed archive in the .cc files. That is, do: template void save<boost::archive::xml_oarchive>( boost::archive::text_oarchive & ar, const MObject & m, const unsigned int file_version ); And same for load. This is what you do in demo_pimpl.cpp. Is that what you usually do and recommend to do? This has the advantage to avoid big compilations (these code instantiations will only occur when the class to serialize has indeed changed). However this has the inconvenience of manually instantiating every template (and if you want to change your archive format , eg from text to xml for example, everything needs to be changed). Jean-Noël

2 1

[BGL] graph without parallel edges
by Alejandro Aragón 28 Feb '06

28 Feb '06

Hi everyboty, Can someone point to a concrete example of a graph without parallel edges??? I am using setS as my container for the edges but I still insert edges twice in my graph algorithm. Thank you, aa

3 4

Re: [Boost-users] [graph] [python] Python vertex vs. C++ Vertex
by Nat Goodspeed 28 Feb '06

28 Feb '06

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org [mailto:boost-users- > bounces(a)lists.boost.org] On Behalf Of David E. Konerding > Sent: Monday, February 27, 2006 5:09 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] [graph] [python] > > Doug Gregor wrote: > > > > Your guess is correct. We don't cache the Python objects corresponding > > to vertex and edge descriptors. > > my idea was to keep the > mapping between on-screen widgets and the graph vertices they corresponded > to in a dictionary: > > self._widgetmap[vertex] = widget > > However, since Vertex objects aren't cached, placing the vertex object I > get back from add_vertex obviously isn't going to work. [Nat] Maybe twiddle the hash function of the Python vertex object so that it derives its return value from the underlying C++ Vertex?

1 0

[program_options]Iterator decremented past begin of container
by Peter Gerell 28 Feb '06

28 Feb '06

Hi, I have filed the following bug in the SF tracker. In format_paragraph the following code appears: string::const_iterator line_begin = par.begin(); <snip> string::const_iterator last_space = find(reverse_iterator<string::const_iterator>(line_end - 1), reverse_iterator<string::const_iterator>(line_begin - 1), ' ') .base(); This generates a run-time assertion if compiled with VC8 and debug/checked iterators. /Peter

1 1

Re: [Boost-users] serialization: again a problem, failing to serialize a std::vector of pointers
by RIVASSEAU Jean Noel 28 Feb '06

28 Feb '06

I added this into the ClassSpecification_serialization.cc : typedef std::vector< MemberVariableSpecification * , std::allocator<MemberVariableSpecification*> > my_vector; BOOST_CLASS_IMPLEMENTATION(my_vector, boost::serialization::object_serializable) But I still get the same error... help! Jean-Noël Ps: the typedef was necessary, else gcc parsing would recognize 3 arguments to the macro BOOST_CLASS_IMPLEMENTATION -----Message d'origine----- De : boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] De la part de Robert Ramey Envoyé : lundi 27 février 2006 18:25 À : boost-users(a)lists.boost.org Objet : Re: [Boost-users] serialization: again a problem,failing to serialize a std::vector of pointers "RIVASSEAU Jean Noel" <JN.RIVASSEAU(a)oberthurcs.com> wrote in message news:87F60F7FA02FF749AFB02BD9FCAA6B04DA7ABF@naserv31.nanterre.oberthurcs.com... Hello This is my last problem with the BSL but the most important one (because there is no workaround). I am trying to serialize a class (whose name is "ClassSpecification") which has a std::vector of pointers. The code for serializing the class the pointer refer to (MemberVariableSpecification) is written and instantiated correctly. However I cannot correctly serialize the std::vector. It fails with a message complaining about: C:/Boost/include/boost-1_33_1/boost/archive/detail/iserializer.hpp:115: error: incomplete type `boost::serialization::extended_type_info_null<std::vector<MemberVariableSpecification*, std::allocator<MemberVariableSpecification*> > >' used in nested name specifier I do not understand why I need an extended_type_info for this vector. I sure need it for the class the pointers refer to (and I did specify it), but the std::vector itself is serialized as such, not as a pointer. *** hmmm - can sympathise with you here. I suspect that this is a mistake. It might be an accidental side effect of the fact that the default serialization trait for any class is tracked with class information. You might try the following: BOOST_CLASS_IMPLEMENTATION( std::vector<MemberVariableSpecification*, std::allocator<MemberVariableSpecification*>, boost::serialization::object_serializable ) Why do I get this error ??? I would have to look into it. Can you please check the attached code and help me? Thanks Jean-Noël Ps: using gcc 3.4.2 _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Re: [Boost-users] Serialization : unregistered_cast & otherquestions
by RIVASSEAU Jean Noel 28 Feb '06

28 Feb '06

Hello I agree with you, and currently have the same comprehension of the problem than you. I am currently also including BOOST_EXPORT_CLASS in only one implementation file *per class*. This seems to work. Robert is saying however, that even that can cause problem, but as written on a previous message, I cannot manage to follow his advice on including the archive headers in only one instantiation module (except putting all serialization code into that module, which I did previously: this is a maintenance nightmare, to the point that I ended up trying to break my code into smaller places). I'll chime in, as I'm having exactly the same issue, but on darwin/ gcc-4 with code in multiple dynamically loaded libraries... (I have other issues too, I get to those later) The problem is that although export.hpp is only included once per generated .o file, there are multiple .o files all including the same headers - and each therefore generates the same template instantiations, thereby causing the multiple definitions during linking. Also - the same headers may be included in multiple shared libraries, exacerbating the problem with the same code instantiated into multiple libraries - a serious problem if there are singletons. I may not be understanding this correctly - here's what >I< think needs to happen - please correct me. For any derived class, there is a set of code (templates) that need to be instantiated for each archive type (specifically, the list boost::archive::detail::known_archive_types::type, for the templates guid_initializer<T> and export_instantiate<T, archive_list>) From what I see, these are NOT declarations required by the other serialization code, but singletons that, during construction, register the serializers to the derived classes with the extended_type_info class registry. Is that incorrect? If the above is correct, then the BOOST_EXPORT_CLASS should only be in exactly one implementation file (.cpp, .C, .cc, whatever). And also, THAT implementation file should ONLY be linked into one shared library. _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Re: [Boost-users] serialization: problem with abstract base class
by RIVASSEAU Jean Noel 28 Feb '06

28 Feb '06

I have included <boost/serialization/base_object.hpp> where it should be, it did not change anything... Anyway what is "implementing is_abstract for your compiler" ?? Jean-Noël *** its hard for me to follow what's going on here. One thing I did notice is that the I didn't see <boost/serialization/base_object.hpp> included in the places where it is used. I'm not sure if that's significant. Robert Ramey _______________________________________________ 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

1 0

Building 1.33.1 with VC .NET 2003
by D. R. Evans 28 Feb '06

28 Feb '06

As far as I can tell, I followed the instructions exactly: > First you need to change to the directory where you have the Boost distribution you downloaded. OK, I'm in boost_1_33_1. Then execute: bjam "-sTOOLS=vc-7_1" which produces: ----- Jamfile:197: in load-jamfiles *** argument error * rule install-subinclude ( jamfiles + : options * ) * called with: ( : ) * missing argument jamfiles C:\boost\boost_1_33_1\tools/build/v1\boost-base.jam:2855:see definition of rule 'install-subinclude' being called C:\boost\boost_1_33_1\tools\build\v1\bootstrap.jam:21: in boost-build C:\boost\boost_1_33_1\boost-build.jam:16: in module scope ----- What am I doing wrong? Doc Evans

9 16

Boost lambda question
by yinglcs2＠yahoo.com 28 Feb '06

28 Feb '06

Hi I have a Boost lambda question, I appreciate is someone can help me out: I have a class A: class A{ private: B& getB() {return _b;} B& _b; }; vector<A> aList; void aFunction (A& a, B& b); how can I write a loop to walk thru a list of A and call aFunction. for (vector<A>::iterator itr = aList.begin; itr != end; itr++) { A a = (*itr); aFunction (a, a->getB()); } __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

Re: [Boost-users] Buggy Prim's minimum spanning tree example
by Olivier Delalleau 27 Feb '06

27 Feb '06

>> Hello, >> >> I have a problem with the example for Prim's minimum spanning tree >> that >> can be found here: >> http://www.boost.org/libs/graph/example/prim-example.cpp >> >> The problem is that when compiled in 32 bits but run on a 64 bits >> computer, and modified with different edges and weights, it does not >> work anymore. >> The modified version that exhibits this behaviour is here: >> http://www.iro.umontreal.ca/~delallea/tmp/prim-example-fail.cpp >> It is a simplified version (I removed some compiler-specific code for >> MSVC) where I replaced the edges and weights by a real-life example I >> have to solve. >Unfortunately, I am unable to duplicate the problem here. On our 64-bit >Opteron machines (running Linux), I get the same results for 64- and >32-bit binaries. >Which version of Boost are you using? What operating system? What >version of GCC? Thanks for the reply. I hope this message will get into the proper thread on the boost mailing-list (had forgotten to turn on my boost digest email...). Here are more detailed information: OS = Fedora Core 4: 'uname -a' -> Linux xxx.yyy 2.6.15-1.1831_FC4 #1 SMP Tue Feb 7 13:37:59 EST 2006 x86_64 x86_64 x86_64 GNU/Linux g++ --version -> g++ (GCC) 4.0.2 20051125 (Red Hat 4.0.2-8) Boost version is 1.33.0. CPU is AMD Athlon(tm) 64 Processor 3500+ Thank again, Olivier PS: just in case, my original post with full details and program output: http://lists.boost.org/boost-users/2006/02/17314.php

2 2

Re: [Boost-users] Serialization : unregistered_cast & otherquestions
by RIVASSEAU Jean Noel 27 Feb '06

27 Feb '06

Hello Robert, Thanks for your reply. However you did not understand the problem. I read the documentation and understood the purpose of BOOST_EXPORT as explained in the documentation, and as reexplained in your last mail. The problem is at linking, but is not one of undefined reference (template not instantiated), but, on the other hand, *a multiple definition problem.* If, as suggested, you move BOOST_EXPORT to the class header, even if you move the archive headers before the serialization/export header, you will have multiple instantiations of the same template. This is because every time you include the serialization class header in your program there is some code instantiation, since the EXPORT is in that file. Since this header is included several times in the program, multiple instantiations of the same code occurs (note: apparently this happens even if there is no definition of the templated code to be instantiated (since the implementation is only in the .cc), only a declaration, because BOOST_EXPORT instantiates some kind of *helper code* that gets multiple defined). Anyway, if you can change the code in order to avoid this multiple definition problem, I'll be glad to test, but I believe it is impossible. However, putting BOOST_EXPORT in the .cc avoids the problem entirely, so this is acceptable. I am sending again code with your suggested changes, in order to show you your method does not work. If you look at the code you will see that each serialization header includes <CommonSerialize.h> which contains the archive headers. Then after <CommonSerialize.h> inclusion comes serialization/export.hpp inclusion, so the archive headers are BEFORE export.hpp. Then follows BOOST_EXPORT. At linking I get the multiple definition problem that I mentioned. If you just move BOOST_EXPORT into the .cc no problems at all. You can check for yourself if you try to compile the code. Thank you!! Jean-Noël Ps: I ran into two other problems that I'll write mail for later... OK - BOOST_EXPORT has some non-obvious behavior which I'll explain. Maybe this will help. BOOST_EXPORT has two functions: a) To associate a class with an external unique name (GUID) b) To instanticiate templated code for archives used. The second is not as obvious as it might seem. Suppose I have: class A { }; class B : public A { } A * aptr = new B; text_archive ar; ar << a; The problem is that the compiler never sees anything like ar << b so it has no way to know that the serialization code for B needs to be instantiated for the archive class text_archive. So each archive class defines a special macro. Then BOOST_EXPORT instantiates code for each combination of the class and archive class. If this were not done, one would get a link error with undefined symbol for load<text_archive, B> or something lke that. Of course the above presumes that the archive classes are included BEFORE the serialization/boost/export.hpp header. So if you make the following changes in your code I believe you will get the desired results. a) Move BOOST_EXPORT to the class header. b) In test.cc - move the headers boost/archive/... above the headers boost/serialization/.. and let me know that happens. Robert Ramey

3 4

graph class creation???
by Alejandro Aragón 27 Feb '06

27 Feb '06

Hi, I've been using the graph library for a while now. I was finally able to run my first Kruskal's algorithm adapted to my own problem. I am not a expert in C++ so I would like to ask something. I was taught that you should keep the definitions in one file and the declarations in another file. Well, working with the boost graph lirary, do we have to do this as well???? It doesn't make sense to me to do this since I am already working with the headers of the boost graph library to have the declarations in a .h file. Therefore, I just created a file graph.cxx where I put the particular implementation that I'm using, the definitions of my own graph properties and so on. Is this correct? Thanks for your help. a^2

2 2

serialization: problem with abstract base class
by RIVASSEAU Jean Noel 27 Feb '06

27 Feb '06

Hello The following code (attached) demonstrate a problem that I have. I am trying to serialize via pointer to base class (MObject) which is abstract. The docs say that a compile error will occur when trying to do that. I don't have any compile time errors emitted but the build fails at link time (it does not instantiate the save/load code for the abstract base class). The solutions provided in the docs are: write BOOST_IS_ABSTRACT(MObject): I did that and nothing changes; Or Implement is_abstract for your compiler. I do not understand what this means. Can you help me out ? Currently the only workaround I have is to not make the base class abstract, but I would like it to be abstract... Jean-Noël

2 1

Re: [Boost-users] Serialization : unregistered_cast & otherquestions
by RIVASSEAU Jean Noel 27 Feb '06

27 Feb '06

Again I forgot to include the code sorry... _____ De : boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] De la part de Robert Ramey Envoyé : vendredi 24 février 2006 17:53 À : boost-users(a)lists.boost.org Objet : Re: [Boost-users] Serialization : unregistered_cast & otherquestions "RIVASSEAU Jean Noel" <JN.RIVASSEAU(a)oberthurcs.com> wrote in message news:87F60F7FA02FF749AFB02BD9FCAA6B04DA737E@naserv31.nanterre.oberthurcs.com... Thanks for all your help. I have decided to try to reorganize everything into small parts as you have said, in order to better understand. I am in the process of doing this, but I have already some remarks about your comments. I have chosen the organisation principle you have said: in the class.h, nothing about the serialization is present in serialization/class_serialization.hh : I have the serialization declaration code + some traits in serialization/class_serialization.cc : I have the serialization implementation code + BOOST_EXPORT The only thing where I have not followed your advice is the presence of BOOST_EXPORT on the class_serialization.hh rather than class_serialization.cc. If I put it on the header, since I have to include the header on test.cc, one instantation of something is done while encountering BOOST_EXPORT. Later while compiling class_serialization.cc, since it encounters BOOST_EXPORT one more time another instantiation occurs and I had problems with linking (gcc 3.4 reported multiple definitions of something). **** OK - BOOST_EXPORT has some non-obvious behavior which I'll explain. Maybe this will help. BOOST_EXPORT has two functions: a) To associate a class with an external unique name (GUID) b) To instanticiate templated code for archives used. The second is not as obvious as it might seem. Suppose I have: class A { }; class B : public A { } A * aptr = new B; text_archive ar; ar << a; The problem is that the compiler never sees anything like ar << b so it has no way to know that the serialization code for B needs to be instantiated for the archive class text_archive. So each archive class defines a special macro. Then BOOST_EXPORT instantiates code for each combination of the class and archive class. If this were not done, one would get a link error with undefined symbol for load<text_archive, B> or something lke that. Of course the above presumes that the archive classes are included BEFORE the serialization/boost/export.hpp header. So if you make the following changes in your code I believe you will get the desired results. a) Move BOOST_EXPORT to the class header. b) In test.cc - move the headers boost/archive/... above the headers boost/serialization/.. and let me know that happens. Robert Ramey _____ De : boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] De la part de Robert Ramey Envoyé : jeudi 23 février 2006 17:44 À : boost-users(a)lists.boost.org Objet : Re: [Boost-users] Serialization : unregistered_cast & otherquestions Without actually seeing the code, its hard for me to give intelligent advice. Lucky for you (maybe) that's not going to inhibit me from speculating. Here is what I recommend for anyone making a very large program: a) extended_type_info_no_rtti presumes that all classes serialized as pointers have been exported. Should this not be the case, you'll get the error message indicated. Double check this. b) Serilaization traits should be in the header files so that they are not "missed" anytime something like "ar << x" is invoked. Given you're situation I would recommend a file structure like the following: class.hpp - without seriaiization like you have now. serialization/class.hpp - includes class.hpp. also includes BOOST_EXPORT and any other traits for this "class". serialization/class.cpp c - includes serialization/class.hpp and includes the actual serialization code. Also this should include code instantiation for the archives that you use. Look at demo_pimpl to see how this is done. All the above code should be organized into a library. The reason is that this will generate code for all the archives mentioned but your application may not use all the archives so putting the above code in a library and linking to it will mean that your application will always have what it actuallyuses but nothing it doesn't - avoids "code bloat". Note that in compiling code for the library make sure to specify "function level linking". Take the "least derived class" - that one at the top of the class hierarchy. Make a small test program similar to the tests in the serialization library. This should be a very small job. This code can be class_test.cpp. Run this test on all archives you use. When this test passes, do the same for the other classes until something fails. This might seem to be more work - believe me its not. It will a) guarentee that you make progress toward a robust program b) give you confidence that your program has minimum of hidden bugs c) permit you to re-run the tests automatically when you make future changes. d) should a problem arise with the serialization or other library, it will give a lot more information in order to be helpful. Robert Ramey Now, the problem is where to put the serialization code for these classes. If I just write them on the implementation file (the .cc) for the class, it does not work. At run time I have always errors telling me that either the class is not exported (unregistered_class exception) or an unregistered_cast happens. The only solution I have found is to put *ALL* serialization code into the same big .cc file. If I do just that, it works. However this file is becoming enormous and has to be recompiled every time I change only *one* of the class to be serialized. It is already taking a minute to compile on a fast machine, so I must really break it up into other parts. But everytime I do that everything stops working. Have you any ideas, Robert? I am using extended_type_info_no_rtti, this may be the cause of the problem... Jean-Noël Ps: I still have the std::string bug, which is also uncomprehensible for me. _____ _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users _____ _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

2 1

[BGL] Is it a bug when using random access EdgeList?
by Tux Han 27 Feb '06

27 Feb '06

I wrote a very simple sample using BGL adjacent list and using a random access EdgeList. But when I invoke remove_out_edge method, It seems wrong. My config is Boost 1.33.1 and Visual Studio 2005, here is my code: ------------x-------------------------------Begin here-----------------------------------------x------------- #include <boost/graph/adjacency_list.hpp> #include <string> using namespace boost; using namespace std; namespace boost{ struct vertex_label_t { typedef vertex_property_tag kind; }; } template <class EdgeIter, class Graph> void print_graph(EdgeIter first, EdgeIter last, const Graph& G) { typedef typename property_map<Graph, vertex_label_t>::const_type LabelMap; LabelMap label = get(vertex_label_t(), G); typedef typename boost::property_traits<LabelMap>::value_type LabelType; LabelType src_label, targ_label; while (first != last) { src_label = boost::get(label, source(*first, G)); targ_label = boost::get(label, target(*first, G)); cout << src_label << " <-> " << targ_label << endl; ++first; } } typedef property<vertex_label_t, std::string> LabelProperty; typedef adjacency_list<vecS, vecS, undirectedS, LabelProperty, boost::no_property, boost::no_property, vecS> MyGraphType; bool AnyEdge(MyGraphType::edge_descriptor e) { return true; } int main() { typedef pair<int,int> Pair; Pair edge_array[8] = { Pair(0,1), Pair(0,2), Pair(0,3), Pair(0,4), Pair(2,4), Pair(3,1), Pair(3,4), Pair(4,1) }; MyGraphType G(5); for (int i = 0; i < 8; ++i) add_edge(edge_array[i].first, edge_array[i].second, G); property_map<MyGraphType, vertex_label_t>::type name = get(vertex_label_t(), G); boost::put(name, 0, "0"); boost::put(name, 1, "1"); boost::put(name, 2, "2"); boost::put(name, 3, "3"); boost::put(name, 4, "4"); print_graph(edges(G).first, edges(G).second, G); // Remove out edges of vertex 0 cout << "Remove out edges of vertex 0" << endl; remove_out_edge_if(0, AnyEdge, G); print_graph(edges(G).first, edges(G).second, G); } ------------x-------------------------------End here-----------------------------------------x------------- and the result is: ------------------------------------------------------------------------------------------------------------------ 0 <-> 1 0 <-> 2 0 <-> 3 0 <-> 4 2 <-> 4 3 <-> 1 3 <-> 4 4 <-> 1 Remove out edges of vertex 0 0 <-> 2 0 <-> 4 3 <-> 1 4 <-> 1 ------------------------------------------------------------------------------------------------------------------ Is there something wrong? --------------------------------- Brings words and photos together (easily) with PhotoMail - it's free and works with Yahoo! Mail.

2 1

Buggy Prim's minimum spanning tree example
by Olivier Delalleau 27 Feb '06

27 Feb '06

Hello, I have a problem with the example for Prim's minimum spanning tree that can be found here: http://www.boost.org/libs/graph/example/prim-example.cpp The problem is that when compiled in 32 bits but run on a 64 bits computer, and modified with different edges and weights, it does not work anymore. The modified version that exhibits this behaviour is here: http://www.iro.umontreal.ca/~delallea/tmp/prim-example-fail.cpp It is a simplified version (I removed some compiler-specific code for MSVC) where I replaced the edges and weights by a real-life example I have to solve. Here is the output on a 64 bits computer: -> g++ prim-example-fail.cpp -> ./a.out parent[0] = no parent parent[1] = 9 parent[2] = 19 parent[3] = 4 parent[4] = 0 parent[5] = 26 parent[6] = 27 parent[7] = 4 parent[8] = 0 parent[9] = 3 parent[10] = 0 parent[11] = 0 parent[12] = 6 parent[13] = 12 parent[14] = 17 parent[15] = 28 parent[16] = 4 parent[17] = 15 parent[18] = 1 parent[19] = 24 parent[20] = 12 parent[21] = 10 parent[22] = 5 parent[23] = 1 parent[24] = 22 parent[25] = 0 parent[26] = 4 parent[27] = 7 parent[28] = 13 parent[29] = 4 And when compiled in 32 bits with the -m32 option of g++: -> g++ -m32 prim-example-fail.cpp -> ./a.out parent[0] = no parent parent[1] = no parent parent[2] = no parent parent[3] = no parent parent[4] = no parent parent[5] = no parent parent[6] = no parent parent[7] = no parent parent[8] = no parent parent[9] = no parent parent[10] = no parent parent[11] = no parent parent[12] = no parent parent[13] = no parent parent[14] = no parent parent[15] = no parent parent[16] = no parent parent[17] = no parent parent[18] = no parent parent[19] = no parent parent[20] = no parent parent[21] = no parent parent[22] = no parent parent[23] = no parent parent[24] = no parent parent[25] = no parent parent[26] = no parent parent[27] = no parent parent[28] = no parent parent[29] = no parent I don't know if the problems comes from a faulty example or from the Boost Prim's spanning tree algorithm. Unfortunately I find the graph library quite difficult to understand and this example is the only basis I have to work from. Thanks for any help, Olivier

2 1

[BGL]Problems in the shortest pair algorithms.
by Peter Gerell 27 Feb '06

27 Feb '06

Hi, I have reported some problems with the johnson_all_pairs_shortest_paths and floyd_warshall_all_pairs_shortest_paths algorithms. What is the correct way to report these problems. I made some posts to the list last week, but didn't get any response. Perhaps this should go on the developer mailing list instead? However, the problems I have noticed are: Floyd-Warshall: 1. std::min is used instead of the functor passed to as teh distance_compare parameter at several places 2. The distance map is initialized with 0 instead of zero. Johnson: 3. std::numeric_limits<DT>::max() is used instead of the distance_inf parameter. 4. The distance_combine and distance_compare parameters are not used. The bellman_ford_shortest_paths algorithm is called with std::less and closed_plus. Thanks Peter

2 1

[BGL] obtaining list of edges in a shortest path
by Lars S. Jessen 27 Feb '06

27 Feb '06

Hi. I have an adjacency_list graph where I need to find the shortest path between two vertices. This can be done with the following code (from http://www.boost.org/libs/graph/example/astar-cities.cpp) ... vector<mygraph_t::vertex_descriptor> p(num_vertices(g)); vector<cost> d(num_vertices(g)); try { // call astar named parameter interface astar_search (g, start, distance_heuristic<mygraph_t, cost, location*> (locations, goal), predecessor_map(&p[0]).distance_map(&d[0]). visitor(astar_goal_visitor<vertex>(goal))); } catch(found_goal fg) { // found a path to the goal list<vertex> shortest_path; for(vertex v = goal;; v = p[v]) { shortest_path.push_front(v); if(p[v] == v) break; } ... As you can see, it's easy to obtain the list of vertices that makes the shortest path from start to goal, but how do I obtain the list of edges connecting start to goal? - Lars

2 1

Bjam question
by Drumheller, Michael 27 Feb '06

27 Feb '06

Dear Bjam Experts: For some reason all my source files are getting compiled twice. Below is my Jamfile (stripped to its essentials, and names changed to protect the innocent), and below that is the output (also stripped way down). Sorry for the clutter--I have tried to strip it down to the minimum. Notice how every .obj gets constructed twice. Yet the destination path (vc-7_1\release\threading-multi\ is the same in each case; also, I'm also invoking bjam with precisely that target specified on the command line. Is there anything really obvious to bjam-adjusted eyes going on here? Thank you very much. Michael Drumheller ----------------------------------------------------------cut here: Jamfile--------------------------------------- project-root ; import python ; include python.jam ; FOOCORE_SOURCES = File1 File2 ; FOOCORE_SOURCES = ..\\..\\src\\$(FOOCORE_SOURCES).cpp ; lib Foo : $(FOOCORE_SOURCES) : <include>C:\\Boost\\include\\boost-1_32 <vc-7_1><*><define>WIN32 <include>..\\..\\src <include>C:\\Python24\\include <include>"C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\include" ; ----------------------------------------------------------cut here: resulting output --------------------------- 06-02-26:12:22:26:boost/FooBar=> bjam -sTOOLS=vc-7_1 "-sBUILD=release <threading>multi" ...found 3088 targets... ...updating 142 targets... vc-C++ ./build\bin\FooBar\libFoo.lib\vc-7_1\release\threading-multi\File1.obj File1.cpp vc-C++ ./build\bin\FooBar\libFoo.lib\vc-7_1\release\threading-multi\File2.obj File2.cpp ...<snip>... vc-Archive ./build\bin\FooBar\libFoo.lib\vc-7_1\release\threading-multi\libFoo.lib Microsoft (R) Library Manager Version 7.10.3077 Copyright (C) Microsoft Corporation. All rights reserved. "./build\bin\FooBar\libFoo.lib\vc-7_1\release\threading-multi\File1.obj" "./build\bin\FooBar\libFoo.lib\vc-7_1\release\threading-multi\File2.obj" ...<snip>... vc-C++ ./build\bin\FooBar\libFoo.lib\vc-7_1\release\threading-multi\File1.obj File1.cpp vc-C++ ./build\bin\FooBar\libFoo.lib\vc-7_1\release\threading-multi\File2.obj File2.cpp ...<snip>... vc-Archive ./build\bin\FooBar\libFoo.lib\vc-7_1\release\threading-multi\libFoo.lib Microsoft (R) Library Manager Version 7.10.3077 Copyright (C) Microsoft Corporation. All rights reserved. "./build\bin\FooBar\libFoo.lib\vc-7_1\release\threading-multi\File1.obj" "./build\bin\FooBar\libFoo.lib\vc-7_1\release\threading-multi\File2.obj" ...<snip>...

3 2

std::map, boost::smart_ptr and std::for_each()
by Pavel Syomin 26 Feb '06

26 Feb '06

Hi to all! How to use for_each() for std::map of boost::smart_ptr items? Thanks.

1 0

Re: [Boost-users] Building 1.33.1 with VC .NET 2003
by Wu Yinghui, Freddie 26 Feb '06

26 Feb '06

> Message: 5 > Date: Sat, 25 Feb 2006 16:50:16 -0700 > From: "D. R. Evans" <doc.evans(a)gmail.com> > Subject: Re: [Boost-users] Building 1.33.1 with VC .NET 2003 > Message-ID: <256f4e900602251550i2cd6f6d3m(a)mail.gmail.com> > > Incidentally, I get the same result if I try: > > C:\boost\boost_1_33_1>bjam "-sTOOLS=vc-7_1" "-sVC71_ROOT=C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7" > > In fact, I get the same result using any reasonable set of parameters > on the command line. > > Doc > > PS This is getting so painful and with no end in sight I'm wondering > whether anyone has a Windows VC 7.1 build of 1_33_1 that I could grab > or they could send? Actually, I only want the debug multi-threaded > date-time library. I do agree the building Boost with MSVC (on Windows platform, of course) is pretty painful. Though I do not have the time the review the actual points here, I do consider it worth taking some time to review the installation doc. It took me 2 full days to do trial&error + research-from-the-web in order to build Boost the first time and to realize all the tricks necessary to make it work. I'll check back to office tomorrow to see if it is possible for me to post some pointers out of the Batch file I wrote to make my own life easier... Cheers, Freddie P.S. I do have a version of Boost 1.33.1 (as well as a Boost 1.34 CVS) built with MSVC71 + STLport 5.0. Do let me know if you want it.

1 0

How should I do to replace the constant pointer with shared_ptr?
by pegacorn＠jcom.home.ne.jp 26 Feb '06

26 Feb '06

How should I do to replace the constant pointer with shared_ptr? int main() { const int *ip = new int(1); *ip = 2; // NG ip = new int(2); // OK } How should I do to achieve the above-mentioned example by using shared_ptr? ---- pegacorn

2 2

Re: [Boost-users] [spirit] should be a very simple problem, but I'm stumped
by Todd Day 26 Feb '06

26 Feb '06

>> "ParmName: ParmValue" >> I'm looking for certain ParmNames, and I have to grab the associated >> ParmValue. >[Nat] Maybe the Spirit parser is the wrong place to get specific about >the ParmNames you're seeking? Maybe what you should do is parse *every* >item of that form, stuffing the pairs into a std::map. Then you can >extract from that map the specific items you want. Nat, thanks for the reply. In the course of writing a reply to you explaining what I'm really trying to do, I had an "aha" head-slapping moment. You know how it is... sometimes, just trying to explain a problem is enough to generate the answer. In reply to your quoted text above, yes, I should not be specific about which ParmNames I'm seeking at this level. I was actually using a map; I had just removed that from my example to make it a bit easier to understand. There is a bigger problem that the files I'm looking at may have mismatched single quotes in the parts of the file I don't care about. Like this random-text " random-text random-text In other words, to a parser looking for quoted text, these single quotes would appear as damaged, and the parser would still halt like it does now. The only thing I can be sure of is that "ParmName: ParmValue" will be properly quoted and non-damaged and consistent within itself. So it turns out my basic comprehension problem here is similar to one I had actually gone through when I was first learning pattern matching and regular expressions under Perl. I went and dug up some old Perl code of mine that did a similar search to see how I did it back then. My basic problem is thinking that the parser would continue grinding through non-matches just by putting a kleene-star on the front of it. Once I took this into account, a new strategy emerged. First, search for a single quote. Then try and see if there is a match at that point. If a match, move to just beyond the match, else just move to the next character. Repeat. The code is not as simple as my previous non-working version, since now I have to use iterators. This example also looks for multiple types of ParmNames. It comes out looking like the code below. I love that you can load up a complex map assignment right in the middle of the rule. map<string,string> smap; string key; typedef string::const_iterator iterator_t; typedef scanner<iterator_t> scanner_t; typedef rule<scanner_t> rule_t; typedef parse_info<iterator_t> parse_info_t; rule_t quote = ch_p('"'); rule_t colon = ch_p(':'); rule_t eat_all_non_quotes = *~ch_p('"'); rule_t parm_names = str_p(DWARF_DEVICE_NAME) | DWARF_DEVICE_TYPE | DWARF_DEVICE_SOFTWARE_VERSION | DWARF_DEVICE_COMMENTS; rule_t parm_string = quote >> parm_names[assign_a(key)] >> colon >> *blank_p >> eat_all_non_quotes[insert_at_a(smap, key)] >> quote; string str = "\"broken\" (text \"DeviceName: Altera in Controller\" (blah))"; iterator_t first = str.begin(); iterator_t last = str.end(); parse_info_t pi; while (first != last) { // skip to first quote character pi = parse(first, last, eat_all_non_quotes); first = pi.stop; // make sure we haven't gone past the end if (first != last) { // eat up any matching parms here pi = parse(first, last, parm_string); if (pi.hit) first = pi.stop; else first++; } } Thanks for the help, -todd-

1 0

member selector adapter
by Nico Galoppo 25 Feb '06

25 Feb '06

Hi, is there some utility (templated) adapter type class that I could use to construct an adapter such that an (associative) array of (pointers to) objects behaves like an (associative) array of a member variable of the objects? Something like class A { int val; }; std::map<int, shared_ptr<A> > container_type; container_type amap; shared_ptr<A> elem(new A()); amap[2] = elem; amap[4] = elem; amap[6] = elem; selector_adapter<container_type, &A::val> val_container(&amap); std::cout << val_container[4]; // should output amap[4]->val; --nico -- nico galoppo von borries @ address: 105 creel st., chapel hill comp. graphics phd. student @ north carolina, 27516 USA UNC, chapel hill @ phone: +1 (919) 962-1898 (office) @ +1 (919) 942-7609 (home) @ email: nico at cs dot unc dot edu @ homepage: http://www.cs.unc.edu/~nico --- debian linux :: vim powered

1 0

Boost build problems in Scratchbox, mkdir fails
by Rohit Chaudhri 25 Feb '06

25 Feb '06

Hello, I have recently started to work with Boost 1.33 on Linux. I have an X86 based Ubuntu Linux machine. I have installed Scratchbox 1.0 (www.scratchbox.org) on this machine for embedded linux development. I'm able to build boost on Ubuntu, however when I try to do the same within Scratchbox using an arm-gcc-glibc toolchain, the Boost build scripts fail because mkdir commands are failing. I was able to build Boost.Jam by manually creating the required directories within Scratchbox. Now while building Boost 1.33, I'm trying to build the Boost.Python module and it fails in a similar way on MKDIR. I want to fix this mkdir failure problem because I can't manually keep creating each required directory. Would appreciate it someone could help me out with this. Looking at the archives I've read emails that indicate Boost has been successfully built within Scratchbox. This is probably a problem in my Scratchbox environment, but don't know how to fix it. I'll post a similar email on Scratchbox forums too. Thanks in advance. Rohit

1 0

iterator_adaptor question
by Nico Galoppo 25 Feb '06

25 Feb '06

Hi, regarding iterator_adaptor<>, I've created a custom iterator over a map as below. Basically, it allows to iterate over map values without being worried with key values. Anyway, if I would want to do something like this: typedef map<int,int> map_type; typedef map_data_iterator<map_type::iterator> map_iterator; map_type map; map_iterator it = map_data_iterator(map.begin()); for (; it != map.end(); ++map) ... I'd have to add an equal method to the map_data_iterator class that takes the base type iterator, right? I tried to do so below, but it still complains about not being able to convert: binary '!=' : no operator found which takes a left-hand operand of type 'OpenTissue::DepthFirstTesselator<Types>::prism_iterator' (or there is no acceptable conversion) I know this is probably not the right thing(tm) to do , but I basically need to be able to do this comparison for backward compatibility with deprecated code. Thanks, --nico template <class Iterator> class map_data_iterator : public iterator_adaptor< map_data_iterator<Iterator>, Iterator, typename Iterator::value_type::second_type > { typedef typename map_data_iterator::iterator_adaptor_ super_t; typedef typename Iterator::value_type pair_type; typedef typename pair_type::second_type second_type; friend class iterator_core_access; public: map_data_iterator() {} // should be explicit, but removed to give OpenTissue backwards compatibility map_data_iterator(Iterator x) : super_t(x) {} template<class OtherIterator> map_data_iterator( map_data_iterator<OtherIterator> const& r , typename enable_if_convertible<OtherIterator, Iterator>::type* = 0 ) : super_t(r.base()) {} private: second_type & dereference() const { return this->base()->second; } // added to give support for comparison with base type iterators //bool equal(Iterator const& other) const //{ // return (this->base() == other); //} //bool equal(super_t const& other) const //{ // return (*this == other); //} }; -- nico galoppo von borries @ address: 105 creel st., chapel hill comp. graphics phd. student @ north carolina, 27516 USA UNC, chapel hill @ phone: +1 (919) 962-1898 (office) @ +1 (919) 942-7609 (home) @ email: nico at cs dot unc dot edu @ homepage: http://www.cs.unc.edu/~nico --- debian linux :: vim powered

2 3

Re: [Boost-users] [mpl] newbie question
by james.jones＠firstinvestors.com 24 Feb '06

24 Feb '06

Andy Little wrote: > What can I say? I acknowledge that mpl is a monumental piece of work . > Wonderful... but far from perfect. You can say, "Sorry, that was terribly rude of me. Here's a patch and some test code so that we can work together to make MPL even better." - James

3 2

Re: [Boost-users] Serialization : unregistered_cast & otherquestions
by RIVASSEAU Jean Noel 24 Feb '06

24 Feb '06

Thanks for all your help. I have decided to try to reorganize everything into small parts as you have said, in order to better understand. I am in the process of doing this, but I have already some remarks about your comments. I have chosen the organisation principle you have said: in the class.h, nothing about the serialization is present in serialization/class_serialization.hh : I have the serialization declaration code + some traits in serialization/class_serialization.cc : I have the serialization implementation code + BOOST_EXPORT The only thing where I have not followed your advice is the presence of BOOST_EXPORT on the class_serialization.hh rather than class_serialization.cc. If I put it on the header, since I have to include the header on test.cc, one instantation of something is done while encountering BOOST_EXPORT. Later while compiling class_serialization.cc, since it encounters BOOST_EXPORT one more time another instantiation occurs and I had problems with linking (gcc 3.4 reported multiple definitions of something). I have attached a small set of code that illustrates the problem. As the code is, it will fail to compile (at least on gcc 3.4). If you just remove BOOST_EXPORT from MObject_serialization.hh and put it into MObject_serialization.cc, everything works and the test passes. I'd like to get feedback on this - did I get everything right ?? Jean-Noël Ps: I now even have a clue about why the code failed in my old design, but I am waiting until I am more sure of myself... _____ De : boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] De la part de Robert Ramey Envoyé : jeudi 23 février 2006 17:44 À : boost-users(a)lists.boost.org Objet : Re: [Boost-users] Serialization : unregistered_cast & otherquestions Without actually seeing the code, its hard for me to give intelligent advice. Lucky for you (maybe) that's not going to inhibit me from speculating. Here is what I recommend for anyone making a very large program: a) extended_type_info_no_rtti presumes that all classes serialized as pointers have been exported. Should this not be the case, you'll get the error message indicated. Double check this. b) Serilaization traits should be in the header files so that they are not "missed" anytime something like "ar << x" is invoked. Given you're situation I would recommend a file structure like the following: class.hpp - without seriaiization like you have now. serialization/class.hpp - includes class.hpp. also includes BOOST_EXPORT and any other traits for this "class". serialization/class.cpp c - includes serialization/class.hpp and includes the actual serialization code. Also this should include code instantiation for the archives that you use. Look at demo_pimpl to see how this is done. All the above code should be organized into a library. The reason is that this will generate code for all the archives mentioned but your application may not use all the archives so putting the above code in a library and linking to it will mean that your application will always have what it actuallyuses but nothing it doesn't - avoids "code bloat". Note that in compiling code for the library make sure to specify "function level linking". Take the "least derived class" - that one at the top of the class hierarchy. Make a small test program similar to the tests in the serialization library. This should be a very small job. This code can be class_test.cpp. Run this test on all archives you use. When this test passes, do the same for the other classes until something fails. This might seem to be more work - believe me its not. It will a) guarentee that you make progress toward a robust program b) give you confidence that your program has minimum of hidden bugs c) permit you to re-run the tests automatically when you make future changes. d) should a problem arise with the serialization or other library, it will give a lot more information in order to be helpful. Robert Ramey Now, the problem is where to put the serialization code for these classes. If I just write them on the implementation file (the .cc) for the class, it does not work. At run time I have always errors telling me that either the class is not exported (unregistered_class exception) or an unregistered_cast happens. The only solution I have found is to put *ALL* serialization code into the same big .cc file. If I do just that, it works. However this file is becoming enormous and has to be recompiled every time I change only *one* of the class to be serialized. It is already taking a minute to compile on a fast machine, so I must really break it up into other parts. But everytime I do that everything stops working. Have you any ideas, Robert? I am using extended_type_info_no_rtti, this may be the cause of the problem... Jean-Noël Ps: I still have the std::string bug, which is also uncomprehensible for me. _____ _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

2 1

problem with boost_unit_test : BOOST_CLASS_TEST_CASE seems no the access instance at the right address, on Mac OS X, with gcc 4.0.1/2 with optimization level > 0
by Ananda Tallur 24 Feb '06

24 Feb '06

Hello, I would like to submit a strange problem we recently discovered, when using boost_unit_test. This problem only occurs : on Mac OS X, when using gcc 4 with any optimization level other than 0 (-O, -O1, -O2, etc...). I have tested with gcc 4.0.1 (build 5250 coming with Apple XCode 2.2.1), and also gcc 4.0.2 delivered by darwinports, and the problem is the same. On the other hand, it works perfectly on Linux, with gcc 4.0.2 and optimizations. The problem : it occurs when using BOOST_CLASS_TEST_CASE. BOOST_CLASS_TEST_CASE executes a test method of a class/struct instance, so that the class/struct attributes can be used in the test. With a very simple class, named SampleTest, having only -> one int attribute "a" -> a single test function : void sampleTest (), which only displays value of "a" -> a test declared in boost test suite : BOOST_CLASS_TEST_CASE ( & SampleTest::sampleTest, instance), with instance being shared pointer to a instance of sampleTest, instanciated with a given value of "a" passed as constructor argument. It does not work on Mac OS X, with the conditions described above. Everything happens as if BOOST_CLASS_TEST_CASE was not using the correct address in memory for accessing the instance attributes data. Furthermore, the value displayed for a is wrong, but always the same, it is not random at all, which seems to mean that there is a shift in the memory adress being accessed. Below is the complete sample program, for reproducing the problem : ---- file boost_unit_test_gcc4_pb_sample.cpp --- #include <iostream> #include <boost/test/unit_test.hpp> using boost::unit_test_framework::test_suite; using boost::unit_test_framework::test_case; using namespace std; class SampleTest { public: SampleTest (int val) : a (val) { } int a; void sampleTest () { std::cout << "a : " << a << std::endl; BOOST_CHECK_EQUAL (a, 12345); } }; test_suite* init_unit_test_suite( int argc, char* argv[] ) { test_suite* test= BOOST_TEST_SUITE( "Sample test" ); boost::shared_ptr<SampleTest> instance (new SampleTest (12345)); test->add (BOOST_CLASS_TEST_CASE ( & SampleTest::sampleTest, instance)); return test; } ---- end-of-file boost_unit_test_gcc4_pb_sample.cpp --- * Command used for compiling : BOOST_PATH=<path-to-your-boost-install> /usr/bin/g++-4.0 -O2 -I${BOOST_PATH}/include -L${BOOST_PATH}/lib - lboost_unit_test_framework boost_unit_test_gcc4_pb_sample.cpp -o boost_unit_test_gcc4_pb_sample When compiled when the above command, and running the program on Mac OS X : export DYLD_LIBRARY_PATH=${BOOST_PATH}/lib ./boost_unit_test_gcc4_pb_sample The result is the following : ---- Running 1 test case...a : 13691 boost_unit_test_gcc4_pb_sample.cpp(18): error in " SampleTest::sampleTest": check a == 12345 failed [13691 != 12345] *** 1 failure detected in test suite "Sample test" --- We see that value of "a" is wrong. When compiled without optimization (-O0), and running, the result is : ---- Running 1 test case...a : 12345 *** No errors detected ---- Everything is right in this case. Has anyone some experience using Boost unit_test framework on Mac OS X, using gcc 4, and already experienced this kind of problems ? Any help would be greatly appreciated ! Regards, Anand

1 0

[statechart] Unexpected events
by David Greene 24 Feb '06

24 Feb '06

I had assumed that if a state_machine definition did not mention any reaction for a particular event in a particular state, occurrence of that event in that state would be flagged as a runtime error. It appears that instead, the event is simply dropped. Can this behavior be changed? It would be tremendously helpful for debugging purposes. Adding an error state and a bunch of transitions into it seems like overkill, especially if the cross product between states and events is large but the "in- and out-degree" of states is small. -Dave

2 2

Re: [Boost-users] [statechart] Asynchronous Machines
by Gottlob Frege 24 Feb '06

24 Feb '06

> > Date: Wed, 22 Feb 2006 10:31:06 -0600 > From: David Greene <greened(a)obbligato.org> > Subject: Re: [Boost-users] [statechart] Asynchronous Machines > To: boost-users(a)lists.boost.org > Message-ID: <43FC91CA.8060801(a)obbligato.org> > Content-Type: text/plain; charset=us-ascii > > Gottlob Frege wrote: > > > Very long answer: More correctly the problem isn't really 'cache > > coherence' in the traditional meaning of cache coherency (which is that > > the cache, for your cpu, is consistent with main memory, etc), it is the > > order of memory reads and writes, and Mutex's are guaranteed to do > > whatever is necessary to make sure all queued reads are read before you > > get the mutex lock (ie they force a memory 'acquire' barrier) and they > > make sure all writes are written before the mutex is released (a > > 'release' memory barrier). > > I understand what you're saying and agree with you in that that's the > current way hardware and software is implemented in the vast majority > of cases. > > However, the concepts of serializing access and maintaining memory > consistency and conherence are orthogonal. There have been > architectures (in academia, mostly) that require explicit software > cache control, for example. One would have to include a cache flush in > your examples. The theory is that by separating concerns the programmer > (or compiler) has more freedom to loosen up implementations based > on weaker requirements of the application, thereby gaining performance. > > We're starting to see this much more in HPC systems, for example, where > there are a multitude of synchronization primitives available with > varying semantics that imply performance tradeoffs. Some machines > cache remote memory (often under software control), others don't. > > So I agree with you in the case of the typical machine architecture, > but it won't necessarily hold in the future. Obviously you understand the problems then. But I don't understand what you don't agree with - my explanation (obviously missing some details), or whether mutexes will work in the future? I'm saying that mutexes will always do whatever is necessary. For example, the pthreads spec tries very hard to describe itself in such a way so that it will 'just work' regardless of the underlying problems. And any other mutex/thread library will also work around the problems (flushing caches, doing whatever is necessary) or else not be worth using. P.S. do you have any links to some of the more esoteric synchronization primatives? I've been looking for variations on the typical acquire/release barriers as well as systems that don't have CAS, etc. All in the hopes of making at least a start on a useful atomics library. -Dave Thanks, Tony.

3 2

member traits
by Perry Smith 24 Feb '06

24 Feb '06

I am still on my adventure to implement a library for manipulating bits for device drivers. I want to be able to define a struct or a class that has the same layout as the hardware registers and also define bits for the registers. I want to have compile time checking to make sure that I use the bit definitions with the proper register. Underneath will be something maybe called "access" classes that would pull the data from the hardware device on the bus or write it back out. Sometimes that is just a simple pointer dereference but other times it is a kernel service call. I've worked on this for a couple of weeks (off and on) and I have something that is kinda working but does not do everything that I need. All that to lead up to this question: from what I've determined so far, all this boils down to giving what is equivalent to traits to members of a class or struct. Then I can give traits to the bit fields and have a compile time assert to make sure that the traits match. My only thought so far is to give each member its own unique type and then assign traits to those types. I am wondering if that seems like a viable path or if there are alternate (better?) ways. Thank you, Perry

1 0

Re: [Boost-users] Serialization : unregistered_cast & otherquestions
by RIVASSEAU Jean Noel 24 Feb '06

24 Feb '06

I forgot the code promised in last email sorry... _____ De : boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] De la part de Robert Ramey Envoyé : jeudi 23 février 2006 17:44 À : boost-users(a)lists.boost.org Objet : Re: [Boost-users] Serialization : unregistered_cast & otherquestions Without actually seeing the code, its hard for me to give intelligent advice. Lucky for you (maybe) that's not going to inhibit me from speculating. Here is what I recommend for anyone making a very large program: a) extended_type_info_no_rtti presumes that all classes serialized as pointers have been exported. Should this not be the case, you'll get the error message indicated. Double check this. b) Serilaization traits should be in the header files so that they are not "missed" anytime something like "ar << x" is invoked. Given you're situation I would recommend a file structure like the following: class.hpp - without seriaiization like you have now. serialization/class.hpp - includes class.hpp. also includes BOOST_EXPORT and any other traits for this "class". serialization/class.cpp c - includes serialization/class.hpp and includes the actual serialization code. Also this should include code instantiation for the archives that you use. Look at demo_pimpl to see how this is done. All the above code should be organized into a library. The reason is that this will generate code for all the archives mentioned but your application may not use all the archives so putting the above code in a library and linking to it will mean that your application will always have what it actuallyuses but nothing it doesn't - avoids "code bloat". Note that in compiling code for the library make sure to specify "function level linking". Take the "least derived class" - that one at the top of the class hierarchy. Make a small test program similar to the tests in the serialization library. This should be a very small job. This code can be class_test.cpp. Run this test on all archives you use. When this test passes, do the same for the other classes until something fails. This might seem to be more work - believe me its not. It will a) guarentee that you make progress toward a robust program b) give you confidence that your program has minimum of hidden bugs c) permit you to re-run the tests automatically when you make future changes. d) should a problem arise with the serialization or other library, it will give a lot more information in order to be helpful. Robert Ramey Now, the problem is where to put the serialization code for these classes. If I just write them on the implementation file (the .cc) for the class, it does not work. At run time I have always errors telling me that either the class is not exported (unregistered_class exception) or an unregistered_cast happens. The only solution I have found is to put *ALL* serialization code into the same big .cc file. If I do just that, it works. However this file is becoming enormous and has to be recompiled every time I change only *one* of the class to be serialized. It is already taking a minute to compile on a fast machine, so I must really break it up into other parts. But everytime I do that everything stops working. Have you any ideas, Robert? I am using extended_type_info_no_rtti, this may be the cause of the problem... Jean-Noël Ps: I still have the std::string bug, which is also uncomprehensible for me. _____ _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

using boost libs in a managed C++ dll (vc7.1)
by KonT 24 Feb '06

24 Feb '06

Hi, This is my second attempt to get some help on this issue... Can anyone provide a pointer to the steps required to using a boost lib in a managed C++ dll. I am using boost 1.33.1 with vc7.1. Boost libs were built with default options using bjam (bjam "-sTOOLS=vc-7_1" install). I am able to build a dll, but .net app using the dll crashes when it attempts to call code from the boost libs (in my case date). Building either managed or unmanaged static libs & using in a managed c++ app work fine, so I suspect that the problem is due to dll loader issues. I have tried linking with static & dynamically linked libs (CRT & boost), but the result is the same. I have built the dll with the /NO ENTRY switch & added manual calls to initialise the CRT. This removes the vc warnings, but the dll still cause the app to crash. Thanks in advance Kon Tantos

1 0

[Boost.date-time] Problem with leak with time_from_string? Incorrect use, or other problem?
by Stewart Loving-Gibbard 24 Feb '06

24 Feb '06

We have observed leaky behavior while using the Boost.date-time libraries, with time_from_string specifically. The leak is simple to replicate for us, on both Win32 (Visual Studio .NET 2005) and on Linux (GCC 3.x). This code snippet leaks for us, at a rate of about a MB every 10 seconds: while (true) { time_from_string("2002-01-20 23:59:59"); } As far as I can tell, ptime (what time_from_string returns) is an object that doesn't need to be deallocated with a Boost API function. So, why are we leaking here? Did we compile Boost incorrectly? Is there a way to link Boost that can trigger a leak? (from_iso_string() also appears to leak for us, by the way, while to_iso_string does not. It looks like time_from_string and to_iso_string are in the same neighborhood, so I'm betting they share the same fix.) Any and all help appreciated. This is a blocking issue for us. Stewart

3 4

Re: [Boost-users] [spirit] should be a very simple problem, but I'm stumped
by Nat Goodspeed 23 Feb '06

23 Feb '06

> -----Original Message----- > From: boost-users-bounces(a)lists.boost.org [mailto:boost-users- > bounces(a)lists.boost.org] On Behalf Of Todd Day > Sent: Thursday, February 23, 2006 9:35 AM > To: boost-users(a)lists.boost.org > Subject: [Boost-users] [spirit] should be a very simple problem,but I'm > stumped > > I have to look for strings of the form (including the > quotes) > "ParmName: ParmValue" > I'm looking for certain ParmNames, and I have to grab the associated > ParmValue. [Nat] Maybe the Spirit parser is the wrong place to get specific about the ParmNames you're seeking? Maybe what you should do is parse *every* item of that form, stuffing the pairs into a std::map. Then you can extract from that map the specific items you want.

1 0

Re: [Boost-users] [statechart] Asynchronous Machines
by Gottlob Frege 23 Feb '06

23 Feb '06

> Date: Thu, 23 Feb 2006 11:45:00 -0500 > From: Kim Barrett <kab(a)irobot.com> > Subject: Re: [Boost-users] [statechart] Asynchronous Machines > To: boost-users(a)lists.boost.org > Message-ID: <p06230901c02396579da8(a)[192.168.1.102]> > Content-Type: text/plain; charset="us-ascii" ; format="flowed" > > At 2:08 AM -0500 2/23/06, Gottlob Frege wrote: > >All in the hopes of making at least a start on a useful atomics library. > > Are you familiar with the atomic operations library at > http://www.hpl.hp.com/research/linux/atomic_ops > > Yep, thanks. That's probably the level I'm thinking of, but I'd just like to see a few more libraries and know what some of the edges are. Every library I see tends to say that they avoid handling the esoterics, and I would as well, but I'd like to know better what the esoterics are so that they can later be added without redoing everything, if at all possible.

1 0

Serialization : unregistered_cast & other questions
by RIVASSEAU Jean Noel 23 Feb '06

23 Feb '06

Hello First I would like to point out a bug in the documentation : void_register_cast <Derived, Base> MUST take two (bogus) arguments, so calling void_register_cast <Derived, Base> () as said in the documentation will not work. I had to look at the code to figure that out. Secondly, I am at the point where I am wondering if I should have started to use the BSL at all. The library is undoubtly useful but is plagued by strange things that must be done in order for it to run smoothly. I do not at all understand how the system works behind the scenes; I would not care if it would "just work" but this is not the case. My problem is: Ok, I have lots of classes, many of which need to be persistent. So, I have written serialization code for them. I have always written my code as non-intrusive, which means I have not used member functions, but templated functions. Now, the problem is where to put the serialization code for these classes. If I just write them on the implementation file (the .cc) for the class, it does not work. At run time I have always errors telling me that either the class is not exported (unregistered_class exception) or an unregistered_cast happens. The only solution I have found is to put *ALL* serialization code into the same big .cc file. If I do just that, it works. However this file is becoming enormous and has to be recompiled every time I change only *one* of the class to be serialized. It is already taking a minute to compile on a fast machine, so I must really break it up into other parts. But everytime I do that everything stops working. Have you any ideas, Robert? I am using extended_type_info_no_rtti, this may be the cause of the problem... Jean-Noël Ps: I still have the std::string bug, which is also uncomprehensible for me.

2 1

filter_iterator usage
by Nico Galoppo 23 Feb '06

23 Feb '06

Hi, I have a class with some custom iterators, I would like to add another custom iterator that is a 'filtered' version of the custom iterator. Something like this: class A { public: typedef boost::filter_iterator<predicate_type, custom_iterator> filtered_iterator; filtered_iterator begin() { predicate_type predicate = boost::bind(...); return boost::make_filter_iterator(predicate, custom_begin(), custom_end()); } } Unfortunately, the following code doesn't compile: A a; A::filtered_iterator it = a.begin(); Reason: cannot convert from 'boost::filter_iterator<Predicate,Iterator>' to 'const boost::filter_iterator<Predicate,Iterator>' I can give more compiler output if needed. Thanks! --nico -- nico galoppo von borries @ address: 105 creel st., chapel hill comp. graphics phd. student @ north carolina, 27516 USA UNC, chapel hill @ phone: +1 (919) 962-1898 (office) @ +1 (919) 942-7609 (home) @ email: nico at cs dot unc dot edu @ homepage: http://www.cs.unc.edu/~nico --- debian linux :: vim powered

2 1

[spirit] should be a very simple problem, but I'm stumped
by Todd Day 23 Feb '06

23 Feb '06

There has got to be a very very easy problem, but I've been knocking around for the better part of 12 hours in the docs and the examples and in google groups and the spirit list, and I've not made any progress. There must be some basic concept I'm totally missing out on. This is my first cut at using Spirit. I have the following, which is a simplified version of what I'm really after. Basically, I have to look for strings of the form (including the quotes) "ParmName: ParmValue" I'm looking for certain ParmNames, and I have to grab the associated ParmValue. This is what the code below is supposed to do. list<string> sl; rule<> parm_string = ch_p('"') >> str_p("DeviceName") >> ch_p(':') >> *blank_p >> (*~ch_p('"'))[push_back_a(sl)] >> ch_p('"'); rule<> r = *~ch_p('"') >> parm_string; parse(str, *r); This works just find when str = " (text \"DeviceName: Altera in Controller\" (blah))"; It properly returns to me only the value, which is Altera in Controller However, inserting the quoted word "broken" is enough to break it, like so str = "\"broken\" (text \"DeviceName: Altera in Controller\" (blah))"; In other words, it doesn't work if non-matching random quoted text is found. The problem in my rule r is the *~ch_p('"'). I thought this rule would mean, (a) eat all non-quoted characters until followed by (b) my parm match. But the rule really says, (a) eat all non-quoted characters, then stop working if it isn't followed by (b) my parm match. I think I might be screwed here since *anychar_p is greedy and I can't figure out how to otherwise skip over bad stuff. It still doesn't make sense to me that the simpler parse(str, *parm_string) does not work. I'm not sure why I have to specify the characters I want to skip if I've specified the characters I want to match. Perplexed, and thanking you profusely in advance for any help, -todd- PS - hopefully, any solution does not involve a skip rule. These don't seem to work when parsing file_iterators, which is what I'm really trying to do. I get compile errors that I don't get when using the simple string version of parse(). Also, don't skip rules run *after* a match has first been made?

1 0

how to get free space of a folder (or disk) using boost?
by hongxing 23 Feb '06

23 Feb '06

how to get free space of a folder (or disk) using boost? I am no using boost 1.33 in windows xp sp2 and SuSE Linux Enterprise Server sp2 thanks!

3 2

Serialization problem with polymorphic archives and std::string
by Michael Sperber 23 Feb '06

23 Feb '06

Hi there, I'm trying to convert a piece of code from templated archives to polymorphic ones, and am running into trouble when serializing std::string. Either I get an error message saying that std::string has no serialize member function, or I get the attached message. The relevant code is this: ---snip--- #include <boost/serialization/serialization.hpp> #include <boost/archive/polymorphic_iarchive.hpp> #include <boost/archive/polymorphic_oarchive.hpp> void mtime::serialize(boost::archive::polymorphic_iarchive& ar, const unsigned int file_version) { std::string iso; ar & boost::serialization::make_nvp("iso_time", iso); set_from_iso_string(iso); } void mtime::serialize(boost::archive::polymorphic_oarchive& ar, const unsigned int file_version) { std::string iso =3D to_iso_string(); ar & boost::serialization::make_nvp("iso_time", iso); } ---snip--- Am I missing something obvious? Are certain types not directly supported for serialization via polymorphic archives? Any help would be much appreciated. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla --=-=-= g++ -g -Wall -I /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1 -c -o mtime.o mtime.cpp /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/iserializer.hpp: In constructor `boost::archive::detail::iserializer<Archive, T>::iserializer() [with Archive = boost::archive::polymorphic_iarchive, T = std::basic_string<char, std::char_traits<char>, std::allocator<char> >]': /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/iserializer.hpp:146: instantiated from `static boost::archive::detail::iserializer<Archive, T>& boost::archive::detail::iserializer<Archive, T>::instantiate() [with Archive = boost::archive::polymorphic_iarchive, T = std::basic_string<char, std::char_traits<char>, std::allocator<char> >]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/iserializer.hpp:375: instantiated from `static void boost::archive::detail::load_non_pointer_type<Archive, T>::load_standard::invoke(Archive&, T&) [with Archive = boost::archive::polymorphic_iarchive, T = std::basic_string<char, std::char_traits<char>, std::allocator<char> >]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/iserializer.hpp:425: instantiated from `static void boost::archive::detail::load_non_pointer_type<Archive, T>::invoke(Archive&, T&) [with Archive = boost::archive::polymorphic_iarchive, T = std::basic_string<char, std::char_traits<char>, std::allocator<char> >]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/iserializer.hpp:572: instantiated from `void boost::archive::load(Archive&, T&) [with Archive = boost::archive::polymorphic_iarchive, T = std::basic_string<char, std::char_traits<char>, std::allocator<char> >]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/polymorphic_iarchive.hpp:127: instantiated from `void boost::archive::polymorphic_iarchive::load_override(const boost::serialization::nvp<T>&, int) [with T = std::string]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/interface_iarchive.hpp:76: instantiated from `Archive& boost::archive::detail::interface_iarchive<Archive>::operator>>(T&) [with T = const boost::serialization::nvp<std::string>, Archive = boost::archive::polymorphic_iarchive]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/interface_iarchive.hpp:83: instantiated from `Archive& boost::archive::detail::interface_iarchive<Archive>::operator&(T&) [with T = const boost::serialization::nvp<std::string>, Archive = boost::archive::polymorphic_iarchive]' mtime.cpp:36: instantiated from here /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/iserializer.hpp:115: error: incomplete type `boost::serialization::extended_type_info_null<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >' used in nested name specifier /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/oserializer.hpp: In constructor `boost::archive::detail::oserializer<Archive, T>::oserializer() [with Archive = boost::archive::polymorphic_oarchive, T = std::basic_string<char, std::char_traits<char>, std::allocator<char> >]': /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/oserializer.hpp:135: instantiated from `static boost::archive::detail::oserializer<Archive, T>& boost::archive::detail::oserializer<Archive, T>::instantiate() [with Archive = boost::archive::polymorphic_oarchive, T = std::basic_string<char, std::char_traits<char>, std::allocator<char> >]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/oserializer.hpp:264: instantiated from `static void boost::archive::detail::save_non_pointer_type<Archive, T>::save_standard::invoke(Archive&, const T&) [with Archive = boost::archive::polymorphic_oarchive, T = std::basic_string<char, std::char_traits<char>, std::allocator<char> >]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/oserializer.hpp:322: instantiated from `static void boost::archive::detail::save_non_pointer_type<Archive, T>::invoke(Archive&, const T&) [with Archive = boost::archive::polymorphic_oarchive, T = std::basic_string<char, std::char_traits<char>, std::allocator<char> >]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/oserializer.hpp:536: instantiated from `void boost::archive::save(Archive&, const T&) [with Archive = boost::archive::polymorphic_oarchive, T = std::basic_string<char, std::char_traits<char>, std::allocator<char> >]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/polymorphic_oarchive.hpp:128: instantiated from `void boost::archive::polymorphic_oarchive::save_override(const boost::serialization::nvp<T>&, int) [with T = std::string]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/interface_oarchive.hpp:78: instantiated from `Archive& boost::archive::detail::interface_oarchive<Archive>::operator<<(T&) [with T = const boost::serialization::nvp<std::string>, Archive = boost::archive::polymorphic_oarchive]' /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/interface_oarchive.hpp:86: instantiated from `Archive& boost::archive::detail::interface_oarchive<Archive>::operator&(T&) [with T = const boost::serialization::nvp<std::string>, Archive = boost::archive::polymorphic_oarchive]' mtime.cpp:46: instantiated from here /afs/informatik.uni-tuebingen.de/i386_fbsd54/boost-1.33.1/include/boost-1_33_1/boost/archive/detail/oserializer.hpp:108: error: incomplete type `boost::serialization::extended_type_info_null<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >' used in nested name specifier make: *** [mtime.o] Error 1 Compilation exited abnormally with code 2 at Wed Feb 22 11:56:36 --=-=-=--

4 3

How to bind the first of a pair?
by Meryl Silverburgh 23 Feb '06

23 Feb '06

I have a map with key is a pair: typedef map < pair<int, int>, string> pairMapString; pair<int, int> key(1,3); map[key] = "one"; How can I create a binary function using boost lamba which check the first value of the pair of the key of the map? void add(pairMapString;& myMap, int x) { iterator& itr = find_if(myMap.begin(), myMap.end(), bind(equal_to < int >(), bind(&BlockDataPairMap::value_type::first::value_type::first, _1 ) , x) ); }

6 11

filter_iterator and bind
by Nico Galoppo 23 Feb '06

23 Feb '06

Hi, I'm having trouble getting make_filter_iterator and bind to work together nicely: ------------------------------------------------------------------------------- boost::function<bool (const node_type&)> is_constraint; is_constraint = boost::bind(&node_type::IsConstraint, _1); boost::make_filter_iterator(is_constraint, ab.begin(), ab.end()); // ERROR: does not compile boost::make_filter_iterator(boost::bind(&node_type::IsConstraint, _1), ab.begin(), ab.end()); // compiles ------------------------------------------------------------------------------- Note that ab.begin()/ab.end() return iterators to containers of shared pointers. See below for compiler errors. What I would like to do, in the end, is something like this: ------------------------------------------------------------------------------- typedef boost::filter_iterator<boost::function<bool (const node_type&)>, articulated_model_type::node_df_traversal_iterator> joint_iterator; joint_iterator first = boost::make_filter_iterator(boost::bind(&node_type::IsConstraint, _1), ab.begin(), ab.end()); ------------------------------------------------------------------------------- Unfortunately, this doesn't compile either. I want an explicit handle to the interator (first), because I'd like to do a normal for loop like this: for(joint_iterator joint = first; joint != last; ++joint) { ... } Again, compile errors are below. Thanks for the help. --nico d:\dev\boost_1_33_1\boost\iterator\filter_iterator.hpp(100) : error C2664: 'boost::function1<R,T0,Allocator>::result_type boost::function1<R,T0,Allocator>::operator ()(T0) const' : cannot convert parameter 1 from 'Hybrid::Graph<node_traits>::const_node_ptr' to 'const Hybrid::Node<graph_type_,node_traits> ' with [ R=bool, T0=const Hybrid::Node<Hybrid::Graph<ArticulatedModelNodeTraits<MyTypes>>::graph_type,ArticulatedModelNodeTraits<MyTypes>> , Allocator=std::allocator<void> ] and [ node_traits=ArticulatedModelNodeTraits<MyTypes> ] and [ graph_type_=Hybrid::Graph<ArticulatedModelNodeTraits<MyTypes>>::graph_type, node_traits=ArticulatedModelNodeTraits<MyTypes> ] Reason: cannot convert from 'Hybrid::Graph<node_traits>::const_node_ptr' to 'const node_type' with [ node_traits=ArticulatedModelNodeTraits<MyTypes> ] No constructor could take the source type, or constructor overload resolution was ambiguous d:\dev\boost_1_33_1\boost\iterator\filter_iterator.hpp(99) : while compiling class-template member function 'void boost::filter_iterator<Predicate,Iterator>::satisfy_predicate(void)' with [ Predicate=boost::function<bool (const node_type &)>, Iterator=Hybrid::Graph<ArticulatedModelNodeTraits<MyTypes>>::node_df_traversal_iterator ] d:\dev\Hybrid\Tests\Graph\main.cpp(645) : see reference to class template instantiation 'boost::filter_iterator<Predicate,Iterator>' being compiled with [ Predicate=boost::function<bool (const node_type &)>, Iterator=Hybrid::Graph<ArticulatedModelNodeTraits<MyTypes>>::node_df_traversal_iterator ] ====================================================================================== :\dev\Hybrid\Tests\Graph\main.cpp(646) : error C2440: 'initializing' : cannot convert from 'boost::filter_iterator<Predicate,Iterator>' to 'boost::filter_iterator<Predicate,Iterator>' with [ Predicate=boost::_bi::bind_t<bool,boost::_mfi::cmf0<bool,ConstraintNodeTraits>,boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>, Iterator=Hybrid::Graph<ArticulatedModelNodeTraits<MyTypes>>::node_df_traversal_iterator ] and [ Predicate=boost::function<bool (const node_type &)>, Iterator=Hybrid::Graph<ArticulatedModelNodeTraits<MyTypes>>::node_df_traversal_iterator ] No constructor could take the source type, or constructor overload resolution was ambiguous -- nico galoppo von borries @ address: 105 creel st., chapel hill comp. graphics phd. student @ north carolina, 27516 USA UNC, chapel hill @ phone: +1 (919) 962-1898 (office) @ +1 (919) 942-7609 (home) @ email: nico at cs dot unc dot edu @ homepage: http://www.cs.unc.edu/~nico --- debian linux :: vim powered

7 15

date-time library question
by Albert Wessel 23 Feb '06

23 Feb '06

Hello, How can I get a localized date string with the boost date / time library? To illustrate: date d(2005,06,25); string sometext=to_simple_string(d); This returns: 2005-Jun-25 However, I want to be able to define my own formats.I can get the localization example to work and format my stuff on stdout, but nowhere it tells anything about how to fill in a string using localized settings. Thank you, Albert

4 5

Re: [Boost-users] [bind] Generic loop with generic algorithmchickenand egg signature problem
by Nat Goodspeed 23 Feb '06

23 Feb '06

From: boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Antonio Piccolboni Sent: Wednesday, February 22, 2006 7:15 PM To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] [bind] Generic loop with generic algorithmchickenand egg signature problem Thanks Peter, but it does not. Error message bind_test.cpp: In function 'int main()': bind_test.cpp:33: error: no matching function for call to 'bind(<unknown type>, const boost::lambda::lambda_functor<boost::lambda::placeholder<1> >&, const boost::lambda::lambda_functor<boost::lambda::placeholder<2> >&, int)' This also dooms my theory of why this doesn't work since the explicit instantiation of the accumulate template should provide the necessary information. On 2/22/06, Peter Dimov <pdimov(a)mmltd.net> wrote: Antonio Piccolboni wrote: [...] > int main() { > std::vector<int> d; > std::vector<std::vector<int> > s; > loop_func(s.begin(), s.end (), d.begin(), > BinFunc()); //flies with gcc > loop_func(s.begin(), s.end(), d.begin(), > bind<int>(std::accumulate, _1, _2, 0.0)); //does not bind( std::accumulate< std::vector<int>::iterator, int >, _1, _2, 0 ) [Nat] Umm, parentheses() after the std::accumulate template params?

1 0

[bind] Generic loop with generic algorithm chicken and egg signature problem
by Antonio Piccolboni 23 Feb '06

23 Feb '06

I have a vector of vectors or some nested data structure of that sort. I want to loop over the outer structure and summarize the inner structure, like taking averages of all the vectors or what not. Once I saw that in the code three times I thought it was time to abstract it out. So the plan was to have a generic loop function that takes a functor type for the action to perform inside the loop. So far so good. In many instances that action is a standard algorithm or composition thereof, so why not use functors like those returned by bind(accumulate, _1, _2, 0) instead of writing little polluting classes like BinFunc below? But the compiler is at a loss guessing the types, and it looks to me like it is for a good reason, because to instantiate the accumulate template it has to know the precise signature of my loop function and the converse too. Can the lambda experts shed light on this? It seems a quite natural use case. Thanks Antonio PS: in an ideal world the following example can be done combining transform call_begin and call_end, but that an whole different story #include <boost/lambda/lambda.hpp> #include <boost/lambda/bind.hpp> #include <vector> #include <numeric> #include <functional> using namespace boost::lambda; template<class Func, class NestedIt, class It> void loop_func(NestedIt start, NestedIt stop, It dest, Func f) { for(;start < stop; start++, dest++) { *dest = f(start->begin(), start->end()); } } class BinFunc: public std::binary_function<std::vector<int>::iterator, std::vector<int>::iterator, int> { public: int operator() (std::vector<int>::iterator b, std::vector<int>::iterator e) { return accumulate(b,e,0); } }; int main() { std::vector<int> d; std::vector<std::vector<int> > s; loop_func(s.begin(), s.end (), d.begin(), BinFunc()); //flies with gcc loop_func(s.begin(), s.end(), d.begin(), bind<int>(std::accumulate, _1, _2, 0.0)); //does not } bind_test.cpp: In function 'int main()': bind_test.cpp:32: error: invalid initialization of reference of type 'const int&' from expression of type '<unknown type>' /usr/include/boost/lambda/detail/bind_functions.hpp:532: error: in passing argument 1 of 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lambda::action<4, boost::lambda::function_action<4, boost::lambda::detail::unspecified> >, typename boost::lambda::detail::bind_tuple_mapper<const Arg1, const Arg2, const Arg3, const Arg4, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type>::type> > boost::lambda::bind(const Arg1&, const Arg2&, const Arg3&, const Arg4&) [with Arg1 = int, Arg2 = boost::lambda::lambda_functor<boost::lambda::placeholder<1> >, Arg3 = boost::lambda::lambda_functor<boost::lambda::placeholder<2> >, Arg4 = double]'

2 3

Re: [Boost-users] Program option parsing
by Merrill Cornish 22 Feb '06

22 Feb '06

If you don't want a --help or -h on the command line, could you output the help text is the user doesn't provide exactly two positional arguments? Merrill

2 1

Program option parsing
by Calderon Hector 22 Feb '06

22 Feb '06

Hi all, I'm using <boost/program_options.hpp> to parse a command line. It has only two positional arguments. However, I don't see how to generate the help without the name of the variable. I'd like to get the following output: MyProg.exe Param1 [Param2] where Param1 is the first parameter Param2 (=200) is the second parameter (optional) Any ideas would be appreciated. Hector C. ---------------------------------- --------------------------------- Yahoo! Mail Use Photomail to share photos without annoying attachments.

1 0

[statechart] Asynchronous Machines
by David Greene 22 Feb '06

22 Feb '06

If I have an asynchronous state machine running in another thread and I send it an event, is there any way to have the sending thread block until the event is processed? I need to use an asynchoronous machine because the rest of my app is threaded but yet there are points where I must synchronize to know the machine is in a certain state before moving on. >From the documentation it seems like passing zero to FifoWorker::operator() (via fifo_scheduler::operator()) will do the trick, but I'm not sure. I've created a non-blocking asynchronous machine because the thread calling fifo_scheduler::operator() should not block if the queue is empty. It should process all events in the queue and return. Have I got that all correct? -Dave

3 12

Re: [Boost-users] [statechart] Asynchronous Machines
by Gottlob Frege 22 Feb '06

22 Feb '06

> > Date: Tue, 21 Feb 2006 19:03:11 -0600 > From: David Greene <greened(a)obbligato.org> > Subject: Re: [Boost-users] [statechart] Asynchronous Machines > To: boost-users(a)lists.boost.org > Message-ID: <43FBB84F.70305(a)obbligato.org> > Content-Type: text/plain; charset=us-ascii > > > Nowadays both CPUs tend to have caches. Whether or not the cache > > contents is guaranteed to be written back to the main memory when thread > > A returns depends on the architecture of your hardware. IIRC, on X86 > > architectures there is such a guarantee. On other architectures you > > might need to use mutexes or a similar concept to guarantee that thread > > B sees the updates of thread A. > > Mutexes don't effect cache coherence. Likely there will have to be > calls to special intrinsics depending on the architecture. Short Answer: Yes they do. Very long answer: More correctly the problem isn't really 'cache coherence' in the traditional meaning of cache coherency (which is that the cache, for your cpu, is consistent with main memory, etc), it is the order of memory reads and writes, and Mutex's are guaranteed to do whatever is necessary to make sure all queued reads are read before you get the mutex lock (ie they force a memory 'acquire' barrier) and they make sure all writes are written before the mutex is released (a 'release' memory barrier). The important example is this: Thread 1: bool object_is_contstructed = false; Object object(17); // construct it object_is_constructed = true; Thread 2: if (object_is_constructed) { use_object(object); } else dont_use_object(); // really we would probably wait, but this is an example Problem 1 (Thread 1) object_is_constructed may be set to true (in shared memory) BEFORE all the constructed bytes of object are seen in shared memory. This has NOTHING to do with compiler optimizations or 'volatile' or the OS or other stuff. It is the hardware. (And really, whether you think of this as cache coherency or read/write order or whatever doesn't matter much, as long as the rules and concepts make sense.) Problem 2: EVEN IF object_is_constructed is written AFTER object is constructed, Thread 2 might read object BEFORE reading object_is_constructed! (Similar stuff. Basically, think about how the processor wants to optimize the order of memory reads/writes so as to not jump around memory too much - similar to how disk drivers try to optimize read/writes to avoid seeks.) So what to do? In a sense, flush the reads/writes similar to what you would need to do for harddrives. Any and all thread primitives will do this for you implicitly. POSIX threads (pthreads) actually try to document this, but you can assume it for any thread library otherwise the library is essentially useless. So use locks. Look are writing first: lock mutex, write object, write object_is_constructed release a mutex. note that in whatever order object and is_constructed are actually written to main memory, they both are written before the release. ***the order of those writes CANNNOT come after the order of the writes inside the mutex*** because of the 'release' memory barrier inside the mutex release. Now on reading, lock mutex read is_constructed read object release mutex So the read of object might still come before the read of is_constructed, but you CANNOT read either of them before the read of the mutex. And the mutex was written in order, so everything stays in order. To take it a step further, if you had barrier control, you COULD do away with the mutex (if you wanted to spin lock, or just skip using 'object' as in the example) as so: Thread 1: write object release barrier write is_constructed the barrier prevents the object write to move below the barrier. Thread 2: read is_constructed (into temp) acquire barrier if (temp) read object the acquire barrier prevents the read of 'objecrt' to move above the acquire. Note that, for example, Win32 now has explicit barrier versions of its Interlocked functions ie InterlockedIncrementAcquire, etc. (The old ones, it can be assumed, did 'full' barriers.) Mac OSX has similar functions. x86 never re-orders writes, but it can re-order reads. The IA64 *spec* says it can reorder both, although the processor doesn't seem to. Conventional wisdom is that the spec is explicitly 'looser' so that they can loosen the implementation in the future. Oh, also, the are other refinements on the barriers - think of the combinations - are we only concerned about the order of reads w.r.t. other reads, writes with other writes? What about the order of reads vs writes, etc? Thus back to the short answer: mutexes et al, magically do what is necessary to make it work. Tony. P.S. hope I got all that straight. It is easy to mix up the names of the barriers relative to their direction and reads vs writes, etc. I tend to just remember the general principles.

2 1

[BGL]Repost? Problems in the shortest pair algorithms.
by Peter Gerell 22 Feb '06

22 Feb '06

Hi, sorry if this is a repost. I made this post through the nntp at gmane, but it never appeared in my mail. I have reported some problems with the johnson_all_pairs_shortest_paths and floyd_warshall_all_pairs_shortest_paths algorithms. What is the correct way to report these problems. I made some posts to the list last week, but didn't get any response. Perhaps this should go on the developer mailing list instead? However, the problems I have noticed are: Floyd-Warshall: 1. std::min is used instead of the functor passed to as teh distance_compare parameter at several places 2. The distance map is initialized with 0 instead of zero. Johnson: 3. std::numeric_limits<DT>::max() is used instead of the distance_inf parameter. 4. The distance_combine and distance_compare parameters are not used. The bellman_ford_shortest_paths algorithm is called with std::less and closed_plus. Thanks Peter

2 2

mutexes : Is this thread-safe ?
by Dhanvi Kapila 22 Feb '06

22 Feb '06

Hi : I have this piece of code for mutex operations. is this code thread-safe ? I plan to use this code in threads... ------------------------------------ class BoostMutexLock { public : void lock() { lk = new boost::mutex::scoped_lock(global_mutex); } void unlock() { delete lk; } BoostMutexLock() : lk( 0 ) { } ~BoostMutexLock() { } private: boost::mutex global_mutex; boost::mutex::scoped_lock* lk; }; ------------------------------------------------------ I appreciate all the help.. How do I know to check for thread-safety in a code ? Are there any documents? I have checked online and have some links, but havent found documents which provide examples and explain.. such a document would be really useful. Thanks... Dhanvi

7 13

newbie: including boost lib in a managed C++ dll (vc71)
by KonT 22 Feb '06

22 Feb '06

Hi, I have only recently started using boost. platform win2k, winxp dev vs.net 2003 (vc7.1) I have downloaded the src & built boost libs using bjam. I have had no problems using them in std C++ apps. However, I have struck a prob in a case which has involved replacing my date/time code with boost::gregorian classes. I build an umanaged static lib which uses the boost date time stuff. The lib has been used successfully in a test harness (std C++ console app). This lib is then included in a manged C++ dll which exposes a std CLI interface, hiding the native c++ stuff. The managed dll is then included in a C# app. before I converted to boost, the whole arrangement worked ok. However now the C# app crashes when it calls code which jumps into the boost date lib. I have attempted to read up on the issue involved in having such a structure, & following advice from the ms on line help I have added a 'ManagedWrapper' class to the managed c++ dll (as per MS docs) which provides static methods to initialise the C++ run time lib. public __gc class ManagedWrapper { public: static int minitialize() { int retval = 0; try { __crt_dll_initialize(); } catch(System::Exception* e) { Console::WriteLine(e); retval = 1; } return retval; } static int mterminate() { int retval = 0; try { __crt_dll_terminate(); } catch(System::Exception* e) { Console::WriteLine(e); retval = 1; } return retval; } }; The C# calls the appropriate methods in Main static void Main(string[] args) { ManagedWrapper.minitialize(); TestFs(); TestAcct(); TestAccMgr(); ManagedWrapper.mterminate(); } At this point I think that I need to initialise statics within the boost lib. Does anyone have any advice on how to solve this issue (even if it means totally rearranging the dll wrapping a lib structure). Thanks Kon Tantos

1 0

How to use bind library to de-reference a pointer
by Meryl Silverburgh 21 Feb '06

21 Feb '06

I have a list of A pointers: vector <A*> aVector; And i have a function which takes a A reference. void myFunc(A& a); how can I loop thru aVector to call myFunct? for_each (aVector;.begin(), aVector;.end(), bind (&myFunc, _1)); // does not compile. Thanks for any help.

4 7

[Serialization]: How to get export to work
by sui tam 21 Feb '06

21 Feb '06

Hi, I run into compilation error with the Intel compiler for doing serialization traits and tracking. I have the following code which does serialization of virtual base classes : #include <boost/archive/text_iarchive.hpp> #include <boost/archive/text_oarchive.hpp> #include <boost/serialization/utility.hpp> #include <boost/serialization/split_member.hpp> #include <boost/serialization/tracking.hpp> #include <boost/serialization/nvp.hpp> #include <boost/serialization/export.hpp> typedef unsigned _int64 ut8; typedef unsigned char otext; typedef unsigned int ut4; class Object { private: void* _ojhi; ut8 _seqno; public: template<class Archive> void save(Archive &ar, const unsigned int /* file version */) const { ar << BOOST_SERIALIZATION_NVP(_ojhi) << BOOST_SERIALIZATION_NVP(_seqno); } template<class Archive> void load(Archive& ar, const unsigned int /* file version */) { ar >> BOOST_SERIALIZATION_NVP(_ojhi) >> BOOST_SERIALIZATION_NVP(_seqno); } BOOST_SERIALIZATION_SPLIT_MEMBER() protected: Object(const Object& ) : _ojhi(NULL), _seqno(0) {} Object(const char *num=NULL, int is_stub=1) : _ojhi(NULL), _seqno(0) {} virtual ~Object() {} void operator=(const Object& ) {} }; BOOST_IS_ABSTRACT(Object) BOOST_CLASS_TRACKING(Object, track_always) class EModule { public: class IInterface : public virtual Object { private: static const otext * _Desc; static const ut4 _pkgIndex; static const ut4 _clsIndex; protected: IInterface() {} IInterface(const IInterface&) {} public: template<class Archive> void save(Archive& ar, const unsigned int /*file_version*/) const { ar << const_cast(otext *> (_Desc) << const_cast<ut4> (_pkgIndex) << const_cast<ut4> (_clsIndex); ar << BOOST_SERIALIZATION_BASE_OBJECT_NVP(Object); } template<class Archive> void load(Archive& ar, const unsigned int /*file_version*/) const { ar << const_cast(otext *> (_Desc) << const_cast<ut4> (_pkgIndex) << const_cast<ut4> (_clsIndex); ar << BOOST_SERIALIZATION_BASE_OBJECT_NVP(Object); } }; }; BOOST_CLASS_TRACKING(EModule::IInterface, track_always) class CModule { public: class CInterface : public virtual EModule::IInterface, public virtual Object { private: static const otext * _Desc; static const ut4 _pkgIndex; static const ut4 _clsIndex; protected: CInterface() {} CInterface(const CInterface&) {} public: template <class Archive> void save(Archive& ar, const unsigned int /* file_version */) const { ar << const_cast<otext *> (_Desc) << const_cast<ut4> (_pkgIndex) << const_cast<ut4> (_clsIndex); ar << BOOST_SERIALIZATION_BASE_OBJECT_NVP(EModule::IInterface); ar << BOOST_SERIALIZATION_BASE_OBJECT_NVP(Object); } template <class Archive> void load(Archive & ar, const unsigned int /* file_version */) { ar >> const_cast<otext *> (_Desc) >> const_cast<ut4> (_pkgIndex) >> const_cast<ut4> (_clsIndex); ar >> BOOST_SERIALIZATION_BASE_OBJECT_NVP(EModule::IInterface); ar >> BOOST_SERIALIZATION_BASE_OBJECT_NVP(Object); } BOOST_SERIALIZATION_SPLIT_MEMBER() virtual ~CInterface() {} }; }; BOOST_CLASS_EXPORT(CModule::CInterface) I followed strictly from the documentation. Is there a way I can get it compiled? Enclosed please find the compile log. --------------------------------- Yahoo! Mail Use Photomail to share photos without annoying attachments. W:\WUTemp\Myfolder\xsolapi>ecl /c /Fotest1.obj /G2 /Wp64 /GR /GX /Qms /O1 /G2 /nologo /Zl /G2 /DWIN64 /D_WIN64 /DWIN_NT /DWIN32COMMON /MD /DSS_64BIT_SERVER /D_IA64_=1 -DOS_STL_ASSERT /Zm300 /Ob0 test1.cpp test1.cpp v:\temp\boost_1_33_0\boost/archive/detail/oserializer.hpp(566): error: incomplete type is not allowed BOOST_STATIC_ASSERT(check_tracking<T>::value); ^ detected during: instantiation of "void boost::archive::save(Archive &__ptr64, T &__ptr64) [with Archive=boost::archive::text_oarchive, T=otext={unsigned char} *__ptr64]" at line 78 of "v:\temp\boost_1_33_0\boost/archive/basic_text_oarchive.hpp" instantiation of "void boost::archive::basic_text_oarchive<Archive>::save_override(T &__ptr64, int) [with Archive=boost::archive::text_oarchive, T=otext={unsigned char} *__ptr64]" at line 85 of "v:\temp\boost_1_33_0\boost/archive/detail/interface_oarchive.hpp" instantiation of "Archive &__ptr64 boost::archive::detail::interface_oarchive<Archive>::operator<<(T &__ptr64) [with Archive=boost::archive::text_oarchive, T=otext={unsigned char} *__ptr64]" at line 92 of "test1.cpp" instantiation of "void CModule::CInterface::save(Archive &__ptr64, const unsigned int ) const [with Archive=boost::archive::text_oarchive]" at line 93 of "v:\temp\boost_1_33_0\boost/serialization/access.hpp" instantiation of "void boost::serialization::access::member_save(Archive &__ptr64, T &__ptr64, const unsigned int ) [with Archive=boost::archive::text_oarchive, T=const CModule::CInterface ]" at line 43 of "v:\temp\boost_1_33_0\boost/serialization/split_member.hpp" [ 15 instantiation contexts not shown ] instantiation of class "boost::archive::detail::export_generator<T, ASeq> [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" implicit definition of "const boost::archive::detail::export_generator<CModule::CInterface, boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>> boost::archive::detail::export_generator<T, ASeq>::instance [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "const void *__ptr64 boost::archive::detail::export_instance<T, ASeq>::not_abstract::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 210 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instance<T, ASeq>::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 219 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instantiate(T &__ptr64, ASeq &__ptr64) [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" v:\temp\boost_1_33_0\boost/serialization/access.hpp(109): error: expression must have class type t.serialize(ar, file_version); ^ detected during: instantiation of "void boost::serialization::access::serialize(Archive &__ptr64, T &__ptr64, const unsigned int ) [with Archive=boost::archive::text_oarchive, T=unsigned char]" at line 81 of "v:\temp\boost_1_33_0\boost/serialization/serialization.hpp" instantiation of "void boost::serialization::serialize(Archive &__ptr64, T &__ptr64, const unsigned int ) [with Archive=boost::archive::text_oarchive, T=unsigned char]" at line 140 of "v:\temp\boost_1_33_0\boost/serialization/serialization.hpp" instantiation of "void boost::serialization::serialize_adl(Archive &__ptr64, T &__ptr64, const unsigned int ) [with Archive=boost::archive::text_oarchive, T=unsigned char]" at line 224 of "v:\temp\boost_1_33_0\boost/archive/detail/oserializer.hpp" instantiation of "boost::archive::detail::pointer_oserializer<T, Archive>::pointer_oserializer() [with T=unsigned char, Archive=boost::archive::text_oarchive]" at line 189 of "v:\temp\boost_1_33_0\boost/archive/detail/oserializer.hpp" instantiation of class "boost::archive::detail::pointer_oserializer<T, Archive> [with T=unsigned char, Archive=boost::archive::text_oarchive]" at line 189 of "v:\temp\boost_1_33_0\boost/archive/detail/oserializer.hpp" [ 28 instantiation contexts not shown ] instantiation of class "boost::archive::detail::export_generator<T, ASeq> [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" implicit definition of "const boost::archive::detail::export_generator<CModule::CInterface, boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>> boost::archive::detail::export_generator<T, ASeq>::instance [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "const void *__ptr64 boost::archive::detail::export_instance<T, ASeq>::not_abstract::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 210 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instance<T, ASeq>::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 219 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instantiate(T &__ptr64, ASeq &__ptr64) [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" test1.cpp(92): error: the type in a const_cast must be a pointer, reference, or pointer to member to an object type ar << const_cast<otext *> (_Desc) << const_cast<ut4> (_pkgIndex) << const_cast<ut4> (_clsIndex); ^ detected during: instantiation of "void CModule::CInterface::save(Archive &__ptr64, const unsigned int ) const [with Archive=boost::archive::text_oarchive]" at line 93 of "v:\temp\boost_1_33_0\boost/serialization/access.hpp" instantiation of "void boost::serialization::access::member_save(Archive &__ptr64, T &__ptr64, const unsigned int ) [with Archive=boost::archive::text_oarchive, T=const CModule::CInterface ]" at line 43 of "v:\temp\boost_1_33_0\boost/serialization/split_member.hpp" instantiation of "void boost::serialization::detail::member_saver<Archive, T>::invoke(Archive &__ptr64, const T &__ptr64, const unsigned int ) [with Archive=boost::archive::text_oarchive, T=CModule::CInterface]" at line 69 of "v:\temp\boost_1_33_0\boost/serialization/split_member.hpp" instantiation of "void boost::serialization::split_member(Archive &__ptr64, T &__ptr64, const unsigned int ) [with Archive=boost::archive::text_oarchive, T=CModule::CInterface]" at line 103 instantiation of "void CModule::CInterface::serialize(Archive &__ptr64, const unsigned int ) [with Archive=boost::archive::text_oarchive]" at line 109 of "v:\temp\boost_1_33_0\boost/serialization/access.hpp" [ 12 instantiation contexts not shown ] instantiation of class "boost::archive::detail::export_generator<T, ASeq> [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" implicit definition of "const boost::archive::detail::export_generator<CModule::CInterface, boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>> boost::archive::detail::export_generator<T, ASeq>::instance [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "const void *__ptr64 boost::archive::detail::export_instance<T, ASeq>::not_abstract::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 210 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instance<T, ASeq>::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 219 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instantiate(T &__ptr64, ASeq &__ptr64) [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" test1.cpp(92): error: the type in a const_cast must be a pointer, reference, or pointer to member to an object type ar << const_cast<otext *> (_Desc) << const_cast<ut4> (_pkgIndex) << const_cast<ut4> (_clsIndex); ^ detected during: instantiation of "void CModule::CInterface::save(Archive &__ptr64, const unsigned int ) const [with Archive=boost::archive::text_oarchive]" at line 93 of "v:\temp\boost_1_33_0\boost/serialization/access.hpp" instantiation of "void boost::serialization::access::member_save(Archive &__ptr64, T &__ptr64, const unsigned int ) [with Archive=boost::archive::text_oarchive, T=const CModule::CInterface ]" at line 43 of "v:\temp\boost_1_33_0\boost/serialization/split_member.hpp" instantiation of "void boost::serialization::detail::member_saver<Archive, T>::invoke(Archive &__ptr64, const T &__ptr64, const unsigned int ) [with Archive=boost::archive::text_oarchive, T=CModule::CInterface]" at line 69 of "v:\temp\boost_1_33_0\boost/serialization/split_member.hpp" instantiation of "void boost::serialization::split_member(Archive &__ptr64, T &__ptr64, const unsigned int ) [with Archive=boost::archive::text_oarchive, T=CModule::CInterface]" at line 103 instantiation of "void CModule::CInterface::serialize(Archive &__ptr64, const unsigned int ) [with Archive=boost::archive::text_oarchive]" at line 109 of "v:\temp\boost_1_33_0\boost/serialization/access.hpp" [ 12 instantiation contexts not shown ] instantiation of class "boost::archive::detail::export_generator<T, ASeq> [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" implicit definition of "const boost::archive::detail::export_generator<CModule::CInterface, boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>> boost::archive::detail::export_generator<T, ASeq>::instance [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "const void *__ptr64 boost::archive::detail::export_instance<T, ASeq>::not_abstract::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 210 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instance<T, ASeq>::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 219 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instantiate(T &__ptr64, ASeq &__ptr64) [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" v:\temp\boost_1_33_0\boost/archive/detail/oserializer.hpp(459): error: expression must be a pointer to a complete object type const basic_pointer_oserializer * bpos_ptr = register_type(ar, * t); ^ detected during: instantiation of "void boost::archive::detail::save_pointer_type<Archive, TPtr>::invoke(Archive &__ptr64, const TPtr ) [with Archive=boost::archive::text_oarchive, TPtr=void *__ptr64]" at line 535 instantiation of "void boost::archive::save(Archive &__ptr64, const T &__ptr64) [with Archive=boost::archive::text_oarchive, T=void *__ptr64]" at line 78 of "v:\temp\boost_1_33_0\boost/archive/basic_text_oarchive.hpp" instantiation of "void boost::archive::basic_text_oarchive<Archive>::save_override(T &__ptr64, int) [with Archive=boost::archive::text_oarchive, T=void *const __ptr64 ]" at line 85 of "v:\temp\boost_1_33_0\boost/archive/detail/interface_oarchive.hpp" instantiation of "Archive &__ptr64 boost::archive::detail::interface_oarchive<Archive>::operator<<(T &__ptr64) [with Archive=boost::archive::text_oarchive, T=void *const __ptr64 ]" at line 77 of "v:\temp\boost_1_33_0\boost/serialization/nvp.hpp" instantiation of "void boost::serialization::nvp<T>::save(Archivex &__ptr64, const unsigned int ) const [with T=void *const __ptr64 , Archivex=boost::archive::text_oarchive]" at line 93 of "v:\temp\boost_1_33_0\boost/serialization/access.hpp" [ 58 instantiation contexts not shown ] instantiation of class "boost::archive::detail::export_generator<T, ASeq> [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" implicit definition of "const boost::archive::detail::export_generator<CModule::CInterface, boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>> boost::archive::detail::export_generator<T, ASeq>::instance [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "const void *__ptr64 boost::archive::detail::export_instance<T, ASeq>::not_abstract::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 210 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instance<T, ASeq>::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 219 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instantiate(T &__ptr64, ASeq &__ptr64) [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" v:\temp\boost_1_33_0\boost/archive/detail/oserializer.hpp(466): error: expression must be a pointer to a complete object type save(ar, * t, bpos_ptr); ^ detected during: instantiation of "void boost::archive::detail::save_pointer_type<Archive, TPtr>::invoke(Archive &__ptr64, const TPtr ) [with Archive=boost::archive::text_oarchive, TPtr=void *__ptr64]" at line 535 instantiation of "void boost::archive::save(Archive &__ptr64, const T &__ptr64) [with Archive=boost::archive::text_oarchive, T=void *__ptr64]" at line 78 of "v:\temp\boost_1_33_0\boost/archive/basic_text_oarchive.hpp" instantiation of "void boost::archive::basic_text_oarchive<Archive>::save_override(T &__ptr64, int) [with Archive=boost::archive::text_oarchive, T=void *const __ptr64 ]" at line 85 of "v:\temp\boost_1_33_0\boost/archive/detail/interface_oarchive.hpp" instantiation of "Archive &__ptr64 boost::archive::detail::interface_oarchive<Archive>::operator<<(T &__ptr64) [with Archive=boost::archive::text_oarchive, T=void *const __ptr64 ]" at line 77 of "v:\temp\boost_1_33_0\boost/serialization/nvp.hpp" instantiation of "void boost::serialization::nvp<T>::save(Archivex &__ptr64, const unsigned int ) const [with T=void *const __ptr64 , Archivex=boost::archive::text_oarchive]" at line 93 of "v:\temp\boost_1_33_0\boost/serialization/access.hpp" [ 58 instantiation contexts not shown ] instantiation of class "boost::archive::detail::export_generator<T, ASeq> [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" implicit definition of "const boost::archive::detail::export_generator<CModule::CInterface, boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>> boost::archive::detail::export_generator<T, ASeq>::instance [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "const void *__ptr64 boost::archive::detail::export_instance<T, ASeq>::not_abstract::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 210 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instance<T, ASeq>::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 219 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instantiate(T &__ptr64, ASeq &__ptr64) [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" v:\temp\boost_1_33_0\boost/serialization/access.hpp(109): error: expression must have class type t.serialize(ar, file_version); ^ detected during: instantiation of "void boost::serialization::access::serialize(Archive &__ptr64, T &__ptr64, const unsigned int ) [with Archive=boost::archive::text_iarchive, T=unsigned char]" at line 81 of "v:\temp\boost_1_33_0\boost/serialization/serialization.hpp" instantiation of "void boost::serialization::serialize(Archive &__ptr64, T &__ptr64, const unsigned int ) [with Archive=boost::archive::text_iarchive, T=unsigned char]" at line 140 of "v:\temp\boost_1_33_0\boost/serialization/serialization.hpp" instantiation of "void boost::serialization::serialize_adl(Archive &__ptr64, T &__ptr64, const unsigned int ) [with Archive=boost::archive::text_iarchive, T=unsigned char]" at line 318 of "v:\temp\boost_1_33_0\boost/archive/detail/iserializer.hpp" instantiation of "boost::archive::detail::pointer_iserializer<T, Archive>::pointer_iserializer() [with T=unsigned char, Archive=boost::archive::text_iarchive]" at line 201 of "v:\temp\boost_1_33_0\boost/archive/detail/iserializer.hpp" instantiation of class "boost::archive::detail::pointer_iserializer<T, Archive> [with T=unsigned char, Archive=boost::archive::text_iarchive]" at line 201 of "v:\temp\boost_1_33_0\boost/archive/detail/iserializer.hpp" [ 29 instantiation contexts not shown ] instantiation of class "boost::archive::detail::export_generator<T, ASeq> [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" implicit definition of "const boost::archive::detail::export_generator<CModule::CInterface, boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>> boost::archive::detail::export_generator<T, ASeq>::instance [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "const void *__ptr64 boost::archive::detail::export_instance<T, ASeq>::not_abstract::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 210 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instance<T, ASeq>::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 219 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instantiate(T &__ptr64, ASeq &__ptr64) [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" test1.cpp(99): error: the type in a const_cast must be a pointer, reference, or pointer to member to an object type ar >> const_cast<otext *> (_Desc) >> const_cast<ut4> (_pkgIndex) >> const_cast<ut4> (_clsIndex); ^ detected during: instantiation of "void CModule::CInterface::load(Archive &__ptr64, const unsigned int ) [with Archive=boost::archive::text_iarchive]" at line 101 of "v:\temp\boost_1_33_0\boost/serialization/access.hpp" instantiation of "void boost::serialization::access::member_load(Archive &__ptr64, T &__ptr64, const unsigned int ) [with Archive=boost::archive::text_iarchive, T=CModule::CInterface]" at line 54 of "v:\temp\boost_1_33_0\boost/serialization/split_member.hpp" instantiation of "void boost::serialization::detail::member_loader<Archive, T>::invoke(Archive &__ptr64, T &__ptr64, const unsigned int ) [with Archive=boost::archive::text_iarchive, T=CModule::CInterface]" at line 69 of "v:\temp\boost_1_33_0\boost/serialization/split_member.hpp" instantiation of "void boost::serialization::split_member(Archive &__ptr64, T &__ptr64, const unsigned int ) [with Archive=boost::archive::text_iarchive, T=CModule::CInterface]" at line 103 instantiation of "void CModule::CInterface::serialize(Archive &__ptr64, const unsigned int ) [with Archive=boost::archive::text_iarchive]" at line 109 of "v:\temp\boost_1_33_0\boost/serialization/access.hpp" [ 13 instantiation contexts not shown ] instantiation of class "boost::archive::detail::export_generator<T, ASeq> [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" implicit definition of "const boost::archive::detail::export_generator<CModule::CInterface, boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>> boost::archive::detail::export_generator<T, ASeq>::instance [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "const void *__ptr64 boost::archive::detail::export_instance<T, ASeq>::not_abstract::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 210 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instance<T, ASeq>::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 219 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instantiate(T &__ptr64, ASeq &__ptr64) [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" test1.cpp(99): error: the type in a const_cast must be a pointer, reference, or pointer to member to an object type ar >> const_cast<otext *> (_Desc) >> const_cast<ut4> (_pkgIndex) >> const_cast<ut4> (_clsIndex); ^ detected during: instantiation of "void CModule::CInterface::load(Archive &__ptr64, const unsigned int ) [with Archive=boost::archive::text_iarchive]" at line 101 of "v:\temp\boost_1_33_0\boost/serialization/access.hpp" instantiation of "void boost::serialization::access::member_load(Archive &__ptr64, T &__ptr64, const unsigned int ) [with Archive=boost::archive::text_iarchive, T=CModule::CInterface]" at line 54 of "v:\temp\boost_1_33_0\boost/serialization/split_member.hpp" instantiation of "void boost::serialization::detail::member_loader<Archive, T>::invoke(Archive &__ptr64, T &__ptr64, const unsigned int ) [with Archive=boost::archive::text_iarchive, T=CModule::CInterface]" at line 69 of "v:\temp\boost_1_33_0\boost/serialization/split_member.hpp" instantiation of "void boost::serialization::split_member(Archive &__ptr64, T &__ptr64, const unsigned int ) [with Archive=boost::archive::text_iarchive, T=CModule::CInterface]" at line 103 instantiation of "void CModule::CInterface::serialize(Archive &__ptr64, const unsigned int ) [with Archive=boost::archive::text_iarchive]" at line 109 of "v:\temp\boost_1_33_0\boost/serialization/access.hpp" [ 13 instantiation contexts not shown ] instantiation of class "boost::archive::detail::export_generator<T, ASeq> [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" implicit definition of "const boost::archive::detail::export_generator<CModule::CInterface, boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>> boost::archive::detail::export_generator<T, ASeq>::instance [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "const void *__ptr64 boost::archive::detail::export_instance<T, ASeq>::not_abstract::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 210 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instance<T, ASeq>::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 219 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instantiate(T &__ptr64, ASeq &__ptr64) [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" v:\temp\boost_1_33_0\boost/archive/detail/iserializer.hpp(472): error: expression must be a pointer to a complete object type const basic_pointer_iserializer * bpis_ptr = register_type(ar, *t); ^ detected during: instantiation of "void boost::archive::detail::load_pointer_type<Archive, Tptr>::invoke(Archive &__ptr64, Tptr &__ptr64) [with Archive=boost::archive::text_iarchive, Tptr=void *__ptr64]" at line 559 instantiation of "void boost::archive::load(Archive &__ptr64, T &__ptr64) [with Archive=boost::archive::text_iarchive, T=void *__ptr64]" at line 64 of "v:\temp\boost_1_33_0\boost/archive/basic_text_iarchive.hpp" instantiation of "void boost::archive::basic_text_iarchive<Archive>::load_override(T &__ptr64, int) [with Archive=boost::archive::text_iarchive, T=void *__ptr64]" at line 64 of "v:\temp\boost_1_33_0\boost/archive/text_iarchive.hpp" instantiation of "void boost::archive::text_iarchive_impl<Archive>::load_override(T &__ptr64, int) [with Archive=boost::archive::text_iarchive, T=void *__ptr64]" at line 84 of "v:\temp\boost_1_33_0\boost/archive/detail/interface_iarchive.hpp" instantiation of "Archive &__ptr64 boost::archive::detail::interface_iarchive<Archive>::operator>>(T &__ptr64) [with Archive=boost::archive::text_iarchive, T=void *__ptr64]" at line 85 of "v:\temp\boost_1_33_0\boost/serialization/nvp.hpp" [ 65 instantiation contexts not shown ] instantiation of class "boost::archive::detail::export_generator<T, ASeq> [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" implicit definition of "const boost::archive::detail::export_generator<CModule::CInterface, boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>> boost::archive::detail::export_generator<T, ASeq>::instance [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "const void *__ptr64 boost::archive::detail::export_instance<T, ASeq>::not_abstract::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 210 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instance<T, ASeq>::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 219 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instantiate(T &__ptr64, ASeq &__ptr64) [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" v:\temp\boost_1_33_0\boost/archive/detail/iserializer.hpp(480): error: expression must be a pointer to a complete object type t = pointer_tweak(newbpis_ptr->get_eti(), t, *t); ^ detected during: instantiation of "void boost::archive::detail::load_pointer_type<Archive, Tptr>::invoke(Archive &__ptr64, Tptr &__ptr64) [with Archive=boost::archive::text_iarchive, Tptr=void *__ptr64]" at line 559 instantiation of "void boost::archive::load(Archive &__ptr64, T &__ptr64) [with Archive=boost::archive::text_iarchive, T=void *__ptr64]" at line 64 of "v:\temp\boost_1_33_0\boost/archive/basic_text_iarchive.hpp" instantiation of "void boost::archive::basic_text_iarchive<Archive>::load_override(T &__ptr64, int) [with Archive=boost::archive::text_iarchive, T=void *__ptr64]" at line 64 of "v:\temp\boost_1_33_0\boost/archive/text_iarchive.hpp" instantiation of "void boost::archive::text_iarchive_impl<Archive>::load_override(T &__ptr64, int) [with Archive=boost::archive::text_iarchive, T=void *__ptr64]" at line 84 of "v:\temp\boost_1_33_0\boost/archive/detail/interface_iarchive.hpp" instantiation of "Archive &__ptr64 boost::archive::detail::interface_iarchive<Archive>::operator>>(T &__ptr64) [with Archive=boost::archive::text_iarchive, T=void *__ptr64]" at line 85 of "v:\temp\boost_1_33_0\boost/serialization/nvp.hpp" [ 65 instantiation contexts not shown ] instantiation of class "boost::archive::detail::export_generator<T, ASeq> [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" implicit definition of "const boost::archive::detail::export_generator<CModule::CInterface, boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>> boost::archive::detail::export_generator<T, ASeq>::instance [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "const void *__ptr64 boost::archive::detail::export_instance<T, ASeq>::not_abstract::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 210 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instance<T, ASeq>::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 219 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instantiate(T &__ptr64, ASeq &__ptr64) [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" v:\temp\boost_1_33_0\boost/serialization/access.hpp(116): error #373: "Object::~Object(unsigned int)" is inaccessible delete const_cast<T *>(t); ^ detected during: instantiation of "void boost::serialization::access::destroy(const T *__ptr64) [with T=Object]" at line 105 of "v:\temp\boost_1_33_0\boost/archive/detail/iserializer.hpp" instantiation of "void boost::archive::detail::iserializer<Archive, T>::destroy(void *__ptr64) const [with Archive=boost::archive::text_iarchive, T=Object]" at line 113 of "v:\temp\boost_1_33_0\boost/archive/detail/iserializer.hpp" instantiation of "boost::archive::detail::iserializer<Archive, T>::iserializer() [with Archive=boost::archive::text_iarchive, T=Object]" at line 144 of "v:\temp\boost_1_33_0\boost/archive/detail/iserializer.hpp" instantiation of "boost::archive::detail::iserializer<Archive, T> &__ptr64 boost::archive::detail::iserializer<Archive, T>::instantiate() [with Archive=boost::archive::text_iarchive, T=Object]" at line 362 of "v:\temp\boost_1_33_0\boost/archive/detail/iserializer.hpp" instantiation of "void boost::archive::detail::load_non_pointer_type<Archive, T>::load_standard::invoke(Archive &__ptr64, T &__ptr64) [with Archive=boost::archive::text_iarchive, T=Object]" at line 412 of "v:\temp\boost_1_33_0\boost/archive/detail/iserializer.hpp" [ 38 instantiation contexts not shown ] instantiation of class "boost::archive::detail::export_generator<T, ASeq> [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" implicit definition of "const boost::archive::detail::export_generator<CModule::CInterface, boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>> boost::archive::detail::export_generator<T, ASeq>::instance [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "const void *__ptr64 boost::archive::detail::export_instance<T, ASeq>::not_abstract::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 210 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instance<T, ASeq>::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 219 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instantiate(T &__ptr64, ASeq &__ptr64) [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" v:\temp\boost_1_33_0\boost/serialization/access.hpp(123): error #373: "CModule::CInterface::CInterface()" is inaccessible ::new(t)T; ^ detected during: instantiation of "void boost::serialization::access::construct(Archive &__ptr64, T *__ptr64) [with Archive=boost::archive::text_iarchive, T=CModule::CInterface]" at line 105 of "v:\temp\boost_1_33_0\boost/serialization/serialization.hpp" instantiation of "void boost::serialization::load_construct_data(Archive &__ptr64, T *__ptr64, const unsigned int ) [with Archive=boost::archive::text_iarchive, T=CModule::CInterface]" at line 170 of "v:\temp\boost_1_33_0\boost/serialization/serialization.hpp" instantiation of "void boost::serialization::load_construct_data_adl(Archive &__ptr64, T *__ptr64, const unsigned int ) [with Archive=boost::archive::text_iarchive, T=CModule::CInterface]" at line 307 of "v:\temp\boost_1_33_0\boost/archive/detail/iserializer.hpp" instantiation of "void boost::archive::detail::pointer_iserializer<T, Archive>::load_object_ptr(boost::archive::detail::basic_iarchive &__ptr64, void *__ptr64 &__ptr64, const unsigned int ) const [with T=CModule::CInterface, Archive=boost::archive::text_iarchive]" at line 329 of "v:\temp\boost_1_33_0\boost/archive/detail/iserializer.hpp" instantiation of "boost::archive::detail::pointer_iserializer<T, Archive>::pointer_iserializer() [with T=CModule::CInterface, Archive=boost::archive::text_iarchive]" at line 201 of "v:\temp\boost_1_33_0\boost/archive/detail/iserializer.hpp" [ 9 instantiation contexts not shown ] instantiation of class "boost::archive::detail::export_generator<T, ASeq> [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" implicit definition of "const boost::archive::detail::export_generator<CModule::CInterface, boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>> boost::archive::detail::export_generator<T, ASeq>::instance [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 178 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "const void *__ptr64 boost::archive::detail::export_instance<T, ASeq>::not_abstract::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 210 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instance<T, ASeq>::invoke() [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]" at line 219 of "v:\temp\boost_1_33_0\boost/serialization/export.hpp" instantiation of "std::pair<const void *__ptr64, const void *__ptr64> boost::archive::detail::export_instantiate(T &__ptr64, ASeq &__ptr64) [with T=CModule::CInterface, ASeq=boost::mpl::list2<boost::archive::text_oarchive, boost::archive::text_iarchive>]"

2 4

boost 1.33.1 + icu - does not working with simple char's
by Alex Ott 21 Feb '06

21 Feb '06

Hi all I found one strange thing - when i compile boost::regex with unicode support (via icu), my code, that use char's stop linking with following messages: /opt/skvt2-devel/include/boost/regex/v4/basic_regex.hpp:254: undefined reference to `boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::do_assign(char const*, char const*, unsigned int)' Configuration.o: In function `perl_matcher': /opt/skvt2-devel/include/boost/regex/v4/perl_matcher_common.hpp:44: undefined reference to `boost::re_detail::perl_matcher<__gnu_cxx::__normal_iterator<char const*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<boost::sub_match<__gnu_cxx::__normal_iterator<char const*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::construct_init(boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > > const&, boost::regex_constants::_match_flags)' GroupInfo.o: In function `basic_regex': /opt/skvt2-devel/include/boost/regex/v4/basic_regex.hpp:254: undefined reference to `boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::do_assign(char const*, char const*, unsigned int)' LManager.o: In function `basic_regex': /opt/skvt2-devel/include/boost/regex/v4/basic_regex.hpp:254: undefined reference to `boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::do_assign(char const*, char const*, unsigned int)' LManager.o: In function `assign': /opt/skvt2-devel/include/boost/regex/v4/basic_regex.hpp:254: undefined reference to `boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::do_assign(char const*, char const*, unsigned int)' I want to use both unicode regexp's and usual regexp's. how i can fix this? > gcc -v Using built-in specs. Target: i586-suse-linux Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib --enable-languages=c,c++,objc,f95,java,ada --disable-checking --with-gxx-include-dir=/usr/include/c++/4.0.2 --enable-java-awt=gtk --disable-libjava-multilib --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit --without-system-libunwind --host=i586-suse-linux Thread model: posix gcc version 4.0.2 20050901 (prerelease) (SUSE Linux) -- With best wishes, Alex Ott Jet Infosystems, Head of software development group, MBA +7 (095) 411 76 01 http://www.jetsoft.ru/

2 1

CVS import guidance
by Rush Manbert 20 Feb '06

20 Feb '06

Hi all, I am setting up a local CVS archive and I found that when I imported the boost 1.33.1 distribution there are some files that get ignored by CVS. Eventually I figured out that the missing files are described by the path expression "libs/python/pyste/tests/*.cpp" relative to the top level directory. From that I found the .cvsignore in the same directory that specifies *.cpp as an ignore pattern. There are more .cvsignore files in the distribution tree, but this is the only one that filters out files for an import. Does anyone have any guidance as to how CVS imports of Boost source code distributions should be done? Should I delete all of the .cvsignore files in the distribution before importing? Should I replace them with an empty version of the file? Should I do something else? A related question for developers. Should the .cvsignore files be removed from the distribution tree before it is released to the public? Thanks, Rush

1 1

Quick newbie question
by Jason A. Myers 20 Feb '06

20 Feb '06

Hello all, I'm just getting started with the boost graph library (and templates) and there are a few details that I can't figure out. -For the life of me I can't find a definition or a typedef for the UniformCostVisitor declared in dijkstra_shortest_paths_.hpp. I've grep'd all the boost header files and looked in the docs, to no avail. -I am writing my own algorithm o use with BFS to find a vertex weighted MST and some other goodies, so i want to implement something very similar to the implementation of dijkstra's. Is it neccessary to define the "VisitorConcept" struct, or do you only need to do this when you (as in me) are going to invoke some concept checking? I think that's it for now...Thanks in advance! Cheers, Jason

1 0