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

Use of a member pointer to a member function in for_each - is it possible?
by Vesselin Kostadinov 27 May '04

27 May '04

Hi, I am struggling to find the proper combination of ataptors/binders to use a member pointer to a member function in a for_each. Is this possible at all? Any help is appreciated. Here is the code: #include <iostream> #include <algorithm> #include <vector> #include <boost/bind.hpp> #include <boost/ref.hpp> using namespace std; class foo { private: int value; void default_proc(int& x) { cout << "default_proc. Value = " << value << ", Param = " << x << "\n";} void init1_proc(int& x) { cout << "init1_proc. Value = " << value << ", Param = " << x << "\n";} public: void (foo::*func_ptr)(int& x); //yes, I need the reference here foo(int init) : value(init), func_ptr(init == 1 ? &foo::init1_proc : &foo::default_proc) {} }; int main() { vector<foo> foos; foos.push_back(foo(0)); foos.push_back(foo(1)); foos.push_back(foo(2)); int param = 3; //i need this functionality: //prints "default_proc. Value = 0, Param = 3": (foos[0].*foos[0].func_ptr)(param); //prints "init1_proc. Value = 1, Param = 3": (foos[1].*foos[1].func_ptr)(param); //prints "default_proc. Value = 2, Param = 3": (foos[2].*foos[2].func_ptr)(param); //using the right combination of for_each, bind, ref, mem_fn, etc: // std::for_each(foos.begin(), foos.end(), // boost::bind(???????), // _1, boost::ref(param)); } The compiler is Borland C++ 5.6.4 for Win32. Thanks in advance

2 1

Re: [Boost-users] boost::thread, boost::bind, and member functions
by Mike Feldmeier 26 May '04

26 May '04

GAH! No change. My %LIB% is now C:\STLport-4.6.2\lib;C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\Lib\ My %INCLUDE% is now C:\STLport-4.6.2\stlport;C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\include\ My rebuilds have been starting with copying dlls and libs to /Boost, so I blew away the bin directory and the target /Boost directory and watched it rebuild each. I checked a few of the other boost dlls as well, they basically have the same dependencies. >From: GoochRules! <goochrules(a)hotmail.com> >Reply-To: boost-users(a)lists.boost.org >To: boost-users(a)lists.boost.org >Subject: Re: [Boost-users] boost::thread, boost::bind, and member functions >Date: Tue, 25 May 2004 20:10:26 -0600 > >>Sure enough, running depends on the boost dll shows MSVCP71D.DLL, >>MSVCR71D.DLL and KERNEL32.DLL, but no STLPORT! > >To me it looks like your STLport include/lib directories come after the >Platform SDK/VS.Net2003 directories, which means STLport is not being used >at all, hence it is not listed in the dependencies. > >Try: >set INCLUDE=$STLport_include_path;%INCLUDE% >set LIB=$STLport_lib_path;%LIB% > >--mpeltzer > > >_______________________________________________ >Boost-users mailing list >Boost-users(a)lists.boost.org >http://lists.boost.org/mailman/listinfo.cgi/boost-users _________________________________________________________________ Stop worrying about overloading your inbox - get MSN Hotmail Extra Storage! http://join.msn.click-url.com/go/onm00200362ave/direct/01/

1 0

Re: [Boost-users] boost::thread, boost::bind, and member functions
by Mike Feldmeier 26 May '04

26 May '04

>From: GoochRules! <goochrules(a)hotmail.com> >Reply-To: boost-users(a)lists.boost.org >To: boost-users(a)lists.boost.org >Subject: Re: [Boost-users] boost::thread, boost::bind, and member functions >Date: Tue, 25 May 2004 12:37:24 -0600 > >>Unfortunately, this whole roadtrip started with the need for STL >>collections to cross DLL boundaries, which is why I am using STLPort. The >>STL that comes with VC++ 7.1 doesn't (with the exception of string and >>vector). When I built boost, I built it with the vc7.1-stlport toolset, >>and I have the stlport library directory in my "additional library path". >>Along this line, I wonder if I need to be doing something special with the >>STLPort DLL? > >One thing to check, if you have the Platform SDK installed, you should have >a 'depends.exe' application... this shows you the dll an exe or dll depends >upon, and even which functions of those dlls are used. Make sure stlport >is one of 'em. If it isn't, make sure that your additional directories >(include and library) are **before** the VS and PSDK directories. Note >that boost will still depend upon msvcpt71.dll and msvcr71.dll (when >compiled with VS.Net2003, but it will use the stlport dll for stl objects. > Sure enough, running depends on the boost dll shows MSVCP71D.DLL, MSVCR71D.DLL and KERNEL32.DLL, but no STLPORT! I built boost with: set STLPORT_PATH=C:\ (STLPort is in C:\STLport-4.6.2) bjam "-sTOOLS=vc7.1-stlport" "-sBUILD=debug release" install Is this not correct? I don't get any errors indicating that it can't find STLPort. Thanks, Mike _________________________________________________________________ Learn to simplify your finances and your life in Streamline Your Life from MSN Money. http://special.msn.com/money/0405streamline.armx

2 1

RE: [Boost-users] boost::thread, boost::bind, and member functions
by Mike Feldmeier 25 May '04

25 May '04

>From: "Ben Hutchings" <ben.hutchings(a)businesswebsoftware.com> >Reply-To: boost-users(a)lists.boost.org >To: <boost-users(a)lists.boost.org> >Subject: RE: [Boost-users] boost::thread, boost::bind, and member functions >Date: Tue, 25 May 2004 17:32:10 +0100 > >Mike Feldmeier <pooky_bunny(a)hotmail.com> wrote: >[ Ben Hutchings wrote:] > > > Mike Feldmeier <pooky_bunny(a)hotmail.com> wrote: ><snip> > > > > This consistently produces the linking error: > > > > > > > > converter.obj : error LNK2019: unresolved external symbol > > > > "__declspec(dllimport) public: __thiscall boost::thread::thread( > > > > class boost::function0<void,class > > > > _STL::allocator<class boost::function_base> > const &)" > > > > (__imp_??0thread@boost@@QAE@ABV?$function0@XV?$allocator@Vfunction > > > > _base@boost@@@_STL@@@1@@Z) referenced in function "public: void > > > > __thiscall mytest::test::converter::run(void)" > > > > (?run@converter@test@mytest@@QAEXXZ) > > > > > >I think you aren't linking with the thread library. ><snip> > > I'm using Visual C++ 7.1, but using straight C++, no .NET. I've > > defined the addtional library path (C:\boost\lib) and tried linking > > (in the additional dependencies) with > > boost_thread-vc71-mt-gdp-1_31.lib, boost_thread-vc71-mt-gdp.lib, > > boost_thread-vc71-mt-p-1_31.lib, and boost_thread-vc71-mt-p.lib (one > > at a time, of course), but I get the same error message with all of > > them. ><snip> > >I've worked it out now. In your main program you are using STLport - >notice the "_STL" namespace instead of "std" but Boost.Thread is >built with the library that comes with VC++ 7.1, which of course uses >the "std" namespace. Unless STLport has some specific feature that >you need I suggest you use the standard library that comes with VC++ >7.1; it's a very good implementation. If you must use STLport then >you need to build Boost.Thread (and any other libraries with which >you share standard library types) using it. > Unfortunately, this whole roadtrip started with the need for STL collections to cross DLL boundaries, which is why I am using STLPort. The STL that comes with VC++ 7.1 doesn't (with the exception of string and vector). When I built boost, I built it with the vc7.1-stlport toolset, and I have the stlport library directory in my "additional library path". Along this line, I wonder if I need to be doing something special with the STLPort DLL? >_______________________________________________ >Boost-users mailing list >Boost-users(a)lists.boost.org >http://lists.boost.org/mailman/listinfo.cgi/boost-users _________________________________________________________________ MSN Toolbar provides one-click access to Hotmail from any Web page FREE download! http://toolbar.msn.click-url.com/go/onm00200413ave/direct/01/

2 1

RE: [Boost-users] boost::thread, boost::bind, and member functions
by Ben Hutchings 25 May '04

25 May '04

Mike Feldmeier <pooky_bunny(a)hotmail.com> wrote: [ Ben Hutchings wrote:] > > Mike Feldmeier <pooky_bunny(a)hotmail.com> wrote: <snip> > > > This consistently produces the linking error: > > > > > > converter.obj : error LNK2019: unresolved external symbol > > > "__declspec(dllimport) public: __thiscall boost::thread::thread( > > > class boost::function0<void,class > > > _STL::allocator<class boost::function_base> > const &)" > > > (__imp_??0thread@boost@@QAE@ABV?$function0@XV?$allocator@Vfunction > > > _base@boost@@@_STL@@@1@@Z) referenced in function "public: void > > > __thiscall mytest::test::converter::run(void)" > > > (?run@converter@test@mytest@@QAEXXZ) > > > >I think you aren't linking with the thread library. <snip> > I'm using Visual C++ 7.1, but using straight C++, no .NET. I've > defined the addtional library path (C:\boost\lib) and tried linking > (in the additional dependencies) with > boost_thread-vc71-mt-gdp-1_31.lib, boost_thread-vc71-mt-gdp.lib, > boost_thread-vc71-mt-p-1_31.lib, and boost_thread-vc71-mt-p.lib (one > at a time, of course), but I get the same error message with all of > them. <snip> I've worked it out now. In your main program you are using STLport - notice the "_STL" namespace instead of "std" but Boost.Thread is built with the library that comes with VC++ 7.1, which of course uses the "std" namespace. Unless STLport has some specific feature that you need I suggest you use the standard library that comes with VC++ 7.1; it's a very good implementation. If you must use STLport then you need to build Boost.Thread (and any other libraries with which you share standard library types) using it.

1 0

RE: [Boost-users] boost::thread, boost::bind, and member functions
by Mike Feldmeier 25 May '04

25 May '04

>From: "Ben Hutchings" <ben.hutchings(a)businesswebsoftware.com> >Reply-To: boost-users(a)lists.boost.org >To: <boost-users(a)lists.boost.org> >Subject: RE: [Boost-users] boost::thread, boost::bind, and member functions >Date: Tue, 25 May 2004 12:07:32 +0100 > >Mike Feldmeier <pooky_bunny(a)hotmail.com> wrote: > > I've seen variations of this come up in this newsgroup and elsewhere, > > but I have yet to find an answer that works for me. > > > > class threaded_manager > > { > > public: > > void start(void); > > }; > > > > threaded_manager mgr; > > > > boost::thread(boost::bind(&threaded_manager::start, &mgr)); > > > > This consistently produces the linking error: > > > > converter.obj : error LNK2019: unresolved external symbol > > "__declspec(dllimport) public: __thiscall boost::thread::thread(class > > boost::function0<void,class > > _STL::allocator<class boost::function_base> > const &)" > > (__imp_??0thread@boost@@QAE@ABV?$function0@XV?$allocator@Vfunction_bas > > e@boost@@@_STL@@@1@@Z) referenced in function "public: void __thiscall > > mytest::test::converter::run(void)" > > (?run@converter@test@mytest@@QAEXXZ) > >I think you aren't linking with the thread library. Many of the Boost >libraries (such as Boost.Bind) include their implementation entirely in >header files, so they will be compiled into your program as needed. >Boost.Thread doesn't; you need to build it as a library (and on Windows >it must be a DLL) and link it with your program. > I'm using Visual C++ 7.1, but using straight C++, no .NET. I've defined the addtional library path (C:\boost\lib) and tried linking (in the additional dependencies) with boost_thread-vc71-mt-gdp-1_31.lib, boost_thread-vc71-mt-gdp.lib, boost_thread-vc71-mt-p-1_31.lib, and boost_thread-vc71-mt-p.lib (one at a time, of course), but I get the same error message with all of them. > > Separating the two boost functions on to separate lines works fine: > > > > boost::bind(&threaded_manager::start, &mgr); > > boost::thread(); > > > > ..which indicates to me that bind is returning an object that is not > > compatible with thread, but I've seen multiple examples of just this > > type of call. ><snip> > >If that were the case you should see a compiler error. The two lines >above may work because the default constructor for boost::thread is >compiled inline whereas the other constructor must be linked in. >Having said that, though, neither v1.30 nor v1.31 has the default >constructor definition in the header, so I don't entirely understand >what's going on. Did you perhaps mistakenly declare a function >returning a boost::thread? > Thus far, this line (or two lines) are the only boost-related lines in my code. >Ben. > >_______________________________________________ >Boost-users mailing list >Boost-users(a)lists.boost.org >http://lists.boost.org/mailman/listinfo.cgi/boost-users Thanks, Mike _________________________________________________________________ Get 200+ ad-free, high-fidelity stations and LIVE Major League Baseball Gameday Audio! http://radio.msn.click-url.com/go/onm00200491ave/direct/01/

1 0

RE: [Boost-users] Regex++ Installation Problems
by Ben Hutchings 25 May '04

25 May '04

kinshuk srivastava <srivastavakinshuk(a)yahoo.co.in> wrote: > I had written earlier too regarding installation > problems with the regex++...sorry for not providing > the complete details last time..But I am again sending > the errors... > The Gcc compiler which m using is gcc3.2 nd the > operating system is SuSE 9.6...I think the regex++ > version is 331... > the following are the errors: <snip> > ../../../boost/regex/v3/regex_match.hpp:1937: Internal compiler error > in expand_call, at calls.c:3049 > Please submit a full bug report, > with preprocessed source if appropriate. > See <URL:http://www.gnu.org/software/gcc/bugs.html> > for instructions. Why didn't you just do what the error message said? You should have found this existing bug report: <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8701>. Anyway, this turns out to be a bug that SuSE introduced to its version of GCC. Go to them for a fix.

1 0

RE: [Boost-users] boost::thread, boost::bind, and member functions
by Ben Hutchings 25 May '04

25 May '04

Mike Feldmeier <pooky_bunny(a)hotmail.com> wrote: > I've seen variations of this come up in this newsgroup and elsewhere, > but I have yet to find an answer that works for me. > > class threaded_manager > { > public: > void start(void); > }; > > threaded_manager mgr; > > boost::thread(boost::bind(&threaded_manager::start, &mgr)); > > This consistently produces the linking error: > > converter.obj : error LNK2019: unresolved external symbol > "__declspec(dllimport) public: __thiscall boost::thread::thread(class > boost::function0<void,class > _STL::allocator<class boost::function_base> > const &)" > (__imp_??0thread@boost@@QAE@ABV?$function0@XV?$allocator@Vfunction_bas > e@boost@@@_STL@@@1@@Z) referenced in function "public: void __thiscall > mytest::test::converter::run(void)" > (?run@converter@test@mytest@@QAEXXZ) I think you aren't linking with the thread library. Many of the Boost libraries (such as Boost.Bind) include their implementation entirely in header files, so they will be compiled into your program as needed. Boost.Thread doesn't; you need to build it as a library (and on Windows it must be a DLL) and link it with your program. > Separating the two boost functions on to separate lines works fine: > > boost::bind(&threaded_manager::start, &mgr); > boost::thread(); > > ..which indicates to me that bind is returning an object that is not > compatible with thread, but I've seen multiple examples of just this > type of call. <snip> If that were the case you should see a compiler error. The two lines above may work because the default constructor for boost::thread is compiled inline whereas the other constructor must be linked in. Having said that, though, neither v1.30 nor v1.31 has the default constructor definition in the header, so I don't entirely understand what's going on. Did you perhaps mistakenly declare a function returning a boost::thread? Ben.

1 0

Boost.Test release notes typos
by Ross Boylan 25 May '04

25 May '04

I noticed a couple of typos in the latest release notes for Boost.Test, at http://cvs.sourceforge.net/viewcvs.py/boost/boost/libs/test/doc/release_not… It now reads, near the top, <LI>Floating point comaprison algorithm reworked (Is not backward compatible!!!) <UL> <LI><u>tolerance now expected in persent units</u></LI> That should be comparison in the first line and percent in the last.

2 1

boost::thread, boost::bind, and member functions
by Mike Feldmeier 24 May '04

24 May '04

I've seen variations of this come up in this newsgroup and elsewhere, but I have yet to find an answer that works for me. class threaded_manager { public: void start(void); }; threaded_manager mgr; boost::thread(boost::bind(&threaded_manager::start, &mgr)); This consistently produces the linking error: converter.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: __thiscall boost::thread::thread(class boost::function0<void,class _STL::allocator<class boost::function_base> > const &)" (__imp_??0thread@boost@@QAE@ABV?$function0@XV?$allocator@Vfunction_base@boos t@@@_STL@@@1@@Z) referenced in function "public: void __thiscall mytest::test::converter::run(void)" (?run@converter@test@mytest@@QAEXXZ) Separating the two boost functions on to separate lines works fine: boost::bind(&threaded_manager::start, &mgr); boost::thread(); ..which indicates to me that bind is returning an object that is not compatible with thread, but I've seen multiple examples of just this type of call. This is probably something simple, my two days of experience with Boost just doesn't appear to be sufficient. What in the world am I doing wrong? Thanks, Mike _________________________________________________________________ Stop worrying about overloading your inbox - get MSN Hotmail Extra Storage! http://join.msn.click-url.com/go/onm00200362ave/direct/01/

1 0