- Boost-users - lists.boost.org

Re: [Boost-users] [SmartPtr] Memory Leak Perhaps
by Benjamin Sobotta 20 Sep '10

20 Sep '10

On Monday 20 September 2010 02:44:12 pm you wrote: > Dear Benjamin, > > > shared_ptr to this are dangerous. As soon as you do that > > twice you already have a problem. > > Oh, that's interesting. Could you please explain why? Well because you can only erase 'this' once. When you have two _independent_ smart pointers, both will attempt to delete the object they're pointing to. > > > If you want to create shared_ptrs to this, use > > shared_from_this. > > > > http://www.boost.org/doc/libs/1_44_0/libs/smart_ptr/enable_shared_from_th > >is.html > > Thank you for the reference. At the very bottom of the documentation, I see > "There must exist at least one shared_ptr instance p that owns t" (in the > requirements of template<class T> shared_ptr<T const> > enable_shared_from_this<T>::shared_from_this() const). So, does the > following code not meet this requirement? > > class Y: public T, public boost::enable_shared_from_this<Y> > { > public: > > boost::shared_ptr<Y> f() const > { > return shared_from_this(); > } > }; > > const T* tp = new Y;//where Y also derives from T > boost::shared_ptr<T> q = tp->f(); Yes, as far as I know this won't work. But why would you want that? boost::shared_ptr<T> q = boost::make_shared<Y>(); is the safe way to do it. No explicit 'new', no explicit 'delete', no problems. Call your insert_me_into routine through the shared_ptr. Then, inside insert_me_into, after you're done with your computations, use shared_from_this to get a shared_ptr to stick into the container. > TIA, > --Hossein HTH, Benjamin

1 0

[SmartPtr] Memory Leak Perhaps
by Hossein Haeri 20 Sep '10

20 Sep '10

Dear all, (Sorry for cross-posting.) I have a container which stores boost::shared_ptr's. The container has a strange behaviour upon insertion of a SPECIFIC pointer into it. The insertion itself happens with no problem and I can successfully do all my desired operations. Yet, I receive the following strange Win32 exceptions when I'm done and my program is ending (i.e., after the last instruction in my main function): 1) When I run the program from the CodeBlocks IDE (GCC 4.5.1, MinGW, WinXP-SP3), a message box from the JIT debugger pops up which says: "An unhandled Win32 exception occurred in ... [29436]". 2) When I run the same program from MSCV2008, an MSVC++ Debug Library message box pops up which says: "Program ... File f:\dd\... Line 52 Exception _BLOCK_TYPE_IS_VALID(pHead->nBlockUse)...". I call the above error messages strange because of the observations below: 1) The error reported by MSVC2008 refers to a file on my drive F: whereas, basically, I don't have such a drive on my system! 2) The CodeBlocks debugger (a GUI wrapped around GDB) runs the program with no problems over the debug sessions. Despite that, there are several "Program received signal SIGTRAP, Trace/breakpoint trap." messages in the GDB debug log. Unfortunately, I don't know how to locate the place where these are related to. 3) MSVC2008 has the same behaviour over the debug session. The output of debug session ends with "The program '[29312] EE1Debugger.exe: Native' has exited with code 3 (0x3)." (Please find a copy of the debug log at the P.S. if you're interested.) My first guess was a memory leak but I didn't spot anything which smells like that over numerous debug sessions. I'm generally dubious about that because I'm using shared_ptr's. Shallow copy can't be the problem either again 'cause I only insert shared_ptr's (from just-allocated dynamic memory) into my container. On the other hand, the problem only occurs upon insertion of a SPECIFIC entry into my container. Strangely enough, if I delete that specific entry manually before the end of my program, everything goes fine! I even checked the count of that specific shared_ptr and it was 1, i.e., I'm not deleting anybody else's memory. I am really confused and left with no clue... Any suggestions? P.S. 'EE1Debugger.exe': Loaded 'D:\...\EE1Debugger.exe', Symbols loaded. 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\ntdll.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\kernel32.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\WinSxS\x86_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.21022.8_x-ww_597c3456\msvcr90d.dll', Symbols loaded. 'EE1Debugger.exe': Loaded 'C:\WINDOWS\WinSxS\x86_Microsoft.VC90.DebugCRT_1fc8b3b9a1e18e3b_9.0.21022.8_x-ww_597c3456\msvcp90d.dll', Symbols loaded. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f550.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. First-chance exception at 0x7c812afb in EE1Debugger.exe: Microsoft C++ exception: std::runtime_error at memory location 0x0012f5a8.. 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\user32.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\gdi32.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\imm32.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\advapi32.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\rpcrt4.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\secur32.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\lpk.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\usp10.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\msvcrt.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\GDX32.dll', Binary was not built with debug information. 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\acaptuser32.dll', Binary was not built with debug information. 'EE1Debugger.exe': Unloaded 'C:\WINDOWS\system32\acaptuser32.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\uxtheme.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\MSCTF.dll' 'EE1Debugger.exe': Loaded 'C:\Program Files\Trusteer\Rapport\bin\rooksbas.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\version.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\shlwapi.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\psapi.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\shell32.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\ole32.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.5512_x-ww_35d4ce83\comctl32.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\comctl32.dll' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\MSCTFIME.IME' 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\PickWord.dll', Binary was not built with debug information. 'EE1Debugger.exe': Loaded 'C:\Program Files\Dell\QuickSet\dadkeyb.dll', Binary was not built with debug information. 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\hccutils.dll', Binary was not built with debug information. 'EE1Debugger.exe': Loaded 'C:\WINDOWS\system32\oleaut32.dll' The program '[29312] EE1Debugger.exe: Native' has exited with code 3 (0x3).

4 5

boost serialisation 1.44 /linux /gcc 4.2.1 compilation problems
by avibahra 20 Sep '10

20 Sep '10

Having problems with boost 1.44 and serialisation on Linux, gcc 4.2.1 I am migrating from boost 1.43 to boost 1.44 and get compiler errors of the form: In file included from ACore/src/TimeSeries.hpp:13, from ACore/test/TestTimeSeries.cpp:16: /var/tmp/ma0/boost/boost_1_44_0/boost/date_time/posix_time/time_serialize.hpp: In function ‘void boost::serialization::save(Archive&, const boost::posix_time::time_duration&, unsigned int)’: /var/tmp/ma0/boost/boost_1_44_0/boost/date_time/posix_time/time_serialize.hpp:42: error: there are no arguments to ‘make_nvp’ that depend on a template parameter, so a declaration of ‘make_nvp’ must be available This is surprising as boost 1.44 release notes makes no mention of any changes to boost serialisation ? Can anyone help ? Best regards, Ta, Avi

2 1

Re: [Boost-users] boost::bond and assignment
by przemyslaw.sliwa＠uk.bnpparibas.com 20 Sep '10

20 Sep '10

Thank, This is true if you have a boost::shared_ptr<int> but in my case I have a class not an int and I want to assign a value of one of its members called mem, for(vector<clss>::iterator pos=tmp.begin(); pos!=tmp.end(); ++tmp) { clss& item = (*pos); item.mem = 1.0; } how this can be translated into the boost lambda or bind? Cheers ___________________________________________________________ This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is prohibited. Please refer to http://www.bnpparibas.co.uk/en/information/legal_information.asp?Code=ECAS-… for additional disclosures.

2 1

overload resolution with boost::function
by Jens Auer 20 Sep '10

20 Sep '10

Hi, I am trying to use objects of boost::function as parameters to overloaded function. However, the compiler fails to automatically resolve the function type when I use a function pointer: #include <boost/function.hpp> void f(int); void accept( boost::function< void () > g); void accept( boost::function< void (int) > g); int main(int argc, char* argv[]) { accept(f); return 0; } boost_function.cpp: In function ┬╗int main(int, char**)┬½: boost_function.cpp:11: Fehler: Aufruf des ├╝berladenen ┬╗accept(void (&)(int))┬½ ist nicht eindeutig boost_function.cpp:6: Anmerkung: Kandidaten sind: void accept(boost::function<vo id()>) boost_function.cpp:7: Anmerkung: void accept(boost::function<vo id(int)>) Sorry for the german error messages, the compiler complains about ambigous functions and shows two candidates. Is there any way to have the accept function call resolved automatically without creating explicit boost::function object?

2 2

[Concept] boost::FloatingPoint<T>
by Ruediger Berlich 20 Sep '10

20 Sep '10

Hi there, I'd like to make sure that some of my classes are only used with particular value types. This is easy enough to implement for integers, using BOOST_CONCEPT_ASSERT((boost::Integer<T>)) . However, there is no boost::FloatingPoint<T>, which is a bit odd. The following, easy code seems to do what I want, but reqires inclusion of boost/concept/detail/concept_def.hpp /*****************************************************************/ namespace boost { BOOST_concept(FloatingPoint, (T)) { BOOST_CONCEPT_USAGE(FloatingPoint) { x.error_type_must_be_a_floating_point_type(); } private: T x; }; template <> struct FloatingPoint<long double> {}; template <> struct FloatingPoint<double> {}; template <> struct FloatingPoint<float> {}; } /*****************************************************************/ >From what I understand, this means that I am relying on implementation details with the above code. Is there any way to do the above in a portable way ? Thanks and Best Regards, Ruediger P.S.: If the above seems acceptable, please feel free to include it in Boost.Concept.

2 2

Any "2D" iterator?
by lfrfly＠icqmail.com 20 Sep '10

20 Sep '10

I have on several occasions encountered situations in which it would be advantageous to view a container of containers as a flat sequence. It seems like there ought to be a natural way to do this using an iterator class. For instance, if you have vector<list<T>> v, you ought to be able to design an iterator which begins at v.begin()->begin() and runs until v.end(), over every element of every list. Does such a thing exist in Boost, or is it planned in the near future?

6 5

Re: [Boost-users] Serialization of functors and MPL use
by Anonymous user 20 Sep '10

20 Sep '10

Hello, Thanks for the quick response ! It is a good solution, but hhat I try to do is the following: template<class Object,class Type> struct my_class { �boost::function<Type ()> *m_f; template<typename Functor> my_class(Object &obj,Functor &f,Type & newValue) { �m_f= boost::bind(f,&obj); } �... �void serialize(Archive &ar, const unsigned int version) { ��ar & m_f; //does not compile �} �}; Instantiation:� �MyObject myObject("old value");� my_class�<�MyObject,std::string>�m(myObject,&MyObject::setName,e,"new value");� Thus the idea is to avoid changing the design (no inheritance to create functor) and just use boost::function to create dynamically functors. My problem is to rebuild dynamically the boost::function in the serialization step. I really needs to avoid using inheritance on my classes just to creates functors, thus I really need to keep the current design�and just build dynamically functors through boost::bind. One possible idea was to register a pair of types -> object which contains the function and the functor. Example: template<class Object,class Type> struct my_class { typedef boost::mpl::pair<Object,Type> key; typedef boost::function<Type ()> value; typedef�boost::mpl::map< key,value > > Functions; template<typename Functor> my_class(Object &obj,Functor &f,Type & newValue) { �m_f= boost::bind(f,&obj); typedef�boost::mpl::insert<�Functions,Functor > > t; } ... template <class Archive> void serialize( Archive & ar, constunsignedint version ) { ��typedef boost::mpl::at<key>()::type t; ��ar & t; //not possible -> does not instantiate the real functor address ! } }; The problem is the above solution is that we don't store the functor address but only it's signature. If you have an idea to make this example working or another idea to store functors which have been created dynamicaly, don't hesitate. � Thanks again for your help ! Regards. > ----- Original message ----- > From: "Robert Ramey‎" <ramey(a)rrsd.com> > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] Serialization of functors and MPL use > Date: Sun, 19 Sep 2010 11:06:43 -0800 > > >Anonymous user wrote: > > Hello, > > > > Thanks for the response. > > > > Actually, I need to create dynamically functosr, because I call a lot > > of different methods coming from several classes. I don't want to > > implement the operator () inside each object used, because it is not > > appropriate in my code (too much classes). > > > > Can you please , give me an example of registration of functors ? > > I could if I had nothing else to do right now. I've got on my list to > make a "case study" in the documentation on how to do this. But > for now I'll just give a short explanation off the top of my head. > > A functor is just a structure. You can serialize just as you can > any other structure. > > The problem is that you want serialize a data variable which > refers to any one of a number of differently defined structures. > This is a specific instance of something that we want to do > in C++ all the time. The most common way of doing this > is to use a pointer to a virtual base class. e.g. > > struct functor_interface { > virtual int /* or other return type */ operator()(int /* other other > return types */ x, ...); > // virtual makes it polymorphic > // operator() ... makes a functor > }; > > So now we can define any number of functors which use the same interface: > > struct f1 : public functor_interface { > virtual int operator()(int x){ > ... whatever > template<class Archive> > void serialize(Archive &ar, const unsigned int version){ > //.. this functor has no parameters so nothing to do. > // .. serialization still needs this defined though > } > }; > > struct f2 : public functor_interface { > int m_a; // member variable which the functor uses at runtime > virtual int operator()(int x){ > ... whatever - something different than f1 > void serialize(Archive &ar, const unsigned int version){ > ar & m_a; > } > }; > > ... as many as you want. > > Register all the functors > BOOST_EXPORT_CLASS(f1) > ... > > The above makes the functors exportable - that is associates > the functor f1 with the external string name "f1". > > Now you can use a variable > > struct my_class { > functor_interface *m_f; > ... > void serialize(Archive &ar, const unsigned int version){ > ar & m_f; > } > }; > > Which uses the m_f variable as a "variable function". You > call it with > m_f->operator(112) > or maybe with something slicker like > (*m_f)(112) // or something similar > > Now you're done - just serialize m_class like anyother. > when you de-serialize it, it has the same state it did before > (whatever that was). > > Home this is helpful. > > Robert Ramey > > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users > -------------------------------------------------------------- Ovi Mail: Making email access easy http://mail.ovi.com

2 1

Re: [Boost-users] Serialization of functors and MPL use
by Anonymous user 19 Sep '10

19 Sep '10

Hello, Thanks for the response. Actually, I need to create dynamically functosr, because I call a lot of different methods coming from several classes.�I don't want to implement the operator () inside each object used, because it is not appropriate in my code (too much classes).� Can you please , give me an example of registration of functors ? Thanks in advance. Regards. > ----- Original message ----- > From: "OvermindDL1‎" <overminddl1(a)gmail.com> > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] Serialization of functors and MPL use > Date: Fri, 17 Sep 2010 00:22:11 -0600 > > >On Thu, Sep 16, 2010 at 2:43 PM, Anonymous user <nokiac5eel(a)ovi.com> wrote: > > Hello everybody, > > > > > > > > I'm currently trying to serialize functors. > > > > Apparently, it is not possible to serialize boost::function objects, > > > > is it possible to find a way to serialize pointer to function ? (in order to > > make working the example below*) > > > > If it is definitively not possible, is there a way to 'register' a relation > > betwwen objects and functor ? (using MPL library). > > > > The idea is to rebuild the boost function according to the 'Object and > > 'Type' class of the template'. > > > > > > > > Example: > > > > > > > > mpl::pair<Object,Function> container; > > > > serialize() > > > > { > > > > boost::function<Type ()> m_getter=mpl::at< container,Object>; > > > > } > > > > > > > > > > > > *Here is the problem that� I'm trying to resolve: > > > > > > > > MyObject myObject("before"); > > > > > > > > SetCommand<std::string,MyObject> > > SetCommand(myObject,&MyObject::setName,&MyObject::getName,"after"); > > > > > > > > SetCommand.do(); � // call functor 'MyObject::setName("after")' > > > > SetCommand.undo(); // call functor 'MyObject::setName("before")' > > > > > > > > > > > > template<typename Type,typename Object> > > > > class SetCommand : public Command > > > > { > > > > > > > > > > > > � public: > > > > > > > > � � � � template <typename Setter, typename Getter> > > > > � � � � SetCommand(Object& o, const Setter& setter, const Getter& getter, > > const Type& value) : > > > > � � � � � � Command(), > > > > � � � � � � m_getter(boost::bind(getter, &o)), > > > > � � m_setter(boost::bind(setter, &o, _1)), > > > > � � � � � � initialValue(m_getter()), > > > > � � � � � � finalValue(value) > > > > � � � � { > > > > � � � � } > > > > > > > > virtual void undo() > > > > � � � � { > > > > � � � � � � m_setter(initialValue) ; > > > > � � � � } > > > > > > > > � � � � virtual void do() > > > > � � � � { > > > > � � � � � � m_setter(finalValue) ; > > > > � � � � } > > > > > > > > �� private: > > > > > > > > friend class boost::serialization::access; > > > > > > > > SetCommand(){} > > > > > > > > template <class Archive> > > > > void serialize( Archive & ar, const unsigned int version ) > > > > { > > > > > > > > � ar & m_getter; ERROR -> does not compile !!! > > > > � ar & m_setter; ERROR -> does not compile !!! > > > > > > > > � ar & initialValue; > > > > � ar & finalValue; > > > > } > > > > > > > > boost::function<Type ()> m_getter ; > > > > � � � � boost::function<void (Type)> m_setter ; > > > > > > > > � � � � Type initialValue ; > > > > � � � � Type finalValue ; > > > > }; > > > > > > > > Thanks in advance. > > You need to somehow register the function in there, if you know what a > limited set of types it might be, an integer that can rebuild it would > work, but the most common way is to just make a base class with an > operator() and have a (shared) pointer to that be your 'function', > then base classes (that can be properly serialized) to act as the > functions. Not pretty, not the easiest, but it works well and is > expandable. > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users > -------------------------------------------------------------- Ovi Mail: Making email access easy http://mail.ovi.com

2 1

Re: [Boost-users] Serialization of functors and MPL
by Anonymous user 19 Sep '10

19 Sep '10

Hello, Thanks for the response. Actually, I need to create dynamically functor, because I call a lot of different methods coming from several classes. see below: MyObject myObject("before"); SetCommand<std::string,MyObject> cmd(myObject,&MyObject::setName,&MyObject::getName,"after"); Thus, I'm wondering if it is not possible to use the MPL library to register the link between a class and it functor. Example: template<class Object,class Type> class SetCommand { typedef mpl::pair<MyObject,Function>::type �container; template<class Functor> SetCommand() { typedef mpl::insert<container,mpl::pair<Object,Functor>::type myType; } }; serialize() { boost::function<Type ()> getter=mpl::at< container,MyObject>::type; } MyObject myObject("before"); SetCommand<std::string,MyObject> cmd(myObject,&MyObject::setName,&MyObject::getName,"after"); The mechanism should be like the registration of serializable class with boost. The problem here is the registration of the functor, we don't register the address of the functor, but only its type(function signature). Thus it is difficult to allocate this functor ! If someone can give me a solution to this problem, it would be great :) Remark: I don't want to implement the operator () inside each object used, because it is not appropriate in my code (too much classes).� Thanks in advance. Regards. > ----- Original message ----- > From: "Robert Ramey‎" <ramey(a)rrsd.com> > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] Serialization of functors and MPL > Date: Thu, 16 Sep 2010 14:20:06 -0800 > > >Anonymous user wrote: > > Hello everybody, > > > > I'm currently trying to serialize functors. > ... > > Thanks in advance. > > > Without going through your specific situation, I can say that this is an > easy problem. > Here are a couple of ways to do it. > > a) use boost::variant > > Make your functors: f, g, h > make a variant boost::variant<f, g, h> v; > > v = f or g or h ... > > #include boost/serialization/variant.hpp > serialize v > > b) make your functors f, g, h all derived from a base class - functors > make the base class polymorphic by making at least one member virtual > EXPORT f, g, and h > > functor *fx; > fx = &f, or &g, or &h > > serialize fx > > c) There might be a way to do it with boost::any also. > > Robert Ramey > > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users > -------------------------------------------------------------- Ovi Mail: Making email access easy http://mail.ovi.com

1 0