April 2012 - Boost - lists.boost.org

[scope_exit] C++11 freely uses typename (on MSVC10?)
by lcaminiti 03 Apr '12

03 Apr '12

Hi all, Isn't it C++11 supposed to allow to use typename freely even outside type-dependent context? Does MSVC10 support this? For example, is the following supposed to compile on MSVC10? #include <boost/mpl/identity.hpp> int main() { typedef typename boost::mpl::identity<int>::type t; t i = 0; return i; } Note: Using typename freely will allow me to not introduce SCOPE_EXIT_ALL_TPL and still support this_ (not just this). Thanks. --Lorenzo -- View this message in context: http://boost.2283326.n4.nabble.com/boost-scope-exit-C-11-freely-uses-typena… Sent from the Boost - Dev mailing list archive at Nabble.com.

4 5

[git] Mercurial?
by Daryle Walker 02 Apr '12

02 Apr '12

Git has a competitor called Mercurial? If we're moving to a Distributed-VCS, should we go to Mercurial instead of Git? They're kind-of like CVS vs. Subversion, except I think they came up in parallel. (While Subversion was designed as an updated CVS.) I think Git was made up of a bunch of script hacks, while Mercurial was a regimented single program. I don't have a preference, but I want to make sure we consider the rival options. Daryle W.

48 236

[test] Use of namespace qualifier before floating point functions in boost/test/impl/execution_monitor.hpp
by Jeremiah Willcock 02 Apr '12

02 Apr '12

According to http://pubs.opengroup.org/onlinepubs/009604599/basedefs/fenv.h.html, operations such as feclearexcept can be defined as macros, and at least some versions of Glibc do that by default. The use of explicit :: qualifiers before calls to those in Boost.Test fails to compile. Is there a workaround for that (other than __NO_MATH_INLINES)? -- Jeremiah Willcock

1 1

[asio] ip::tcp::socket thread safety
by Gaetano Mendola 02 Apr '12

02 Apr '12

Hi all, reading the manual I see that ip::tcp::socket thread safety on shared object is not safe. In my application I'm using: ip::tcp::socket::async_connect boost::asio::async_read( ip::tcp::socket , ...) the application queue an async_read or an async_connect inside the receiving handler (in case of error it retry the connection). >From an external thread (to stop the reception) I perform a: ip::tcp::socket::shutdown ip::tcp::socket::close do I have realy to synchronize the async_connect/async_read with shutdown/close ? Using a mutex to protect those calls seems an overkill, may be shutdown and close can be called in concurrency with async_connect/async_read and the documentation is just conservative? Regards Gaetano Mendola

2 1

[quickbook] coloring code syntax
by lcaminiti 02 Apr '12

02 Apr '12

Hello all, Is there a way to tell QuickBook code fragments to color words that are not C++ keyword for example in blue or in other colors? For example, in `int i = 0;` "int" is colored in blue. I'd like that in `requires Copyable<T>` "requires" is colored in blue (or some other color that I can specify). Thanks a lot! --Lorenzo -- View this message in context: http://boost.2283326.n4.nabble.com/boost-quickbook-coloring-code-syntax-tp4… Sent from the Boost - Dev mailing list archive at Nabble.com.

3 2

[result_of] Test fails on clang trunk and gcc-4.7 due to changes in FDIS
by Michel Morin 01 Apr '12

01 Apr '12

In the code below, const int f(); decltype(f()) i = 0; `i` has type `int` (not `const int`) in C++11. This is because `f()` is a prvalue of a non-class type (i.e. `const int`) and so its cv qualifiers are ignored. C++0x drafts (before FDIS) had a special rule for function calls in decltype: if e is a function call or an invocation of an overloaded operator (parentheses around e are ignored), decltype(e) is the return type of the statically chosen function; but this was removed in FDIS. Clang-3.1 (which will be clang-3.1) and gcc-4.7 seem to have implemented this change, and this change breaks the test case (libs/utility/test/result_of_test.cpp) on those compilers in a C++11 mode. The following are the errors messages: [1] result_of_test.cpp:210:3: error: static assertion failed: (is_same<result_of<const result_of_member_function_template(double)>::type, const double>::value) [2] result_of_test.cpp:211:3: error: static assertion failed: (is_same<result_of<volatile result_of_member_function_template(double)>::type, volatile double>::value) [3] result_of_test.cpp:212:3: error: static assertion failed: (is_same<result_of<const volatile result_of_member_function_template(double)>::type, const volatile double>::value) [4] result_of_test.cpp:239:3: error: static assertion failed: (is_same<result_of<const volatile no_result_type_or_result_of(void)>::type, const unsigned short>::value) [5] result_of_test.cpp:244:3: error: static assertion failed: (is_same<result_of<const volatile no_result_type_or_result_of_template<void>(void)>::type, const unsigned short>::value) Regards, Michel

3 10

Status of proposed boost.overload?
by niXman 01 Apr '12

01 Apr '12

Hello list! boost.overload: http://svn.boost.org/svn/boost/sandbox/overload/ The library will be accepted into the boost libraries ? -- Regards, niXman

5 11