- Boost - lists.boost.org

[fusion] VC8 specific error
by John Maddock 05 Sep '10

05 Sep '10

I'm getting the following error from fusion only when using VC8: ..\..\..\boost/fusion/sequence/intrinsic/at.hpp(59) : error C2504: 'boost::fusion::extension::at_impl<Tag>::apply<Sequence,N>' : base class undefined with [ Tag=boost::fusion::non_fusion_tag ] and [ Sequence=const boost::tuples::tuple<double,double>, N=boost::mpl::int_<0> ] ..\..\..\boost/fusion/sequence/intrinsic/at.hpp(64) : see reference to class template instantiation 'boost::fusion::result_of::at<Sequence,N>' being compiled with [ Sequence=const boost::tuples::tuple<double,double>, N=boost::mpl::int_<0> ] ..\..\..\boost/math/tools/roots.hpp(47) : see reference to class template instantiation 'boost::fusion::result_of::at_c<Sequence,N>' being compiled with [ Sequence=const boost::tuples::tuple<double,double>, N=0 ] ..\..\..\boost/math/tools/roots.hpp(225) : see reference to function template instantiation 'void boost::math::tools::detail::unpack<boost::tuples::tuple<T0,T1>,T,T>(const Tuple &,T &,U &)' being compiled with [ T0=double, T1=double, T=double, Tuple=boost::tuples::tuple<double,double>, U=double ] compile_test\tools_roots_concept_test.cpp(115) : see reference to function template instantiation 'T boost::math::tools::newton_raphson_iterate<F2t,double>(F,T,T,T,int,boost::uintmax_t &)' being compiled with [ T=double, F=F2t ] The code is simply calling boost::fusion::get<N>() on a fusion tuple, and after including <boost/fusion/tuple.hpp>. Any ideas? This is with Trunk BTW. Cheers, John.

2 2

[NVL++]: new library and utilities
by Manfred Doudar 04 Sep '10

04 Sep '10

Hello List, Have recently released a series of libraries aimed at facilitating computer-vision tasks - taking out much of the boiler-plate associated with connecting to multiple cameras, and image streams generally. Work that is largely the product of almost 1.5 years work, using OpenCV as a back-end, but thread-safe, and all in modern C++, and largely header-file only. For those not particularly interested in computer-vision, there are libraries and miscellaneous utilities that may be of interest, in particular: - a library wrapper over Boost.Thread (not entirely complete, but covers majority of use-cases); and makes threading less error-prone - a library for parsing delimited strings (csv, etc) - a library for parsing command-line options (expresses intent better than Boost.Program_options, betters in some areas, lacks in others) - a library that with a bit more of effort can be made stand-alone for streaming ("chaining") of algorithms, though binders are common-place, some work herein presents alternative approaches. [[Documentation]]: is available, but not of Boost quality, however it is sufficient. Depending upon reaction, what I do with these libraries, depends largely upon feedback I get. [[License]]: largely C++ Boost license, with the exception of a few 3rd-party libs included in the package. [[Platform]]: developed & tested on Linux; compiles with GCC-4.4.2 [[Where to get it]]: for the time being can be found here (until comms at work can get their act together and put up on their open-website) - http://users.cecs.anu.edu.au/~manfredd ..there's only one file there: nvl++.tar.bz2 Cheers, -- Manfred

2 3

Re: [boost] [gil] Who has a big-endian machine?
by Belcourt, Kenneth 03 Sep '10

03 Sep '10

On Sep 1, 2010, at 1:24 PM, Belcourt, Kenneth wrote: > > On Sep 1, 2010, at 12:05 PM, Christian Henning wrote: > >> Hi there, could someone with a big-endian machine run the following >> code with the latest gil code from the trunk? > ./ibm.hw purple.sandia.gov: 31488 MB 8 CPU PowerPC_POWER5 model IBM, 9118-575 > xlC -g -I./boost-trunk gil.cpp > ./a.out Assertion failed: v1 == 6, file gil.cpp, line 47 Abort (core dumped) Same source code. -- Noel

2 6

Towards a Warning free code policy proposal
by vicente.botet 03 Sep '10

03 Sep '10

Hi all, Last year there where two long threads about Boost Warning policy. If I'm not wrong nothing was concluded. I think that we can have two warning policies: one respect to the Boost users and one internal for Boost developement. We can consider that Boost headers can be used by the users as system headers, so no warning is reported for these files. The main advantage I see is that it allows the users to don't mix the warnings comming from Boost and their own warnings. Next follows a way to disable completly warnings for 3 compilers: Any Boost header file could be surrounded by #if defined __GNUC__ #pragma GCC system_header #elif defined __SUNPRO_CC #pragma disable_warn #elif defined _MSC_VER #pragma warning(push, 1) #endif and #if defined __SUNPRO_CC #pragma enable_warn #elif defined _MSC_VER #pragma warning(pop) #endif As we want the developer to be able to catch and eliminate as many warning as possible we need some conditional compilation that allows us to enable the warning reporting internally. These could also be useful for users that prefer to see the Boost warnings. Boost.Exception uses already this policy, sourronding some of its files with #if defined(__GNUC__) && !defined(BOOST_EXCEPTION_ENABLE_WARNINGS) #pragma GCC system_header #endif #if defined(_MSC_VER) && !defined(BOOST_EXCEPTION_ENABLE_WARNINGS) #pragma warning(push,1) #endif and #if defined(_MSC_VER) && !defined(BOOST_EXCEPTION_ENABLE_WARNINGS) #pragma warning(pop) #endif I propose to extend this to a 2-level enabling warning system BOOST_ENABLE_WARNINGS: If defined, enable warnings for all the Boost libraries BOOST_<LIB>_ENABLE_WARNINGS: If defined, enable warnings for a specific library <LIB> Regression testers should run with BOOST_WARNING_ENABLED defined. Developers of a library should run with BOOST_<LIB>_WARNING_ENABLED defined at least. Users could enable warnings at any level just by defining the appropriated macro. With this 2-level enabling policy, the preceding surrounding code becomes: #if !defined(BOOST_ENABLE_WARNINGS) && !defined(BOOST_LIB_ENABLE_WARNINGS) #if defined __GNUC__ #pragma GCC system_header #elif defined __SUNPRO_CC #pragma disable_warn #elif defined _MSC_VER #pragma warning(push, 1) #endif #endif and #if !defined(BOOST_ENABLE_WARNINGS) && !defined(BOOST_LIB_ENABLE_WARNINGS) #if defined __SUNPRO_CC #pragma enable_warn #elif defined _MSC_VER #pragma warning(pop) #endif #endif Due to the nature of the GCC solution, this does not work directly within the source (.cpp) file, only within a header (.hpp) file. So if we want to remove the warnings also from the .cpp files we need to move the code to a .hpp file. // a.cpp #include "warning_free_wrapper/a.hpp" Of course this policy don't mean that the developer should not take care of the warnings. Please, let me know if this policy could satisfy the needs of the Boost users and the developers. Best, _____________________ Vicente Juan Botet Escribá http://viboes.blogspot.com/

24 64

[itl] status?
by Jeff Flinn 03 Sep '10

03 Sep '10

What is the current status of the interval template library? Where can I get the latest version? Thanks, Jeff

4 3

nvcc config and mpl_assert
by Andrey Asadchev 03 Sep '10

03 Sep '10

recent boost distribution introduced nvcc as compiler which results in failed compilation when using mpl assert (and components of mpl which do so) here is the fix (it produces warnings, but allows for compile) --- config/compiler/nvcc.hpp 2010-09-02 18:43:46.000000000 -0500 +++ config/compiler/nvcc.hpp~ 2010-09-02 16:40:32.000000000 -0500 @@ -17,8 +17,8 @@ // Boost support macro for NVCC // NVCC Basically behaves like some flavor of MSVC6 + some specific quirks -//#define BOOST_NO_INCLASS_MEMBER_INITIALIZATION -//#define BOOST_MSVC6_MEMBER_TEMPLATES +#define BOOST_NO_INCLASS_MEMBER_INITIALIZATION +#define BOOST_MSVC6_MEMBER_TEMPLATES #define BOOST_HAS_UNISTD_H #define BOOST_HAS_STDINT_H #define BOOST_HAS_SIGACTION --- mpl/aux_/config/gcc.hpp 2010-09-02 18:49:14.000000000 -0500 +++ mpl/aux_/config/gcc.hpp~ 2010-09-02 19:03:39.000000000 -0500 @@ -14,7 +14,7 @@ // $Date: 2008-10-11 02:19:02 -0400 (Sat, 11 Oct 2008) $ // $Revision: 49267 $ -#if defined(__GNUC__) && !(defined(__EDG_VERSION__) || defined(__CUDACC__)) +#if defined(__GNUC__) && !defined(__EDG_VERSION__) # define BOOST_MPL_CFG_GCC ((__GNUC__ << 8) | __GNUC_MINOR__) #else # define BOOST_MPL_CFG_GCC 0 I think nvcc compiler must be differentiated whenever it uses Microsoft (Windows) or GCC(linux) compiler

2 1

[Locale] MS-LCID's table from MSDN site and Copyrights
by Artyom 03 Sep '10

03 Sep '10

Hello, I need a table for conversion of Windows LCIDs to ISO-639 Language and ISO-3199 Country codes and back. I need this for creation Win32 API based backend for Boost.Locale and ability to convert locale names like en_US to LCID 0x0409. Such table can be found here (link to PDF of this page): <http://msdn.microsoft.com/en-us/library/cc233965.aspx> It contains all I need. Now I want to insert such table to the cpp file and include it to the Boost.Locale library. I've read the Copyright notice on this page but I don't clearly understand: - Can I do this? It seems that this notice allow to copy the data but not sure. - Can I release a file that includes such table under Boost License? I need some advice from people who had already deal with such documents or stuff like this or know to read "lowers language" a little bit better and point me to specific line that would make it clear for me. Thank you Artyom P.S.: I can create a workaround based on iterating over all installed LCID's in runtime and querying their ISO-639 and ISO-3199 codes using GetLocaleInfo first time I need to use such table, but integrating static table would be much simpler and faster solution.

3 3

Re: [boost] Thoughts for a GUI (Primitives) Library
by Ralf Globisch 02 Sep '10

02 Sep '10

>>> Giorgio Zoppi 09/01/10 2:17 PM >>> I don't know if there's enough space for this. There are a plenty of GUIs Framework, like Qt or wxWindows, which are more advanced. -- Quiero ser el rayo de sol que cada día te despierta para hacerte respirar y vivir en me. "Favola -Moda". I concur, it would be difficult to match QT for any cross platform GUI development. It is an extensive, mature framework available under the LGPL and in terms of boost there are workarounds to make boost and QT signals co-exist. I'm not so familiar with wxWindows, but both of these GUI libs have been under development for some time and it would be difficult to compete with them, which is what any new library would have to do. -- This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks Transtec Computers for their support.

14 19

Re: [boost] [msm] on_entry must be implemented for every initial events for every states in substatemachines.
by Christophe Henry 02 Sep '10

02 Sep '10

> Hi All > > In the following little example see attachment, > I have a problem that in the RunningStateMachine::State2 the on_entry > function must be implemented with event1 and with event3 as well > but from the logic point of view there is no possibility to call > on_entry in RunningStateMachine::State2 with event1. > > actually at runtime there is no call is happening to to the function : > void on_entry(event1 const&,FSM& ) {std::cout << "entering: > State2:Event1" << std::endl;} > but it must be defined and even implemented ( if no implementation > provided linker error occurs). > Is it a restriction/bug or I'm missing something ? > It is only happening with initial events for substatemachines ? > Or is there a kind of pattern to know what events can enter exit a > state in a top of the ones present in the transition tables ?. Hi, Well, we don't want to go into the implementation details (we really don't ;-) ) but to make it short, msm tries the entry event with every state to see which state is active at run-time. And this means that every state's entry and exit behavior must be able to process this event. Of course it'd be possible to know in advance that some states are wrong candidates but this requires some compile-time graph analysis. And I do plan to start working on this using the metagraph library which is in construction. But for the moment I don't have this tool in msm. And even when I do, there will be a compile-time cost. Back to the example, when you write: template <class FSM> void on_entry(event3 const&,FSM& ) {std::cout << "entering: State2:Event3" << std::endl;} You are hiding the default on_entry, which provides you with an empty implementation for all events. The solution is not incredibly beautiful but will save us some compile-time. We need to tell the compiler we have a version for event3 and one for all others: template <class Event,class FSM> typename boost::enable_if< typename boost::is_same<Event,event3>::type,void >::type // version for event3 on_entry(Event const&,FSM& ) {std::cout << "entering: State2:Event3" << std::endl;} template <class Event,class FSM> typename boost::disable_if< typename boost::is_same<Event,event3>::type,void >::type // version for events != event3 on_entry(Event const&,FSM& ) {std::cout << "entering: State2:Event1" << std::endl;} Now it compiles :) HTH, Christophe

1 0

[quickbook] QUICKBOOK_CYGWIN_1_5 undefined
by vicente.botet 02 Sep '10

02 Sep '10

Hi, I have moved to v1.44, and while I try to build quickbook on cygwin-1.5 I get the following error $ bjam ...patience... ...found 1304 targets... ...updating 5 targets... gcc.compile.c++ ../../../bin.v2/tools/quickbook/gcc-3.4.4/debug/link-static/deta il/input_path.o C:\cygwin\boost\v44\tools\quickbook\detail\input_path.cpp: In function `void qui ckbook::detail::validate(boost::any&, const std::vector<std::string, std::alloca tor<std::string> >&, quickbook::detail::input_path*, int)': C:\cygwin\boost\v44\tools\quickbook\detail\input_path.cpp:80: error: `cygwin_con v_path_t' undeclared (first use this function) C:\cygwin\boost\v44\tools\quickbook\detail\input_path.cpp:80: error: (Each undec lared identifier is reported only once for each function it appears in.) C:\cygwin\boost\v44\tools\quickbook\detail\input_path.cpp:80: error: expected `; ' before "flags" C:\cygwin\boost\v44\tools\quickbook\detail\input_path.cpp:87: error: `flags' und eclared (first use this function) C:\cygwin\boost\v44\tools\quickbook\detail\input_path.cpp:87: error: `cygwin_con v_path' undeclared (first use this function) "g++" -ftemplate-depth-300 -O0 -fno-inline -Wall -g -g0 -DBOOST_ALL_NO_LIB= 1 -DBOOST_SYSTEM_STATIC_LINK=1 -I"../../.." -c -o "C:\cygwin\boost\v44\bin.v2\t ools\quickbook\gcc-3.4.4\debug\link-static\detail\input_path.o" "C:\cygwin\boost \v44\tools\quickbook\detail\input_path.cpp" ...failed gcc.compile.c++ ../../../bin.v2/tools/quickbook/gcc-3.4.4/debug/link-s tatic/detail/input_path.o... ...skipped <p../../../bin.v2/tools/quickbook/gcc-3.4.4/debug/link-static>quickbo ok.exe for lack of <p../../../bin.v2/tools/quickbook/gcc-3.4.4/debug/link-static >detail/input_path.o... See on the code I see that there is a test on QUICKBOOK_CYGWIN_1_5 which is not defined in any file. When I define it everything works as before. Should the user define QUICKBOOK_CYGWIN_1_5 when working on cygwin-1.5 ? Best, _____________________ Vicente Juan Botet Escribá http://viboes.blogspot.com/

2 3