- Boost - lists.boost.org

Re: [boost] C++ Builder 2009 and Boost compliance
by Sean Farrow 16 Sep '08

16 Sep '08

Hi: There appears to be an issue with the spirit library and c++ builder. How are boost libraries built, as I want to determine what specifically is causing these issues. I use both boost.spirit and boost.serialization. Cheers Sean. -----Original Message----- From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of siliconman Sent: 16 September 2008 01:24 To: boost(a)lists.boost.org Subject: Re: [boost] C++ Builder 2009 and Boost compliance In article <48CE15DC.6010301(a)tid.es>, joaquin(a)tid.es wrote: > It'd be nice if we could have a regression test runner for this > product. I'll be adding it to my test runs soon. -- -David _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost __________ Information from ESET NOD32 Antivirus, version of virus signature database 3444 (20080916) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 3445 (20080916) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 3445 (20080916) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com

1 0

[Config] Multiple versions of Boost
by Sohail Somani 16 Sep '08

16 Sep '08

Recently, I had the pleasure of integrating a statically linked library that used a version of Boost different from the one I was using. All relevant compiler flags matched. Only the Boost version was the problem. Fortunately, I was able to solve the problem by getting the provider of the statically linked library to rename the Boost namespace by passing in -Dboost=boost_133_1_provider to their compiler. This worked fine for them. Obviously part of this solution involved them rebuilding the part of boost that was important to them in the same manner, but we always build Boost ourselves don't we? Anyway, I thought it might be a good idea to do the same on the larger code base so I attempted to do the same. Failed miserably. The problem is that some of the Boost code contains some variant of: #if defined(SOME_CONDITION) # define HEADER <boost/some/header.hpp> #else # define HEADER <boost/some/other/header.hpp> #endif #include HEADER Reading 16.2/4, it seems that the behaviour in this case is not defined. Specifically, an implementation may or may not replace the boost text with boost_133_1_provider. This is true whether or not you have <boost/some/header.hpp> or "boost/some/header.hpp". So on one compiler, you may end up with: #include <boost_133_1_provider/some/header.hpp> And on another: #include <boost/some/header.hpp> My immediate problem solved, I made do. However, the problem still bugs me. There should be /some/ way to do this. So... What if Boost.Config did something like: #if !defined(BOOST) # define BOOST boost #endif And we replace all uses of the boost namespace with BOOST? Would such a patch against trunk be acceptable? What are the problems? I know it isn't aesthetically pleasing but it might have made this a bit easier. -- Sohail Somani http://uint32t.blogspot.com

8 25

Answers re BENUM library for automated enum streaming
by Tony D 16 Sep '08

16 Sep '08

Hi all, Markus: apologies for not including the full URL. The file is benum_v1.zip at http://www.boostpro.com/vault/ Full URL is hhttp://www.boostpro.com/vault/index.php?action=downloadfile&filename=benum… - note Google Chrome mistakes it for a query, but the vault CGI doesn't seem to cope with %3D/%26 encoding of = and &. Thorsten / Marcus: roughly comparing to smart enum proposal: - BENUM _automates_ conversions based on stringified source code, which (postulating an extra macro "BENUM" hard-coding your favourite selection of meta-data container and optional features) allows BENUM(X, A = 1, B, C = 22, D = B|N); to approximate enum X { A = 1, B, C = 22, D = B|N }; and needs no further code to be streamable etc (preprocessor macros allow run-time cross-referencing of stringified source code with array of actual values) - smart enums requires user-maintained "meta-data" - from the smart enum docs: bool init = (::EnumIO<Foo>::the() (Bar, "bar") (Baz, "baz")), true; - BENUM supports optional mark-up mixed in with the enumerations to capture use of bit masking, guiding conversion to/from pipe-separated identifiers - BENUM supports many optional "features" including bitwise operations, incrementing and arithmetic operations, while smart-enums supports arithmetic and increment - both provide iteration over enumerations - smart enums supports automated range checking, with handling via throw, wrap, modulo The benum.test.cpp file shows a very complex example usage highlighting the features. Sorry for not working in to it gently. Note that all that extra mark-up etc. is optional and not needed by simple enumerations without bit masking/ORing etc.. Regards, Tony

3 2

Old style casts and Boost style guidelines
by Jon Biggar 16 Sep '08

16 Sep '08

I wanted to get rid of all old-style casts in my application, so I turned on -Wold-style-cast in gcc and found a whole bunch of old-style casts in boost headers. It seems to me that the boost coding style guidelines ought to explicitly discourage old-style casts. Any one else have a point of view? I've attached a list of the old-style casts gcc found in the 1.36 headers. This list isn't exhaustive, since my app doesn't use all boost libraries. :) -- Jon Biggar jon(a)floorboard.com jon(a)biggar.org jonbiggar(a)gmail.com ../../../boost/asio/detail/posix_fd_set_adapter.hpp:41: warning: use of old-style cast ../../../boost/asio/detail/posix_fd_set_adapter.hpp:45: warning: use of old-style cast ../../../boost/asio/detail/posix_fd_set_adapter.hpp:53: warning: use of old-style cast ../../../boost/asio/detail/signal_init.hpp:41: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:117: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:163: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:423: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:469: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:470: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:471: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:558: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:560: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:581: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:583: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:772: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:78: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:81: warning: use of old-style cast ../../../boost/asio/detail/socket_ops.hpp:858: warning: use of old-style cast ../../../boost/asio/detail/socket_select_interrupter.hpp:61: warning: use of old-style cast ../../../boost/asio/detail/socket_select_interrupter.hpp:68: warning: use of old-style cast ../../../boost/asio/detail/socket_select_interrupter.hpp:90: warning: use of old-style cast ../../../boost/asio/ip/address_v4.hpp:153: warning: use of old-style cast ../../../boost/asio/ip/address_v4.hpp:159: warning: use of old-style cast ../../../boost/asio/ip/address_v4.hpp:165: warning: use of old-style cast ../../../boost/asio/ip/address_v4.hpp:171: warning: use of old-style cast ../../../boost/asio/ip/address_v4.hpp:213: warning: use of old-style cast ../../../boost/asio/ip/address_v4.hpp:219: warning: use of old-style cast ../../../boost/asio/ip/address_v4.hpp:225: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:189: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:207: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:215: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:222: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:229: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:236: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:243: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:250: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:257: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:264: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:271: warning: use of old-style cast ../../../boost/asio/ip/address_v6.hpp:278: warning: use of old-style cast ../../../boost/asio/ip/basic_endpoint.hpp:71: warning: use of old-style cast ../../../boost/asio/ip/basic_endpoint.hpp:99: warning: use of old-style cast ../../../boost/asio/ip/detail/socket_option.hpp:275: warning: use of old-style cast ../../../boost/asio/ip/detail/socket_option.hpp:284: warning: use of old-style cast ../../../boost/asio/ip/detail/socket_option.hpp:353: warning: use of old-style cast ../../../boost/asio/is_read_buffered.hpp:54: warning: use of old-style cast ../../../boost/asio/is_write_buffered.hpp:54: warning: use of old-style cast ../../../boost/concept_check.hpp:915: warning: use of old-style cast ../../../boost/concept_check.hpp:928: warning: use of old-style cast ../../../boost/concept/detail/general.hpp:29: warning: use of old-style cast ../../../boost/concept/detail/general.hpp:37: warning: use of old-style cast ../../../boost/concept/detail/has_constraints.hpp:40: warning: use of old-style cast ../../../boost/concept/usage.hpp:21: warning: use of old-style cast ../../../boost/detail/lcast_precision.hpp:176: warning: use of old-style cast ../../../boost/detail/lcast_precision.hpp:177: warning: use of old-style cast ../../../boost/detail/sp_convertible.hpp:48: warning: use of old-style cast ../../../boost/exception/enable_error_info.hpp:85: warning: use of old-style cast ../../../boost/functional/detail/hash_float.hpp:180: warning: use of old-style cast ../../../boost/functional/detail/hash_float.hpp:182: warning: use of old-style cast ../../../boost/functional/hash/hash.hpp:112: warning: use of old-style cast ../../../boost/functional/hash/hash.hpp:114: warning: use of old-style cast ../../../boost/functional/hash/hash.hpp:132: warning: use of old-style cast ../../../boost/functional/hash/hash.hpp:134: warning: use of old-style cast ../../../boost/function/function_base.hpp:300: warning: use of old-style cast ../../../boost/function/function_base.hpp:347: warning: use of old-style cast ../../../boost/function/function_base.hpp:434: warning: use of old-style cast ../../../boost/function/function_base.hpp:619: warning: use of old-style cast ../../../boost/function/function_template.hpp:342: warning: use of old-style cast ../../../boost/function/function_template.hpp:435: warning: use of old-style cast ../../../boost/iterator/detail/facade_iterator_category.hpp:145: warning: use of old-style cast ../../../boost/iterator/detail/facade_iterator_category.hpp:151: warning: use of old-style cast ../../../boost/iterator/detail/facade_iterator_category.hpp:152: warning: use of old-style cast ../../../boost/iterator/detail/facade_iterator_category.hpp:153: warning: use of old-style cast ../../../boost/iterator/detail/facade_iterator_category.hpp:155: warning: use of old-style cast ../../../boost/iterator/detail/facade_iterator_category.hpp:166: warning: use of old-style cast ../../../boost/lexical_cast.hpp:578: warning: use of old-style cast ../../../boost/lexical_cast.hpp:694: warning: use of old-style cast ../../../boost/lexical_cast.hpp:764: warning: use of old-style cast ../../../boost/mpl/aux_/preprocessed/gcc/arg.hpp:117: warning: use of old-style cast ../../../boost/mpl/aux_/preprocessed/gcc/arg.hpp:27: warning: use of old-style cast ../../../boost/mpl/aux_/preprocessed/gcc/arg.hpp:45: warning: use of old-style cast ../../../boost/mpl/aux_/preprocessed/gcc/arg.hpp:63: warning: use of old-style cast ../../../boost/mpl/aux_/preprocessed/gcc/arg.hpp:81: warning: use of old-style cast ../../../boost/mpl/aux_/preprocessed/gcc/arg.hpp:99: warning: use of old-style cast ../../../boost/none.hpp:23: warning: use of old-style cast ../../../boost/regex/v4/cpp_regex_traits.hpp:284: warning: use of old-style cast ../../../boost/regex/v4/cpp_regex_traits.hpp:294: warning: use of old-style cast ../../../boost/regex/v4/cpp_regex_traits.hpp:653: warning: use of old-style cast ../../../boost/regex/v4/cpp_regex_traits.hpp:663: warning: use of old-style cast ../../../boost/regex/v4/match_results.hpp:106: warning: use of old-style cast ../../../boost/regex/v4/match_results.hpp:115: warning: use of old-style cast ../../../boost/regex/v4/match_results.hpp:128: warning: use of old-style cast ../../../boost/regex/v4/match_results.hpp:369: warning: use of old-style cast ../../../boost/regex/v4/match_results.hpp:370: warning: use of old-style cast ../../../boost/regex/v4/match_results.hpp:94: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_common.hpp:787: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_common.hpp:831: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_common.hpp:866: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher.hpp:50: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher.hpp:54: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_non_recursive.hpp:432: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_non_recursive.hpp:433: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_non_recursive.hpp:476: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_non_recursive.hpp:477: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_non_recursive.hpp:665: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_non_recursive.hpp:671: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_non_recursive.hpp:733: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_non_recursive.hpp:739: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_non_recursive.hpp:802: warning: use of old-style cast ../../../boost/regex/v4/perl_matcher_non_recursive.hpp:808: warning: use of old-style cast ../../../boost/regex/v4/regex_split.hpp:124: warning: use of old-style cast ../../../boost/regex/v4/regex_token_iterator.hpp:112: warning: use of old-style cast ../../../boost/regex/v4/regex_token_iterator.hpp:141: warning: use of old-style cast ../../../boost/regex/v4/sub_match.hpp:69: warning: use of old-style cast ../../../boost/regex/v4/sub_match.hpp:75: warning: use of old-style cast ../../../boost/thread/locks.hpp:1259: warning: use of old-style cast ../../../boost/thread/locks.hpp:1293: warning: use of old-style cast ../../../boost/thread/locks.hpp:1299: warning: use of old-style cast ../../../boost/thread/locks.hpp:1305: warning: use of old-style cast ../../../boost/thread/locks.hpp:43: warning: use of old-style cast ../../../boost/thread/locks.hpp:59: warning: use of old-style cast ../../../boost/thread/locks.hpp:75: warning: use of old-style cast ../../../boost/thread/pthread/timespec.hpp:28: warning: use of old-style cast ../../../boost/thread/thread_time.hpp:34: warning: use of old-style cast ../../../boost/thread/xtime.hpp:83: warning: use of old-style cast

8 13

C++ Builder 2009 and Boost compliance
by joaquin＠tid.es 15 Sep '08

15 Sep '08

C++ Builder 2009 has been recently launched and there are some claims about its having much better Boost support than previous versions of the product (see for instance http://tinyurl.com/5r2yxu or http://tinyurl.com/6zjnvx ). Does anyone have first-hand experience of C++ Builder 2009 and can verify these claims? It'd be nice if we could have a regression test runner for this product. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

5 6

[review] FSM Library review result
by Martin Vuille 15 Sep '08

15 Sep '08

This is a summary of the comments received during the review of Andrey Semashev's Finite State Machines (FSM) library. Apologies for the delay in getting these out. DOCUMENTATION * Relocate ToC to make it stand out. * Several people used the Wikipedia article http://en.wikipedia.org/wiki/Finite_state_machine as a reference for FSM terminology and operation, and found discrepancies between Boost.FSM and that description. Perhaps Boost.FSM should explicitly describe its FSM metamodel, or refer to an existing metamodel (Wikipedia FSM or Harel or UML Statechart, for example). The latter was mentioned several times as being preferred since it is a standard. * If possible, use standard terminology. For example, "transition map" vs. "state transition table". Or define the non-standard terms. * Include a comprehensive rationale mapping the design choices to the design objectives. * Compare/contrast Boost.FSM with the FSM implementation as described in "C++ Template Metaprogramming". * Add an example of event deferral using boost::function. * Clarify support for multithreading vs. asynchronous FSM, as some were confused by existing text. * Clarify lifetime of objects. * Add implementation of example using transition map/STT. * Add more complex example(s). SCOPE/FEATURES These were features that were suggested or asked about. Some or all may not be suited for addition to the library. In that event, it may be useful to explicitly mention in the documentation that they are not supported, and why. * Support nested states. Return-to-history was cited as an example of a benefit of nested states over nested FSM. * In STT, support matching "any" from state. * Add syntactic sugar to support "synthetic" states (cf. http://lists.boost.org/Archives/boost/2008/08/140714.php) * Support event deferral. * Support data-dependent transitions (perhaps this is the same as the synthetic state suggestion above). * Improve modeling of the "transition" concept. Specifically, there was an issue with the fact that the action was associated with a state rather than a transition. INTERFACE * There was a lot of discussion comparing the amount of code required to implement an "ad hoc" FSM, vs. the amount of code required to implement the same FSM using Boost.FSM. * The "transition map" representation was deemed to contain too much syntactic noise and not sufficiently similar to a traditional STT, and it was suggested that it should include the transition action. * Some felt that the interface was too procedural rather than being declarative. IMPLEMENTATION * There was quite a bit of discussion of the Boost.FSM implementation vs. the C++TM implementation, but I don't believe there were any specific conclusions reached. * Handling of event is different depending on whether or not transition map is used (handled by "to" state vs. current state, respectively). This is also the case when an event is not found in the transition map. This could lead to errors. Thanks again to Andrey for his submission and to all the reviewers and other who made comments for their input. MV

2 1

[bind] mem_fn_eq_test test failure with VC9 in release builds
by Richard Webb 15 Sep '08

15 Sep '08

When running the Trunk regression tests using VC9SP1 and building in release mode, the bind/mem_fn_eq_test test fails. Results available @ http://tinyurl.com/6nfm9m. The same test passes when the tests are run in the default debug mode. Thanks, Richard Webb

2 1

[exception] Virtual destructor warnings (again)
by Chris Newbold 15 Sep '08

15 Sep '08

I'm running into another instance of virtual destructor warnings with Boost.Exception -- this one when building on Solaris using the Sun Studio 12 compiler. The problem is with the boost::exception_detail::exception_clone class template. It uses CRTP and is often instantiated with a type which has a virtual destructor which has been declared 'throw()'. This causes the compiler to complain that the exception specification for exception_clone's implicitly-generated destructor is too wide: "../../../3p_mirror/sol64/boost/include/boost-1_36/boost/exception/enable_current_exception.hpp", line 121: Warning, wlessrestrictedthrow: Function boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::bad_function_call>>::~exception_clone() can throw only the exceptions thrown by the function boost::exception_detail::error_info_injector<boost::bad_function_call>::~error_info_injector() it overrides. "../../../3p_mirror/sol64/boost/include/boost-1_36/boost/exception/enable_current_exception.hpp", line 130: Where, temwhilespec: While specializing "boost::exception_detail::exception_clone<boost::exception_detail::error_info_injector<boost::bad_function_call>>". "../../../3p_mirror/sol64/boost/include/boost-1_36/boost/exception/enable_current_exception.hpp", line 130: Where, teminstfrom: Instantiated from boost::function3<void, int&, const char**&, const char**>::operator()(int&, const char**&, const char**) const. "../../../3p_mirror/sol64/boost/include/boost-1_36/boost/signals/signal_template.hpp", line 119: Where, teminstfrom: Instantiated from boost::signal3<void, int&, const char**&, const char**, boost::last_value<void>, int, std::less<int>, boost::function<void(int&,const char**&,const char**)>>::operator()(int&, const char**&, const char**). The fix seems simple enough, and is compatible with other compilers: add an empty destructor declared 'throw()' to exception_clone. Here's the diff: ==== //3rdparty/tmw/boost/boost/exception/enable_current_exception.hpp#1 - /mathworks/devel/sandbox/cnewbold/3rdp/3p/sources/boost/boost/exception/enable_current_exception.hpp ==== @@ -96,6 +96,10 @@ *be1 = *be2; } + ~exception_clone() throw() + { + } + private: detail::atomic_count mutable count_; -Chris

2 2

[BENUM] Any interest in auto-generated enum-to/from-string functions, without longer/more-complex usage?
by Tony D 15 Sep '08

15 Sep '08

After two expressions of interest (Keith Burton / Lance Diduck Vol 2186 Issue 4), reviews by Andrew Marlow and a few months, I've finally got around to packaging BENUM and putting it in the vault. Further consideration/feedback/questions appreciated. Specifically, I think the optional features and mark-up require fuller consideration and perhaps maturation.... Tony

3 2

Re: [boost] [switch] Is there any interest in library switch extension?
by Kasra Nassiri(Math & ComSci) 15 Sep '08

15 Sep '08

I am not sure how it could be performed on O(1), however, the current algorithm in O(n). Current algorithm is something like: BOOST_SWITCH( "hello world" ) { #include BOOST_PP_UPDATE_COUNTER() BOOST_CASE("invalid case") std::cout << "Reached invalid case!" << std::endl; #include BOOST_PP_UPDATE_COUNTER() BOOST_CASE("another string") std::cout << "Reached invalid case!" << std::endl; #include BOOST_PP_UPDATE_COUNTER() BOOST_CASE( "hello world" ) std::cout << "Reached the correct code!" << std::endl; #include BOOST_PP_UPDATE_COUNTER() BOOST_CASE("hello world 1") std::cout << "Reached the correct code! (no breaks)" << std::endl; BOOST_BREAK; #include BOOST_PP_UPDATE_COUNTER() BOOST_CASE("hello world") std::cout << "Should throw exception! (duplicated value)" << std::endl; #include BOOST_PP_UPDATE_COUNTER() BOOST_CASE("another string 1") std::cout << "Reached invalid case! (broken)" << std::endl; #include BOOST_PP_UPDATE_COUNTER() BOOST_DEFAULT std::cout << "Reached default Hello!" << std::endl; } BOOST_SWITCH_END It works fine but it is O(n) and uses hash tables. I want to get rid of "#include BOOST_PP_UPDATE_COUNTER()" somehow, but at this time I can't. Even when you use BOOST_BREAK at early statements it is still O(n), since it checks for duplicated values. But using break would change to O(m) : m < n. The 'default' statement at the moment must be at the end of all other cases, however, it will be updated so it could be anywhere with in the switch. By the way where is this switch_utility? Any other suggestions?

1 0