May 2012 - Boost - lists.boost.org

[config] New NO_COPYABLE, DELETE_COPY_CTOR and DELETE_COPY_ASSIGN macros
by Vicente J. Botet Escriba 11 May '12

11 May '12

Hi, I'm using the following BOOST_NO_COPYABLE, BOOST_DELETE_COPY_CTOR, BOOST_DELETE_COPY_ASSIGN and macros in Boost.Thread (see http://svn.boost.org/svn/boost/trunk/boost/thread/detail/delete.hpp) I guess some of you have their own similar macros. For uniformity purposes, couldn't them be added to Boost.Config/ Boost Helper Macros <cid:part1.09000208.02050709@wanadoo.fr> if I provide a patch with doc and tests? Best, Vicente [section:delete `=delete` emulation] C++11 allows to delete some implicitly generated functions as constructors and assignment using '= delete' as in public: CLASS(CLASS const&) = delete; CLASS& operator=(CLASS const&) = delete; On compilers not supporting this feature, we can relays on a partial simulation, by declaring the function as private without definition. private: CLASS(CLASS &); CLASS& operator=(CLASS&); The emulation is good but partial as the private functions are still visible. To have the best the user should write public: #ifndef BOOST_NO_DELETED_FUNCTIONS CLASS(CLASS const&) = delete; CLASS& operator=(CLASS const&) = delete; #else // BOOST_NO_DELETED_FUNCTIONS private: CLASS(CLASS&); CLASS& operator=(CLASS&); public: #endif // BOOST_NO_DELETED_FUNCTIONS The following macros allows to take in account the features the compiler provides and have the same effect public: BOOST_DELETE_COPY_CTOR(CLASS) BOOST_DELETE_COPY_ASSIGN(CLASS) As these come together quite often when we want to make a non copyable class the user can use instead public: BOOST_NO_COPYABLE(CLASS) [section:delete_copy_ctor `BOOST_DELETE_COPY_CTOR(CLASS)`] This macro deletes the copy constructor when the compiler supports it or makes it private. It can be included on the public section only. [endsect] [section:delete_copy_assign `BOOST_DELETE_COPY_ASSIGN(CLASS)`] This macro deletes the copy assignment when the compiler supports it or makes it private. It can be included on the public section only. [endsect] [section:no_copyable `BOOST_NO_COPYABLE(CLASS)`] This macro makes a class as no copyable, disabling copy construction and assignment. It can be included on the public section only. [endsect] [endsect]

3 3

[build]
by Emil Dotchevski 11 May '12

11 May '12

Hello, I get the following Boost Build error and I have no idea what's wrong. Halp! C:\Users\Zajo\z\git\reverge\bjam\test c:/Users/Zajo/z/git/munch/boost-build/build\feature.jam:138: in feature.feature from module feature error: feature already defined: error: in feature declaration: error: feature "boost.locale.iconv" : "on" "off" : "optional" "propagated" c:\Users\Zajo\z\git\lib\boost_1_49_0\libs\locale\build\Jamfile.v2:19: in modules.load from module Jamfile</c:/Users/Zajo/z/git/lib/boost_1_49_0/libs/locale/build> c:/Users/Zajo/z/git/munch/boost-build/build\project.jam:314: in load-jamfile from module project c:/Users/Zajo/z/git/munch/boost-build/build\project.jam:62: in project.load from module project c:/Users/Zajo/z/git/munch/boost-build/build\project.jam:766: in project.use from module project c:/Users/Zajo/z/git/munch/boost-build/build\project.jam:89: in load-used-projects from module project c:/Users/Zajo/z/git/munch/boost-build/build\project.jam:73: in project.load from module project c:/Users/Zajo/z/git/munch/boost-build/build\project.jam:766: in project.use from module project c:/Users/Zajo/z/git/munch/boost-build/build\project.jam:89: in load-used-projects from module project c:/Users/Zajo/z/git/munch/boost-build/build\project.jam:73: in project.load from module project c:/Users/Zajo/z/git/munch/boost-build/build\project.jam:766: in project.use from module project c:/Users/Zajo/z/git/munch/boost-build/build\project.jam:89: in load-used-projects from module project c:/Users/Zajo/z/git/munch/boost-build/build\project.jam:73: in load from module project c:/Users/Zajo/z/git/munch/boost-build/build\project.jam:115: in load-parent from module project c:/Users/Zajo/z/git/munch/boost-build/build\project.jam:464: in initialize from module project c:/Users/Zajo/z/git/munch/boost-build/build\project.jam:309: in load-jamfile from module project c:/Users/Zajo/z/git/munch/boost-build/build\project.jam:62: in load from module project c:/Users/Zajo/z/git/munch/boost-build/build\project.jam:115: in load-parent from module project c:/Users/Zajo/z/git/munch/boost-build/build\project.jam:464: in initialize from module project c:/Users/Zajo/z/git/munch/boost-build/build\project.jam:309: in load-jamfile from module project c:/Users/Zajo/z/git/munch/boost-build/build\project.jam:62: in load from module project c:/Users/Zajo/z/git/munch/boost-build/build\project.jam:168: in project.find from module project c:/Users/Zajo/z/git/munch/boost-build/build\targets.jam:369: in find-really from module object(project-target)@683 c:/Users/Zajo/z/git/munch/boost-build/build\targets.jam:435: in object(project-target)(a)683.find from module object(project-target)@683 c:/Users/Zajo/z/git/munch/boost-build/build\targets.jam:816: in resolve-reference from module targets c:/Users/Zajo/z/git/munch/boost-build/build\targets.jam:833: in targets.generate-from-reference from module targets c:/Users/Zajo/z/git/munch/boost-build/build\targets.jam:1217: in generate-dependencies from module object(typed-target)@1905 c:/Users/Zajo/z/git/munch/boost-build/build\targets.jam:1268: in object(typed-target)(a)1905.generate from module object(typed-target)@1905 c:/Users/Zajo/z/git/munch/boost-build/build\targets.jam:732: in generate-really from module object(main-target)@2599 c:/Users/Zajo/z/git/munch/boost-build/build\targets.jam:704: in object(main-target)(a)2599.generate from module object(main-target)@2599 c:/Users/Zajo/z/git/munch/boost-build\build-system.jam:736: in load from module build-system c:\Users\Zajo\z\git\munch\NT\..\..\munch\boost-build\kernel\modules.jam:283: in import from module modules c:\Users\Zajo\z\git\munch\NT\..\..\munch\boost-build\kernel\bootstrap.jam:142: in boost-build from module c:\Users\Zajo\z\git\munch\NT\..\..\munch\boost-build.jam:6: in module scope from module Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode

2 2

For Boost PP: IF_NONEMPTY(), IS_NONEMPTY
by Daniel Santos 11 May '12

11 May '12

I came up with some macros the other day trying to solve a kernel problem and I haven't seen them anywhere else and if I found one, I sure would have stolen it. :) I used this to have a single function-like macro service different numbers of parameters, essentially adding "optional parameter" support so I didn't have to have different version of the macro. IF_NONEMPTY(test, result) expands to result if test is non-empty, empty otherwise. IS_NONEMPTY(arg) expands to 0 if arg is empty, 0x1 if it isn't. OPT_OFFSETOF(type, member) isn't very useful in C++, but it is an example of how the above can be used. It expands to a compiler-time constant that is the offset of the member in the struct or union type, unless member isn't specified, in which case it's zero. #define __JUNK junk, #define _if_nonempty(arg1_or_junk, result) __if_nonempty(arg1_or_junk, result) #define __if_nonempty(__ignored, result, ...) result #define CONCAT_TOKEN(a, b) _concat_token(a, b) #define _concat_token(a, b) a ## b #define IF_NONEMPTY(test, result) _if_nonempty(__JUNK##test, result) #define IS_NONEMPTY(arg) CONCAT_TOKEN(0, IF_NONEMPTY(arg, x1)) #define OPT_OFFSETOF(type, m) ((size_t) &((*((type *)0)) IF_NONEMPTY(m,.)m))

3 3

[reference_wrapper] add operator()(Args...) to reference_wrapper
by Philipp Moeller 10 May '12

10 May '12

Given that Boost now has perfect forwarding emulation through Boost.Move and a better result_of, would it be possible to enable reference_wrapper to forward the function call operator? The current behavior is somewhat surprising and makes a few of the most promising applications of reference_wrapper (reference wrap polymorphic boost::function objects) impossible with code that is no prepared to work with reference_wrapper. It would also be more consistent with reference_wrapper of the stdlib. I can file a corresponding bug report and add a patch, if there is interest. Cheers, Philipp Moeller

2 5

[multi_array] Updated patches
by Bill Buklis 10 May '12

10 May '12

For the multi_array library, there is an updated version of the library in the trunk plus a few tickets that have proposed patches. These are updates for some fairly important issues. I'd absolutely love it if these patches could be incorporated into the next boost release, whenever that may be. I realize that the official maintainer, Garcia, is understandably very busy, so could one of the powers that be please review these patches for correctness and update the official libraries as needed? Here are the tickets that already have proposed fixes: ticket:4874 <https://svn.boost.org/trac/boost/ticket/4874> - multi_array compile errors using Visual C++ 2010 in debug mode ticket:6554 <https://svn.boost.org/trac/boost/ticket/6554> - Compiler error dereferencing multi_array value via an iterator ticket:6811 <https://svn.boost.org/trac/boost/ticket/6811> - Default argument of type multi_array fails under MSVC 2010 SP1 Thanks, -- Bill

1 0

[preprocessor] include speed question
by lcaminiti 10 May '12

10 May '12

Hello all, I have a general question about what's the best way to include files that results in faster compilation time. In my example, I have *a lot* of files that use different parts of Boost.Preprocessor. Each header includes the specific Boost.Preprocessor headers that it needs. As a results the same Boost.Preprocessor header and #included many times (50+?) even if the including has no effect after the first inclusion. Furthermore, at the end essentially all Boost.Preprocessor header get included. This way is more module in that each single file includes all the headers that it needs. But, does that slow down compilation? Would it be faster to just #include <boost/preprocessor.hpp> just once into a front-end header that then includes all my single header files? (Maybe with modern compilers and file-systems this makes no difference?) Thanks a lot. --Lorenzo -- View this message in context: http://boost.2283326.n4.nabble.com/boost-preprocessor-include-speed-questio… Sent from the Boost - Dev mailing list archive at Nabble.com.

3 2

Scoped enum emulation
by Anthony Williams 10 May '12

10 May '12

Hi, On trunk there are currently two scoped enum emulation headers. One is the one that Beman wrote, in boost/detail/scoped_enum_emulation.hpp and the other is the one that Vicente has developed for the new version of Boost.Thread, in boost/thread/detail/scoped_enum.hpp It seems to me that it is a shame to have two implementations of the same thing in boost. Since Vicente's version provides additional facilities, I would therefore like to merge Vicente's code into the boost/detail header. We could retain the simple macros from Beman's header as wrappers for the more complex macros that Vicente has written. What do you think? Anthony -- Author of C++ Concurrency in Action http://www.stdthread.co.uk/book/ just::thread C++11 thread library http://www.stdthread.co.uk Just Software Solutions Ltd http://www.justsoftwaresolutions.co.uk 15 Carrallack Mews, St Just, Cornwall, TR19 7UL, UK. Company No. 5478976

3 2

[mpl] cross product and gcc specific compiler error
by Josh Quigley 10 May '12

10 May '12

Hi, A question from the grossly uninformed: I grabbed an mpl cross product implementation (product_view) of this mailing list. It works fine in MSVC but fails in gcc: typedef boost::mpl::vector<float, double, long double> DecimalTypes; typedef boost::mpl::vector<int, unsigned int, long, unsigned long, long long, unsigned long long> IntegralTypes; typedef product_view<boost::mpl::vector<DecimalTypes, IntegralTypes> > EachDecimalWithEachIntegralT; BOOST_AUTO_TEST_CASE_TEMPLATE(MyTest, DecimalIntegralT, EachDecimalWithEachIntegralT) { { typename DecimalIntegralT::item1 r(1234567); // Fails on gcc: no type named ‘item0’ in ‘struct boost::mpl::v_item<long long unsigned int, boost::mpl::v_item<ext::decimal::decimal128, boost::mpl::vector0<mpl_::na>, 0>, 0> typename DecimalIntegralT::item0 d(r); BOOST_CHECK_EQUAL(static_cast<long long>(d), r); } } A complete listing is below. The thing that has me really stumped is the type exsits in MSVC, so I'm at a bit of loss of how to proceed debugging. // // LISTING // #include <boost/mpl/vector.hpp> #include <boost/mpl/if.hpp> #include <boost/mpl/at.hpp> #include <boost/mpl/copy.hpp> #include <boost/mpl/transform.hpp> #include <boost/type_traits/is_same.hpp> #include <boost/function.hpp> #include <boost/mpl/vector.hpp> #include <boost/mpl/list.hpp> #include <boost/mpl/joint_view.hpp> #include <boost/test/unit_test.hpp> namespace detail { using boost::mpl::at_c; using boost::mpl::at; using boost::mpl::vector3; using boost::mpl::true_; using boost::mpl::false_; using boost::mpl::if_; using boost::mpl::next; using boost::mpl::bool_; using boost::mpl::front_inserter; using boost::mpl::clear; using boost::mpl::forward_iterator_tag; using boost::mpl::reverse_copy; using boost::mpl::transform1; using boost::mpl::deref; using boost::mpl::_1; using boost::mpl::_2; using boost::mpl::int_; using boost::mpl::fold; using boost::mpl::or_; using boost::mpl::nested_begin_end_tag; template<typename S, typename O> struct state_with_overflow { typedef S state; typedef O overflow; }; template<typename I3S> struct i3s_increment_inserter { template<typename I3, typename O> struct i3_ { typedef I3 i3; typedef O overflow; }; template<typename I3> struct incr_ { typedef typename next< typename at_c< I3, 1 >::type >::type next_; typedef bool_< boost::is_same< next_, typename at_c<I3,2>::type >::value > overflow_; typedef i3_< vector3< typename at_c<I3,0>::type, typename if_< overflow_, typename at_c<I3,0>::type, next_ >::type, typename at_c<I3,2>::type >, overflow_ > type; }; typedef front_inserter< typename clear<I3S>::type > base_; typedef state_with_overflow< typename base_::state, true_ > state; struct operation { template<typename S, typename I3> struct apply { typedef typename if_< typename S::overflow, typename incr_<I3>::type, i3_<I3,false_> >::type next_; typedef state_with_overflow< typename base_::operation::template apply< typename S::state, typename next_::i3 >::type, typename next_::overflow > type; }; }; }; template< typename SWO > struct product_iterator { private: typedef typename SWO::state I3S; public: typedef forward_iterator_tag category; typedef typename transform1< I3S, deref< at< _1, int_<1> > > >::type type; typedef product_iterator< typename reverse_copy< I3S, i3s_increment_inserter<I3S> >::type > next; }; template<typename S> struct product_view { private: typedef typename transform1< S, vector3< boost::mpl::begin<_1>, boost::mpl::begin<_1>, boost::mpl::end<_1> > >::type begin_impl; typedef typename fold< S, false_, or_< _1, boost::is_same< boost::mpl::begin<_2>, boost::mpl::end<_2> > // empty<_2> refuses to compile on MSVC 7.1 > >::type empty_result; public: typedef nested_begin_end_tag tag; typedef product_iterator< state_with_overflow< begin_impl, empty_result > > begin; typedef product_iterator< state_with_overflow< begin_impl, true_ > > end; }; } using detail::product_view; // typedef boost::mpl::vector<decimal32, decimal64, decimal128> DecimalTypes; // Original typedef boost::mpl::vector<float, double, long double> DecimalTypes; // for demonstration typedef boost::mpl::vector<int, unsigned int, long, unsigned long, long long, unsigned long long> IntegralTypes; typedef product_view<boost::mpl::vector<DecimalTypes, IntegralTypes> > EachDecimalWithEachIntegralT; BOOST_AUTO_TEST_CASE_TEMPLATE(MyTest, DecimalIntegralT, EachDecimalWithEachIntegralT) { { typename DecimalIntegralT::item1 r(1234567); // Fails on gcc: no type named ‘item0’ in ‘struct boost::mpl::v_item<long long unsigned int, boost::mpl::v_item<ext::decimal::decimal128, boost::mpl::vector0<mpl_::na>, 0>, 0> typename DecimalIntegralT::item0 d(r); BOOST_CHECK_EQUAL(static_cast<long long>(d), r); } }

1 0

[coroutine]
by Christopher Kormanyos 10 May '12

10 May '12

Hello, I am checking out the fascinating work with Boost.Coroutine. Excellent! This is definitely paving the way for C++ threads. I have been looking for this kind of thing for quite some time now. I am mostly interested in adaptability, as I386 and the lot are mostly done. It's always the same game with the cooperative context switching. Time-after-time, you identify the clobbered registers after a cooperative yield, save them in a context structure and restore them after the yield. Then you deal with the stacks. OK, fine. But how can you approach the dream of generic context switching? So you know, here I am. I would want Boost.Context for numerous GCC targets: Atmel AVR, Renesas V850, Renesas RL78, Cortex-M3/4. And the list goes on, as I use numerous embedded processors. The compiler's calling convention is poorly documented at best. And various compiler vendors may or may not coordinate the calling convention among each other. Can the documentation of Boost.Coroutine aid in adaptation in any way? Or is this simply beyond the present scope of the proposed Boost.Coroutine? * Is there any documentation regarding the context switch? * Are you specifically targeting preemptive yields? * If so, is the compiler's calling convention taken into account? * Can the remarkable Boost.Coroutine be adapted to other CPUs? * How? * Is Coroutine meant to be compatible with std::this_thread::yield(), etc? * Can the user select the stack sizes? * How? Thank you. And keep up the great work! Best regards, Chris.

3 6

[coroutine] request for review manager
by Oliver Kowalke 10 May '12

10 May '12

Hi, I want to ask who wants to be the review manager for boost.coroutine? The documentation is updated and available at: http://ok73.ok.funpic.de/boost/libs/coroutine/doc/html/index.html best regards, Oliver

2 4

[serialization] portable_binary_archive using shared lib
by Renato Tegon Forti 09 May '12

09 May '12

Hi, I want use portable_binary_archive, but using shared link on Windows! Have any way? Thanks

1 0

[exception] patches for a few testing-related issues
by David Deakins 09 May '12

09 May '12

Hi Emil, I have opened two Trac tickets (6877 and 6878) related to what I believe is a bug in exception_ptr_test.cpp and also for a minor change to the testing jamfile that will allow some of the thread-dependent tests to run on platforms that do not have automatic thread-specific-storage cleanup implemented (WinCE falls in this category). Are you ok with me applying these patches? Thanks, -Dave

2 1

enable_if question
by John Maddock 08 May '12

08 May '12

Folks I'm having some difficulties understanding the subtleties of enable_if, consider: using namespace boost; template <unsigned B> struct dummy {}; template <unsigned B, class Integer> typename boost::enable_if<mpl::and_<is_signed<Integer>, mpl::bool_<(sizeof(Integer) <= sizeof(long))> > >::type bar(dummy<B>&, const Integer&) { } template <unsigned B, class Integer> typename boost::enable_if<mpl::and_<is_unsigned<Integer>, mpl::bool_<(sizeof(Integer) <= sizeof(long))> > >::type bar(dummy<B>&, const Integer&) { } Then calling: dummy<2> d; bar(d, 2); Leads to an ambiguity between the two overloads (both gcc and VC++10), how can that be? However, changing the condition to: template <unsigned B, class Integer> typename boost::enable_if<mpl::and_<is_signed<Integer>, mpl::bool_<(B || !B) && (sizeof(Integer) <= sizeof(long))> > >::type bar(dummy<B>&, const Integer&) { } template <unsigned B, class Integer> typename boost::enable_if<mpl::and_<is_unsigned<Integer>, mpl::bool_<(B || !B) && (sizeof(Integer) <= sizeof(long))> > >::type bar(dummy<B>&, const Integer&) { } "fixes" things. But this fix isn't always possible. Thoughts? Thanks, John.

2 2

[preprocessor] Chaos: Auto macros incorrectly deduces the recursion state
by paul Fultz 08 May '12

08 May '12

Hello, I am not sure if this is the most appropriate place to post this, but I do know the author frequents this mailing list often. Well, when I run this code: #define FIXED(s, n, text) text #define TTP(s, n, id) \ template< \ CHAOS_PP_AUTO_ENUM( \ CHAOS_PP_INC(n), FIXED, class \ ) \ > class id ## n \ /**/ CHAOS_PP_AUTO_ENUM(3, TTP, T) // template<class> class T0, // template<class, class> class T1, // template<class, class, class> class T2 It expands to: template< CHAOS_IP_AUTO_ENUM_1( 1, FIXED, class ) > class T0 , template< CHAOS_IP_AUTO_ENUM_1( 2, FIXED, class ) > class T1 , template< CHAOS_IP_AUTO_ENUM_1( 3, FIXED, class ) > class T2 Showing CHAOS_IP_AUTO_ENUM_1 is incorrect, and its why it won't expand since its trying to be expanded recursively. It should be CHAOS_IP_AUTO_ENUM_2 instead. I'm not sure why it incorrectly deduces the recursion state. TTP is not a deferred expression. Any ideas? Thanks, Paul Fultz II

2 1

Aspen Meadows Resort suite available for up to 4 nights for C++Now Conference
by Pdruck 08 May '12

08 May '12

Hi. I reserved a suite at Aspen Meadows Resort for 4 nights, for the C++Now conference; Sunday night, May 13 – Wed night, May 16, leaving Thurs. May 17. But due to last minute pressing events in the office, I have to cancel my registration. Propose to switch my reservation to whomever might be attending. Win-win. I don’t lose a heft cancellation fee. You get a beautiful suite (having been there previously) and conveniently located to the conference at Physics Center. Regards. Phil

1 0

Iterator Range and operator==
by Olaf van der Spek 08 May '12

08 May '12

Hi, What do you expect this code to do? Is b true or false? And why? Is this expected behaviour? #include <boost/range/iterator_range.hpp> #include <string> int main() { std::string s = "Olaf"; boost::iterator_range<std::string::iterator> r(s); bool a = r == s; bool b = r == "Olaf"; assert(a); assert(b); return 0; } -- Olaf

9 17

[bind] variant arg list template functions could have a forward declaration as doc & coding suggeustion
by Huang Huan 08 May '12

08 May '12

Hi all, Before I do some change, no suggestion when I coding with Boost.Bind. This is a big disadvantage for learning & using. Variant arg list template functions as follow are there in so many boost code file. // template<class F, class A1, ... class An> // X foo(F f, A1 a1, ... An an); template<class F> X foo(F f) { ... } template<class F, class A1> X foo(F f, A1 a1) { ... } template<class F, class A1, class A2> X foo(F f, A1 a1, A2 a1) { ... } ... Some code like the comment, the forward declaration could be good doc & coding suggestion, such as following: template<class F /*, class A1, ... class An */> X foo(F f /*, A1 a1, ... An an */); OR template<class F, class A1, class A2 /*, ... */> X foo(F f, A1 a1, A2 a2, ... ); OR template<class F /*... */> // may no cxx11 X foo(F f , ... ); This may like BOOST_CONTAINERS_PERFECT_FORWARDING Becase of the template grammar, this forward declaration has no implementation. The code is ONLY for coding suggestion & doc. As an example [boost][bind] When I write the code boost::bind( _ ) I want the suggestions as follow ______________________________________________ | [1 of 3] _bi::bind_t<_bi::unspecified, F, L> bind(F f, ...) | |_____________________________________________| A more difficulty is boost bind has a BOOST_BIND for redefine the name. my patch as follow: =================================================================== --- bind.hpp (revision 77278) +++ bind.hpp (working copy) @@ -1289,6 +1289,17 @@ #ifndef BOOST_BIND #define BOOST_BIND bind + +template<class R, class F, class L> + _bi::bind_t<R, F, L> + bind(F f, ...); +template<class R, class F, class L> + _bi::bind_t<R, F, L> + bind(boost::type<R>, F f, ...); +template<class F, class L> + _bi::bind_t<_bi::unspecified, F, L> + bind(F f, ...); + #endif // generic function objects

1 0

Boost Threads - x86 Platforms / 64 bits compilation in Managed/Unmanaged Code / Visual Studio 2010 / Windows SDK 7.1 /clr
by Guillaume Rembert 07 May '12

07 May '12

As I had lots of issues to include boost thread libraries in a windows 64 bits code generated under Visual Studio 2010, here are the different steps to follow in order to get it compiling and executing quickly (mix of lots of the different specific posts). I could not find an easy, up to date procedure for this. This has been tested with Boost 1_49_0 release, Visual Studio 2010, Windows SDK 7.1 and Microsoft .NET 4. - Download 64 bits libraries, as binaries: http://boost.teeks99.com/ + unzip in a dedicated folder (for the example C:\boost\lib64) - Download boost headers and source code: http://sourceforge.net/projects/boost/files/boost/1.49.0/ + unzip in a dedicate folder (for the example C:\boost) - Set the project not to use precompiled headers + compilation with /clr to mix managed and unmanaged code - Add the headers path to the project additional include directories (in the example C:\boost) - Add the compiled libraries path to the linker additional library directories (in the example C:\boost\lib64) - Add to your project the following lines (force dynamic linking): #define BOOST_ALL_DYN_LINK #define BOOST_THREAD_USE_DLL #define BOOST_LIB_DIAGNOSTIC #include <boost/thread.hpp> --> Just compile and execute, it should not give any problems. The first line (#define BOOST_ALL_DYN_LINK) solves the following error I had: An unhandled exception of type 'System.TypeInitializationException' occurred in Unknown Module. Additional information: The type initializer for '<Module>' threw an exception.

2 1

[generic] status?
by lcaminiti 06 May '12

06 May '12

Hello all, What's the status of Matt Calabrese's Boost.Generic library? I was looking at the similarities between Boost.Generic and Boost.Contract syntax, and I think the following syntax can be implemented to define concepts, concepts_maps, axioms, etc CONTRACT_CONCEPT( concept (Iterator) ( typename X ) extends( Semiregular<X> ) ( typename(MoveConstructible) reference, as typename X::reference , typename(MoveConstructible) postinc_result , requires HasDereference<postinc_result> , (reference) operator(*)(deref) ( X& ) , (reference) operator(*)(deref) ( X&& ) , (X&) operator(++)(preinc) ( X& ) , (postinc_result) operator(++)(postinc) ( X&, int ) ) ) More examples here (auto concepts, concept maps, axioms, etc): http://contractpp.svn.sourceforge.net/viewvc/contractpp/trunk/doc/html/cont… If there was real interest using this syntax to define concepts, either the syntax could replace the on of Boost.Generic or Boost.Contract could provide the syntax and then use Boost.Generic behind the scene to actually define the concepts (same as Boost.Contract now does for Boost.Parameter). What do you think? Thanks. --Lorenzo -- View this message in context: http://boost.2283326.n4.nabble.com/boost-generic-status-tp4611363.html Sent from the Boost - Dev mailing list archive at Nabble.com.

2 2

[concept] typenames vs. typedefs
by lcaminiti 06 May '12

06 May '12

Hello all, I have questions about concepts (it's related to Boost.ConceptCheckign and Boost.Generic, but it's really just about the concept syntax that was proposed and never adopted for C++11). What's the difference between typename new_type = old_type and typedef old_type new_type? Why are they both allowed? For example, what's the difference between this: auto concept HasFind < typename T > { typename key_type = typename T::key_type; // use typename typename mapped_type; std::pair<key_type, mapped_type> find ( T const&, key_type const& ); } And this: auto concept HasFind < typename T > { typedef typename T::key_type key_type; // use typedef typename mapped_type; std::pair<key_type, mapped_type> find ( T const&, key_type const& ); } Thanks a lot. --Lorenzo -- View this message in context: http://boost.2283326.n4.nabble.com/boost-concept-typenames-vs-typedefs-tp46… Sent from the Boost - Dev mailing list archive at Nabble.com.

2 2

question about C++11 guidelines
by Eric Niebler 06 May '12

06 May '12

Say I'm rewriting an existing Boost library and targeting C++11 users. I plan to ship C++03 and C++11 versions of my library side-by-side, so back-compat isn't an issue for the new code. Is there a reason to prefer using Boost's versions of utilities like enable_if, type traits, integral constant wrappers (e.g. mpl::int_), tuples, etc., over the now-standard ones? I'm leaning toward using std:: where I can, and falling back on Boost's versions only when there is a compelling reason. -- Eric Niebler BoostPro Computing http://www.boostpro.com

16 30

Latest version and status of lockfree
by Julien Nitard 06 May '12

06 May '12

Hi All, Where can I find the latest version of boost.lockfree ? There's nothing in the sandbox or the vault (it seems). The latest commit on Tim's public git repo was done more than 6 month ago. Now that atomic has been accepted, are there any roadblocks to have boost.lockfree released ? Many thanks, Julien

4 9

trac spam (was: [Boost C++ Libraries] #6866: affiliate revolution)
by Eric Niebler 06 May '12

06 May '12

Who maintains trac these days? Can we get this spammy ticket deleted? Thanks, Eric -------- Original Message -------- Subject: [Boost C++ Libraries] #6866: affiliate revolution Date: Fri, 04 May 2012 20:08:29 -0000 From: Boost C++ Libraries <noreply(a)lists.boost.org> CC: boost-bugs(a)lists.boost.org #6866: affiliate revolution ----------------------------------+----------------------------------------- Reporter: anonymous | Owner: eric_niebler Type: Tasks | Status: new Milestone: To Be Determined | Component: proto Version: Boost 1.37.0 | Severity: Cosmetic Keywords: affiliate revolution | ----------------------------------+----------------------------------------- [<link deleted> affiliate revolution] -- Ticket URL: <https://svn.boost.org/trac/boost/ticket/6866> Boost C++ Libraries <http://www.boost.org/> Boost provides free peer-reviewed portable C++ source libraries.

3 3

[polygon] Trunk write access
by Andrii Sydorchuk 05 May '12

05 May '12

I sent a message recently to the Boost owners list to get write access to the Boost trunk, but haven't got any response yet. I am going to merge lately discussed Voronoi library and some updates to the Boost.Polygon. Those are approved by the library owner: Simonson, Lucanus J. Sorry for the rush. Regards, Andrii

2 2

Red Hat Enterprise Linux Test Page
by Olaf van der Spek 05 May '12

05 May '12

Hi, This does not look right. ;) https://www.boost.org/ -- Olaf

3 2