- Boost - lists.boost.org

[Date-time] Borland 5.6.4 / GCC 2.95 Linux regressions
by Aleksey Gurtovoy 09 Jan '05

09 Jan '05

See http://tinyurl.com/4y6tx. -- Aleksey Gurtovoy MetaCommunications Engineering

2 1

Determining interest for a thread library extension to handle blocking situations
by Roland Schwarz 09 Jan '05

09 Jan '05

Currently the threading library does not support for handling situations where a thread might be blocked on IO, in a platform independant way. While it is possible to write (low level) IO such as networking code that has the ability to be unblockable, the lack of an uniform interface seems unfortunate. Say thread B currently is blocking on a (third party) IO library. Now thread A needs to abandon thread B. How should this be done? Possible options are: 1) A schedules a cancel request to B 2) A calls a certain function of the IO library that, given a thread ID is able to unblock the current operation. Ad 1) this is currently not supported by boost thread, and given the rather controversial discussion about correct semantics in the past, it is unlikely to happen soon. Ad 2) This puts a lot of burden onto the user of the library. Interfaces also are likely to be different for various IO libs. Desirable would be a (free) function, say "alert(thread-id)" that is given the thread-id of B. When called by thread A, whatever is necessary to wake up the thread B will be done. The point is that my proposed library does not do the real actions, but only supply a framework that will allow the IO library to register a function to be called when it is time to break out of IO. To find out whether this is feasible I wrote a prototype implementation and an example to demonstrate the use of the interface. (Altough currently only available for MSVC.) My approach is two step. The first of which even might be interesting for a library on its own. 1) A "thdmbrptr" thread member pointer lib The intent of this library is to allow two threads to establish a shared memory space, without requiring the user code to pass any information. This basically does work like a thread local storage from inside the thread: boost::thread_member_ptr<myclass> pmyclass; All functions known from thread_specific_ptr are available, and so is semantics from inside the thread. Besides this another thread can get access to the data by: pmyclass[th]->foo(); where "th" is a thread id (or boost::thread*) and "foo()" is a function of "myclass". The lifetime of the myclass instance is managed by a shared_ptr. One reference is held by the thread (by means of a tss), a second is held by the boost::thread object that created the thread, and additional references might be held by other threads that obtained it by "*pmyclass[th]". 2) An "alert" lib The alert lib has two functions and a class object. alert(boost::thread* th) . . . to alert a thread bool alerted() . . . to find out (and reset) the alerted state of a thread class alerter . . . a class that will be instantiated on the stack. The constructor registers a (IO - ) lib defined function, The destructor unregisters this function. Some additional notes: I have been able to write a prototype implementation that 1) does not need any change to the current boost::thread 2) does not contain platform dependant code since it is built entirely on top of other boost libs. Altough it would by surely desirable to modify boost::thread to give a cleaner interface and improve performance. (Given the alert-ability of threads, a cancellation might later be built on top of it.) If it turns out, that there is interest in my proposal I will upload my files into the "vault". Thank you for your attention, Roland

2 2

[oopsla-results] Discussion of changes to submission process
by Jeff Garland 09 Jan '05

09 Jan '05

All - Since the base write-up of the OOPSLA results failed to spur really any discussion, I've written up a small proposal to tweak the submission process to include a mentor and to require a 'wiki under construction' page for each library. I've posted this on the Wiki and included it here for discussion. There are certainly more details to develop, but hopefully this email will start the process ;-) Jeff ---- http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?Proposed_Cha… The intent of this page is to serve as a focal point for disucssion of potential changes submissions process (http://www.boost.org/more/submission_process.htm) === Overview Of Proposed Process === * Learn about Boost. * Determine interest. * Add a Wiki Under Construction Page ('''new step''') * Preliminary submission. * Request Mentor ('''new step''') * Refinement. * Submission for review. * Formal Review. * Web site posting. * People page. * Lifecycle. === How Mentoring Might Work === The development of a boost library typically takes months/years from conception to finally becoming part of boost. To sucessfully navigate the obsticles requires lots of knowledge about how boost works. The basic role of a boost development mentor is to guide a new library developer thru the boost process. In essence to provide someone to help give new submitters a helping hand. The expectation is that a library mentor might spend a couple hours a month answering email questions to fulfill this role (if it exceeds this then it this process will not be practical. Almost all the boost developers are very busy people and we are now adding another thing to do). Some specific functions include: * Be a first reviewer / sounding board for the library developer * Answer questions about boost processes * Answer questions about boost build and other practices * Make sure the new developer is following the submission process Note that a new library developer is not restricted to using the mentor for asking questions -- in fact, they should be encouraged to use the mailing lists where a the larger group can help. === Wiki Under Construction Pages === One of the issues with the current Boost web structure is that it is quite difficult to find out about libraries that are in progress and it is difficult to others with similar interests. It was suggested that we formally add Wiki pages to track and organize this progress better. While this already exists to some extent in the LibrariesUnderConstruction Wiki page (http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?LibrariesUnd…) this page would be linked from the Boost mainpage and each library under construction would maintain it's own 'under construction page'. I've prototyped a new version of the under construction page (http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl?LibrariesUnd…) The idea is to keep the information on the main page small so that it can be rapidly scanned. Details will go on the page associated with each individual library. The page will have categories of development status as follows: Review Pending Stable but Evolving -- Not Yet Submitted for Review Preliminary On Hold Abandoned === New Boost Vault === There is a new file storage area that new boost developers can use to share their library with the world. http://boost-sandbox.sourceforge.net/vault/

6 20

Re: Singleton
by Dave Handley 09 Jan '05

09 Jan '05

Mikhail Glushenkov wrote: > What about adapting Loki's Singleton? It's the best Singleton > I know about and (probably) the most widely-known one. I agree that it is probably one of the best ones around. My only issues are: 1) Wouldn't it be better to use CRTP than the rather strange usage syntax that Loki uses with a typedef and a requirement to make the constructors/destructors private? It is remarkably easy if you are not familiar with the Singleton implementation in Loki to make your constructors/destructors public by mistake and then use them, whereas a CRTP solution could make the base constructors/destructors protected. 2) There are probably some more options that need to be included, for example making a Singleton be capable of destroying/recreating during the run of a program. Consider a singleton that is managing a print queue. For some reason all the printers go off-line, there is a potential for memory optimisation by closing down the print queue. If printers come back on line the print queue could come back on line - but that isn't possible (as far as I know) with Loki. 3) What issues are there with the licensing of Loki? David Greene wrote: > I think that's a good place to start. What other patterns should > we be looking at. We ought to start a wiki page. > > I would prefer to put the files in the sandbox so they are > versioned, have history, etc. The yahoo files section is > inconvenient due to the registration requirement. I would be happy to submit what I have to the sandbox - who do I contact to get on the sandbox as a developer, and is there a set of submission guidelines? Where would the wiki page be? I also notice from a quick browse of the sandbox that there is a set of classes for visitors, and that they haven't really been touched for 2 years. Did these ever make it into boost? Is there any documentation for them? And could we perhaps look there for a starting point for the visitor side of things? In my view, the best start for a list of patterns to look at is probably the GoF book! I have written generic code in the past for: 1) Flyweights 2) Composites 3) Visitors 4) Singletons 5) Bridge (just to link the 2 classes easily) There is certainly scope to include: 1) Factory Method 2) Abstract Factory 3) Decorator 4) Chain of responsibility However, if we are to have a go at a project like this, I would suggest keeping the initial submission list quite short, and then if there is some interest further down track, follow on with more patterns. Dave

5 4

Boost 1.32.0 FreeBSD port ready -- please review patches
by Simon Barner 08 Jan '05

08 Jan '05

Hello Boosters, I am maintaining the FreeBSD port of Boost, and I'd like to ask you to review the changes I had to make in order to get things to work and possibly to merge some of them into your CVS. First some information about Boost on the FreeBSD platform... There are two supported platforms: - FreeBSD 5.3, with gcc 3.4.2, wchar support - FreeBSD 4.10/11 with gcc 2.95.4, no wchar support, build with stlport 4.6.2 and spirit 1.6.2 to overcome compiler insufficiencies. Sprit 1.6.2 is obtained form http://spirit.sf.net, so I wounder if you guys can do anything about it, but it would be great to have tarball that uses UN*X encoded source files (i.e. without CRLF as line separator). If you don't have a FreeBSD installation, you can find the port skeleton (which is basically a set of patches and scripts needed to build a software package) here: http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/boost/ I will now present all of the patches I made (please don't beat me if I did something ugly or something which might hurt a Boost developer's feelings ;-) The links above a particular patch enable you to download it from FreeBSD's CVS. After that I'll describe briefly the intention of that patch, which is quoted below. One of the intentions of this posting is to check whether I did my changes at the right places, or if the are crude hacks (I suspect some of my changes to the configuration files fall into this category). A total of 8 patches follows, but don't be afraid, most of it is FreeBSD specific, but I wonder if some patches could be merged into Boost's CVS. http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/devel/boost/files/pa… This patch enables wchar support on FreeBSD 5 and disables it on older versions. Unfortunately, I can't remember, why BOOST_NO_INCLASS_MEMBER_INITIALIZATION was necessary, but it won't hurt, will it? --- boost/config/platform/bsd.hpp.orig Fri Feb 27 14:13:00 2004 +++ boost/config/platform/bsd.hpp Wed Dec 15 16:01:21 2004 @@ -39,9 +39,20 @@ #endif // -// No wide character support in the BSD header files: +// Enable wide character support on FreeBSD 5 and above // -#define BOOST_NO_CWCHAR +#if defined(__FreeBSD__) && (__FreeBSD__ >= 5) +# undef BOOST_NO_CWCHAR +# undef BOOST_NO_SWPRINTF +# undef BOOST_NO_CWCTYPE +# undef BOOST_DEDUCED_TYPENAME +#else +# define BOOST_NO_CWCHAR +# define BOOST_NO_SWPRINTF +# define BOOST_NO_CWCTYPE +#endif + +#define BOOST_NO_INCLASS_MEMBER_INITIALIZATION // // The BSD <ctype.h> has macros only, no functions: http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/devel/boost/files/pa… Starting with Boost v. 1.31.0, I intend to bump the shared library version number with every boost release in order to prevent from problems that are caused by ABI incompatiblities. (This is a requirement of the FreeBSD Ports Collection). --- tools/build/v1/allyourbase.jam.orig Wed Feb 18 14:04:28 2004 +++ tools/build/v1/allyourbase.jam Wed Feb 18 14:02:44 2004 @@ -457,7 +457,7 @@ SPLITPATH ?= ":" ; # dwa -- added missing SPLITPATH STDHDRS ?= /usr/include ; SUFEXE ?= "" ; -SUFDLL ?= .so ; +SUFDLL ?= .so.2 ; SUFLIB ?= .a ; SUFOBJ ?= .o ; PREDLL ?= lib ; http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/devel/boost/files/pa… Another requirement of the Ports Collection: Libraries are installed into the same location regardless of built time options. --- tools/build/v1/boost-base.jam.orig Wed Jan 28 23:52:25 2004 +++ tools/build/v1/boost-base.jam Wed Feb 18 14:06:58 2004 @@ -2621,11 +2621,6 @@ local version-tag = [ MATCH "^([^.]+).([^.]+)" : $(version-number[1]) ] ; version-tag = $(version-tag:J="_") ; - tags += $(toolset-tag:J=) ; - tags += $(thread-tag:J=) ; - tags += $(runtime-tag:J=) ; - tags += $(version-tag) ; - if $(tags) { return $(properties) <*><*><tag><prefix>-$(tags:J=-) ; http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/devel/boost/files/pa… Depending on the FreeBSD version, different compiler and linker options are needed. These option are provided by two environment variables PTHREAD_CFLAGS and PTHREAD_LIBS, but I found no other way of getting the right values into Boost's config files than patching that will placeholder values and using sed(1) to replace those dummies with the actual ones. --- tools/build/v1/gcc-stlport-tools.jam.orig Mon Dec 13 19:13:56 2004 +++ tools/build/v1/gcc-stlport-tools.jam Mon Dec 13 19:14:18 2004 @@ -40,7 +40,7 @@ } case *BSD : { - flags gcc LINKFLAGS <stlport-iostream>on : -pthread ; + flags gcc LINKFLAGS <stlport-iostream>on : %%PTHREAD_LIBS%% ; } case IRIX : { http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/devel/boost/files/pa… The first hunk of the patch is needed because ports in FreeBSD are supposed to obey some global CFLAGS settings (whose optimiziation settings would be overridden by -O0). The second hunk is similar to the last patch. --- tools/build/v1/gcc-tools.jam.orig Thu Jan 22 05:11:52 2004 +++ tools/build/v1/gcc-tools.jam Wed Feb 18 12:57:30 2004 @@ -61,7 +61,7 @@ flags gcc LINKFLAGS <runtime-link>static : -static ; flags gcc CFLAGS <debug-symbols>on : -g ; flags gcc LINKFLAGS <debug-symbols>on : -g ; -flags gcc CFLAGS <optimization>off : -O0 ; +flags gcc CFLAGS <optimization>off : ; flags gcc CFLAGS <optimization>speed : -O3 ; # Other optimizations we might want for GCC @@ -125,8 +125,8 @@ } case *BSD : { - flags gcc CFLAGS <threading>multi : -pthread ; - flags gcc LINKFLAGS <threading>multi : -pthread ; + flags gcc CFLAGS <threading>multi : %%PTHREAD_CFLAGS%% ; + flags gcc LINKFLAGS <threading>multi : %%PTHREAD_LIBS%% ; # there is no -lrt on BSD } case IRIX : http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/devel/boost/files/FB… This patch is needed for FreeBSD 4 (gcc 2.95) only! I am sure the first hunk could be solved more cleanly by some configuration option, but where? The second hunk is something I am really unsure about, and which I suppose has something to do with FreeBSD's (or gcc 2.95's?) implementation of std::codecvt. Is this necessary on other platforms? --- boost/program_options/detail/utf8_codecvt_facet.hpp.orig Mon Dec 13 18:48:58 2004 +++ boost/program_options/detail/utf8_codecvt_facet.hpp Mon Dec 13 18:49:51 2004 @@ -67,7 +67,7 @@ #elif defined(BOOST_NO_STDC_NAMESPACE) typedef std::mbstate_t mbstate_t; namespace std{ - using ::codecvt; + using std::codecvt; } // namespace std #endif @@ -81,7 +81,7 @@ { public: explicit utf8_codecvt_facet_wchar_t(std::size_t no_locale_manage=0) - : std::codecvt<wchar_t, char, mbstate_t>(no_locale_manage) + : std::codecvt<wchar_t, char, mbstate_t>() // FIXME {} protected: virtual std::codecvt_base::result do_in( http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/devel/boost/files/FB… FreeBSD 4 only! This disables the build of the wchar version of the serialization library on this platform. I simply couldn't get it to work, AFAIK libc is not ready for wide characters on this platform. --- libs/serialization/build/Jamfile.orig Mon Dec 13 18:36:52 2004 +++ libs/serialization/build/Jamfile Mon Dec 13 18:37:28 2004 @@ -90,12 +90,10 @@ install serialization lib : <lib>boost_serialization - <lib>boost_wserialization ; stage stage/lib : <lib>boost_serialization - <lib>boost_wserialization : <locate>$(BOOST_ROOT) common-stage-tag http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/ports/devel/boost/files/FB… FreeBSD 5 only! This works around a bug in FreeBSD's gcc 3.4.2, which has been reported to the maintainer of FreeBSD's system compiler. --- boost/python/detail/config.hpp.orig Tue Dec 14 14:17:42 2004 +++ boost/python/detail/config.hpp Tue Dec 14 14:19:36 2004 @@ -110,7 +110,11 @@ # define BOOST_PYTHON_OFFSETOF(s_name, s_member) \ ((size_t)__INTADDR__(&(((s_name *)0)->s_member))) #else -# define BOOST_PYTHON_OFFSETOF offsetof +// workaround from http://www.freebsd.org/cgi/query-pr.cgi?pr=72307 +#define BOOST_PYTHON_OFFSETOF(TYPE, MEMBER)\ + (__offsetof__ (reinterpret_cast <size_t>\ + (&reinterpret_cast <const volatile char &>\ + (static_cast<TYPE *> (0)->MEMBER)))) #endif #endif // CONFIG_DWA052200_H_

9 19

OS X Link Problems
by Alan 08 Jan '05

08 Jan '05

I built boost thus: bjam "-sTOOLS=darwin" -sBUILD="debug release <runtime-link>static/dynamic" After hacking around the xml_grammar.cpp problems, I get the link errors where the following functions cannot be found. (Removed a lot of extra stuff to try and display only the library and missing function. If you'd like to see all 183 lines that is possible.) I'm wondering if some test functions that are not meant to be in the library are referenced by something included in the library. darwin-Link-DyLib-action bin/boost/libs/test/build/libboost_prg_exec_monitor.dylib/darwin/debug/runtime-link-static/shared-linkable-true/libboost_prg_exec_monitor-sd-1_32.dylib ld: Undefined symbols: cpp_main(int, char**) darwin-Link-DyLib-action bin/boost/libs/test/build/libboost_prg_exec_monitor.dylib/darwin/debug/shared-linkable-true/libboost_prg_exec_monitor-d-1_32.dylib ld: Undefined symbols: cpp_main(int, char**) darwin-Link-DyLib-action bin/boost/libs/test/build/libboost_prg_exec_monitor.dylib/darwin/debug/shared-linkable-true/libboost_prg_exec_monitor-d-1_32.dylib ld: Undefined symbols: cpp_main(int, char**) darwin-Link-DyLib-action bin/boost/libs/test/build/libboost_prg_exec_monitor.dylib/darwin/release/runtime-link-static/shared-linkable-true/libboost_prg_exec_monitor-s-1_32.dylibld: Undefined symbols:cpp_main(int, char**) darwin-Link-DyLib-action bin/boost/libs/test/build/libboost_prg_exec_monitor.dylib/darwin/release/shared-linkable-true/libboost_prg_exec_monitor-1_32.dylib ld: Undefined symbols: cpp_main(int, char**) darwin-Link-DyLib-action bin/boost/libs/test/build/libboost_test_exec_monitor.dylib/darwin/debug/runtime-link-static/shared-linkable-true/libboost_test_exec_monitor-sd-1_32.dylibld: Undefined symbols:test_main(int, char**) darwin-Link-DyLib-action bin/boost/libs/test/build/libboost_test_exec_monitor.dylib/darwin/debug/shared-linkable-true/libboost_test_exec_monitor-d-1_32.dylibld: Undefined symbols:test_main(int, char**) darwin-Link-DyLib-action bin/boost/libs/test/build/libboost_test_exec_monitor.dylib/darwin/release/shared-linkable-true/libboost_test_exec_monitor-1_32.dylibld: Undefined symbols:test_main(int, char**) darwin-Link-DyLib-action bin/boost/libs/test/build/libboost_unit_test_framework.dylib/darwin/debug/runtime-link-static/shared-linkable-true/libboost_unit_test_framework-sd-1_32.dylibld: Undefined symbols:init_unit_test_suite(int, char**) -- Alan Gutierrez - alan(a)engrm.com

6 7

Any interest in a library for supporting program reuse?
by christopher diggins 08 Jan '05

08 Jan '05

Hi all, the compulsive coder here again, I've just written in a working prototype of a library for writing C++ programs which can be treated in C++ code like Unix filters, i.e. redirected to and from streams, and other programs. For instance: fstream f("c:\\tmp.txt"); stringstream s; HelloWorldProgram() > f > UpperCaseProgram() > s; Is there any interest in this kind of library, for boost? I am using it for writing test and demonstration programs of libraries, but I think it has a lot of other uses. The source code and a more detailed explanation is at http://www.codeproject.com/useritems/program-objects.asp Christopher Diggins http://www.cdiggins.com http://www.heron-language.com

7 13

RE: [boost] Re: Bizarre Lambda bind() problem with Base class types
by Brian Braatz 08 Jan '05

08 Jan '05

> -----Original Message----- > Brian Braatz wrote: > > With the following code, If you UNCOMMENT the "// public : Base" line, > > you get compiler errors (????) > > > > I have tested this with MS VC 7.1 against both 1.31 and 1.32 versions of > > boost with the same results. > > > > Any idea why this is happening? (full sample code I wrote is attached) > >[snip] > > std::string ReturnAString(); > > [snip] > > bind(Base::ReturnAString,_1); > [ Reece Wrote] > This is the problem. Try: > bind(Base::ReturnAString); > or: > bind(&Base::ReturnAString,this); > [Brian Braatz] THANK YOU BOTH REECE AND DANIEL :) (!!!!!!!!!!!!!!!) That fixed it. What is STRANGE is that "sometimes" bind(Base::ReturnAString) works ironically, I have about 40 calls that use that syntax that work just fine. I noticed in the docs, when you have a inline functor, the docs use > bind(Base::ReturnAString); But when you have something that was not inline (??) you use: > bind(&Base::ReturnAString); I was never clear on when you and when you do NOT use the "&" with the bind() syntax..... I will convert everything in my "real code" to using the & always. Question: Does anyone know when you should and should not use the & in a bind call? Or is this is compile time checking hole that exists due to the mechanisms bind relies upon? OR Am I a complete idiot? (I find it important to always hold open this option as a possibility in everything)

3 2

Bizarre Lambda bind() problem with Base class types
by Brian Braatz 08 Jan '05

08 Jan '05

With the following code, If you UNCOMMENT the "// public : Base" line, you get compiler errors (????) I have tested this with MS VC 7.1 against both 1.31 and 1.32 versions of boost with the same results. Any idea why this is happening? (full sample code I wrote is attached) using namespace boost::lambda; namespace Tests { class Base { public: std::string ReturnAString() { std::cout << "hi"; } }; class Derived // : public Base // UNCOMMENT ME to see the errors { public: void Func() { bind(Base::ReturnAString,_1); } }; }; // namespace Tests My Compiler errors are this: ------ Build started: Project: Test_LambdaProblem, Configuration: Debug Win32 ------ Compiling... Test_LambdaProblem.cpp c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<10,boost::lambda::function_action<10,Result>>,detail::bin d_tuple_mapper<const Arg1,const Arg2,const Arg3,const Arg4,const Arg5,const Arg6,const Arg7,const Arg8,const Arg9,const Arg10>::type>> boost::lambda::bind(const Arg1 &,const Arg2 &,const Arg3 &,const Arg4 &,const Arg5 &,const Arg6 &,const Arg7 &,const Arg8 &,const Arg9 &,const Arg10 &)' : expects 10 arguments - 2 provided c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(1743) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<Arity,Act>,detail::bind_tuple_mapper<const Arg1,const Arg2,const Arg3,const Arg4,const Arg5,const Arg6,const Arg7,const Arg8,const Arg9,const Arg10>::type>> boost::lambda::bind(const Arg1 &,const Arg2 &,const Arg3 &,const Arg4 &,const Arg5 &,const Arg6 &,const Arg7 &,const Arg8 &,const Arg9 &,const Arg10 &)' : expects 10 arguments - 2 provided with [ Arity=10, Act=boost::lambda::function_action<10> ] c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(1710) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<10,boost::lambda::function_action<10,Result>>,detail::bin d_tuple_mapper<Result(__cdecl &)(Par1,Par2,Par3,Par4,Par5,Par6,Par7,Par8,Par9),const Arg2,const Arg3,const Arg4,const Arg5,const Arg6,const Arg7,const Arg8,const Arg9,const Arg10>::type>> boost::lambda::bind(Result (__cdecl &)(Par1,Par2,Par3,Par4,Par5,Par6,Par7,Par8,Par9),const Arg2 &,const Arg3 &,const Arg4 &,const Arg5 &,const Arg6 &,const Arg7 &,const Arg8 &,const Arg9 &,const Arg10 &)' : expects 10 arguments - 2 provided c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(1673) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<9,boost::lambda::function_action<9,Result>>,detail::bind_ tuple_mapper<const Arg1,const Arg2,const Arg3,const Arg4,const Arg5,const Arg6,const Arg7,const Arg8,const Arg9>::type>> boost::lambda::bind(const Arg1 &,const Arg2 &,const Arg3 &,const Arg4 &,const Arg5 &,const Arg6 &,const Arg7 &,const Arg8 &,const Arg9 &)' : expects 9 arguments - 2 provided c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(1526) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<Arity,Act>,detail::bind_tuple_mapper<const Arg1,const Arg2,const Arg3,const Arg4,const Arg5,const Arg6,const Arg7,const Arg8,const Arg9>::type>> boost::lambda::bind(const Arg1 &,const Arg2 &,const Arg3 &,const Arg4 &,const Arg5 &,const Arg6 &,const Arg7 &,const Arg8 &,const Arg9 &)' : expects 9 arguments - 2 provided with [ Arity=9, Act=boost::lambda::function_action<9> ] c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(1494) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<9,boost::lambda::function_action<9,Result>>,detail::bind_ tuple_mapper<Result(__cdecl &)(Par1,Par2,Par3,Par4,Par5,Par6,Par7,Par8),const Arg2,const Arg3,const Arg4,const Arg5,const Arg6,const Arg7,const Arg8,const Arg9>::type>> boost::lambda::bind(Result (__cdecl &)(Par1,Par2,Par3,Par4,Par5,Par6,Par7,Par8),const Arg2 &,const Arg3 &,const Arg4 &,const Arg5 &,const Arg6 &,const Arg7 &,const Arg8 &,const Arg9 &)' : expects 9 arguments - 2 provided c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(1458) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<8,boost::lambda::function_action<8,Result>>,detail::bind_ tuple_mapper<const Arg1,const Arg2,const Arg3,const Arg4,const Arg5,const Arg6,const Arg7,const Arg8>::type>> boost::lambda::bind(const Arg1 &,const Arg2 &,const Arg3 &,const Arg4 &,const Arg5 &,const Arg6 &,const Arg7 &,const Arg8 &)' : expects 8 arguments - 2 provided c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(1322) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<Arity,Act>,detail::bind_tuple_mapper<const Arg1,const Arg2,const Arg3,const Arg4,const Arg5,const Arg6,const Arg7,const Arg8>::type>> boost::lambda::bind(const Arg1 &,const Arg2 &,const Arg3 &,const Arg4 &,const Arg5 &,const Arg6 &,const Arg7 &,const Arg8 &)' : expects 8 arguments - 2 provided with [ Arity=8, Act=boost::lambda::function_action<8> ] c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(1291) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<8,boost::lambda::function_action<8,Result>>,detail::bind_ tuple_mapper<Result(__cdecl &)(Par1,Par2,Par3,Par4,Par5,Par6,Par7),const Arg2,const Arg3,const Arg4,const Arg5,const Arg6,const Arg7,const Arg8>::type>> boost::lambda::bind(Result (__cdecl &)(Par1,Par2,Par3,Par4,Par5,Par6,Par7),const Arg2 &,const Arg3 &,const Arg4 &,const Arg5 &,const Arg6 &,const Arg7 &,const Arg8 &)' : expects 8 arguments - 2 provided c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(1257) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<7,boost::lambda::function_action<7,Result>>,detail::bind_ tuple_mapper<const Arg1,const Arg2,const Arg3,const Arg4,const Arg5,const Arg6,const Arg7>::type>> boost::lambda::bind(const Arg1 &,const Arg2 &,const Arg3 &,const Arg4 &,const Arg5 &,const Arg6 &,const Arg7 &)' : expects 7 arguments - 2 provided c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(1123) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<Arity,Act>,detail::bind_tuple_mapper<const Arg1,const Arg2,const Arg3,const Arg4,const Arg5,const Arg6,const Arg7>::type>> boost::lambda::bind(const Arg1 &,const Arg2 &,const Arg3 &,const Arg4 &,const Arg5 &,const Arg6 &,const Arg7 &)' : expects 7 arguments - 2 provided with [ Arity=7, Act=boost::lambda::function_action<7> ] c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(1092) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<7,boost::lambda::function_action<7,Result>>,detail::bind_ tuple_mapper<Result(__cdecl &)(Par1,Par2,Par3,Par4,Par5,Par6),const Arg2,const Arg3,const Arg4,const Arg5,const Arg6,const Arg7>::type>> boost::lambda::bind(Result (__cdecl &)(Par1,Par2,Par3,Par4,Par5,Par6),const Arg2 &,const Arg3 &,const Arg4 &,const Arg5 &,const Arg6 &,const Arg7 &)' : expects 7 arguments - 2 provided c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(1058) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<6,boost::lambda::function_action<6,Result>>,detail::bind_ tuple_mapper<const Arg1,const Arg2,const Arg3,const Arg4,const Arg5,const Arg6>::type>> boost::lambda::bind(const Arg1 &,const Arg2 &,const Arg3 &,const Arg4 &,const Arg5 &,const Arg6 &)' : expects 6 arguments - 2 provided c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(927) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<Arity,Act>,detail::bind_tuple_mapper<const Arg1,const Arg2,const Arg3,const Arg4,const Arg5,const Arg6>::type>> boost::lambda::bind(const Arg1 &,const Arg2 &,const Arg3 &,const Arg4 &,const Arg5 &,const Arg6 &)' : expects 6 arguments - 2 provided with [ Arity=6, Act=boost::lambda::function_action<6> ] c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(899) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<6,boost::lambda::function_action<6,Result>>,detail::bind_ tuple_mapper<Result(__cdecl &)(Par1,Par2,Par3,Par4,Par5),const Arg2,const Arg3,const Arg4,const Arg5,const Arg6>::type>> boost::lambda::bind(Result (__cdecl &)(Par1,Par2,Par3,Par4,Par5),const Arg2 &,const Arg3 &,const Arg4 &,const Arg5 &,const Arg6 &)' : expects 6 arguments - 2 provided c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(867) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<5,boost::lambda::function_action<5,Result>>,detail::bind_ tuple_mapper<const Arg1,const Arg2,const Arg3,const Arg4,const Arg5>::type>> boost::lambda::bind(const Arg1 &,const Arg2 &,const Arg3 &,const Arg4 &,const Arg5 &)' : expects 5 arguments - 2 provided c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(738) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<Arity,Act>,detail::bind_tuple_mapper<const Arg1,const Arg2,const Arg3,const Arg4,const Arg5>::type>> boost::lambda::bind(const Arg1 &,const Arg2 &,const Arg3 &,const Arg4 &,const Arg5 &)' : expects 5 arguments - 2 provided with [ Arity=5, Act=boost::lambda::function_action<5> ] c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(710) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<5,boost::lambda::function_action<5,Result>>,detail::bind_ tuple_mapper<Result(__cdecl &)(Par1,Par2,Par3,Par4),const Arg2,const Arg3,const Arg4,const Arg5>::type>> boost::lambda::bind(Result (__cdecl &)(Par1,Par2,Par3,Par4),const Arg2 &,const Arg3 &,const Arg4 &,const Arg5 &)' : expects 5 arguments - 2 provided c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(679) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<4,boost::lambda::function_action<4,Result>>,detail::bind_ tuple_mapper<const Arg1,const Arg2,const Arg3,const Arg4>::type>> boost::lambda::bind(const Arg1 &,const Arg2 &,const Arg3 &,const Arg4 &)' : expects 4 arguments - 2 provided c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(558) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<Arity,Act>,detail::bind_tuple_mapper<const Arg1,const Arg2,const Arg3,const Arg4>::type>> boost::lambda::bind(const Arg1 &,const Arg2 &,const Arg3 &,const Arg4 &)' : expects 4 arguments - 2 provided with [ Arity=4, Act=boost::lambda::function_action<4> ] c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(532) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<4,boost::lambda::function_action<4,Result>>,detail::bind_ tuple_mapper<Result(__cdecl &)(Par1,Par2,Par3),const Arg2,const Arg3,const Arg4>::type>> boost::lambda::bind(Result (__cdecl &)(Par1,Par2,Par3),const Arg2 &,const Arg3 &,const Arg4 &)' : expects 4 arguments - 2 provided c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(503) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<3,boost::lambda::function_action<3,Result>>,detail::bind_ tuple_mapper<const Arg1,const Arg2,const Arg3>::type>> boost::lambda::bind(const Arg1 &,const Arg2 &,const Arg3 &)' : expects 3 arguments - 2 provided c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(387) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<Arity,Act>,detail::bind_tuple_mapper<const Arg1,const Arg2,const Arg3>::type>> boost::lambda::bind(const Arg1 &,const Arg2 &,const Arg3 &)' : expects 3 arguments - 2 provided with [ Arity=3, Act=boost::lambda::function_action<3> ] c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(361) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<3,boost::lambda::function_action<3,Result>>,detail::bind_ tuple_mapper<Result(__cdecl &)(Par1,Par2),const Arg2,const Arg3>::type>> boost::lambda::bind(Result (__cdecl &)(Par1,Par2),const Arg2 &,const Arg3 &)' : expects 3 arguments - 2 provided c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(333) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2784: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<2,boost::lambda::function_action<2,Result>>,detail::bind_ tuple_mapper<const Arg1,const Arg2>::type>> boost::lambda::bind(const Arg1 &,const Arg2 &)' : could not deduce template argument for 'overloaded function type' from 'overloaded function type' c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(232) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2784: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<2,boost::lambda::function_action<2,Result>>,detail::bind_ tuple_mapper<const Arg1,const Arg2>::type>> boost::lambda::bind(const Arg1 &,const Arg2 &)' : could not deduce template argument for 'overloaded function type' from 'overloaded function type' c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(232) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2784: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<Arity,Act>,detail::bind_tuple_mapper<const Arg1,const Arg2>::type>> boost::lambda::bind(const Arg1 &,const Arg2 &)' : could not deduce template argument for 'overloaded function type' from 'overloaded function type' with [ Arity=2, Act=boost::lambda::function_action<2> ] c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(212) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2784: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<Arity,Act>,detail::bind_tuple_mapper<const Arg1,const Arg2>::type>> boost::lambda::bind(const Arg1 &,const Arg2 &)' : could not deduce template argument for 'overloaded function type' from 'overloaded function type' with [ Arity=2, Act=boost::lambda::function_action<2> ] c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(212) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2784: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<2,boost::lambda::function_action<2,Result>>,detail::bind_ tuple_mapper<Result(__cdecl &)(Par1),const Arg2>::type>> boost::lambda::bind(Result (__cdecl &)(Par1),const Arg2 &)' : could not deduce template argument for 'overloaded function type' from 'overloaded function type' c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(190) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2784: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<2,boost::lambda::function_action<2,Result>>,detail::bind_ tuple_mapper<Result(__cdecl &)(Par1),const Arg2>::type>> boost::lambda::bind(Result (__cdecl &)(Par1),const Arg2 &)' : could not deduce template argument for 'overloaded function type' from 'overloaded function type' c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(190) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<1,boost::lambda::function_action<1,Result>>,detail::bind_ tuple_mapper<const Arg1>::type>> boost::lambda::bind(const Arg1 &)' : expects 1 arguments - 2 provided c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(91) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<Arity,Act>,detail::bind_tuple_mapper<const Arg1>::type>> boost::lambda::bind(const Arg1 &)' : expects 1 arguments - 2 provided with [ Arity=1, Act=boost::lambda::function_action<1> ] c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(71) : see declaration of 'boost::lambda::bind' c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\Test_Lam bdaProblem.cpp(38) : error C2780: 'const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost:: lambda::action<1,boost::lambda::function_action<1,Result>>,detail::bind_ tuple_mapper<Result(__cdecl &)(void)>::type>> boost::lambda::bind(Result (__cdecl &)(void))' : expects 1 arguments - 2 provided c:\Data\Rmtg\Root\_Common\_Lib\Boost\V_1_32\boost\lambda\detail\bind_fun ctions.hpp(49) : see declaration of 'boost::lambda::bind' Build log was saved at "file://c:\Data\Rmtg\Root\_Common\_Lib\Rmx\V_0_02\Exp\Src\LambdaProblem\ _Prj\MsVc_V71\Debug\BuildLog.htm" Test_LambdaProblem - 33 error(s), 0 warning(s) ---------------------- Done ---------------------- Build: 0 succeeded, 1 failed, 0 skipped

4 3

thread lib patch
by François Dumont 08 Jan '05

08 Jan '05

Using MSVC6, STLport 5.0 beta, february 2003 SDK under Windows XP I failed to build thread library because of a missing include. In read_write_mutex.cpp, tchar.h contains _sntprintf macro definition but not the functions definition hidden behind this macro. Those are in stdio.h. Maybe this file was included in a previous version of STLport but it is not anymore. I am also surprised that those files are included if BOOST_HAS_WINTHREADS is defined and symbos coming from them are used if WINVER is defined. Isn't there a little inconsistency? Bests

1 0