- Boost - lists.boost.org

[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

[container][memory] Request to move allocator_arg_t and uses_allocator to a memory related file.
by Vicente J. Botet Escriba 31 Mar '12

31 Mar '12

Hi, I want to add Allocators to the packaged_task and promise class of Boost.Thread template <class Allocator> promise(allocator_arg_t, const Allocator& a); template <class F, class Allocator> explicit packaged_task(allocator_arg_t, const Allocator& a, F&& f); I see that Boost.Container has already defined in namespace boost::container and in file boost/container/scoped_allocator.hpp the following struct allocator_arg_t { }; constexpr allocator_arg_t allocator_arg = allocator_arg_t(); template <class T, class Alloc> struct uses_allocator; I would like to shared these to all the Boost libraries. I don't think it is a good idea to make Boost.Thread depend on Boost.Container just for this. Could these declarations be included in a specific file? These declaration are included in <memory> in the C++11. What would be the best library to contain these declarations? What about a new boost/memory.hpp file? What about moving them to the boost or boost::memory namespace? Best, Vicente

2 5

[offtopic] C++Now! Room Reservation at Aspen Meadows
by Hartmut Kaiser 31 Mar '12

31 Mar '12

Hey all, If somebody needs a room reservation at the Aspen Meadows for C++Now in May, please get in contact with me offline. I have to cancel my trip and would like to avoid the cancellation penalty for my booked room. Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu

1 0

[guideline] 31 character filenames?
by Eric Niebler 30 Mar '12

30 Mar '12

Our current guidelines[1] say filenames should not exceed 31 characters. This was recently brought to my attention by a bug[2] from someone who actually cares because he uses the ODS-2 filesystem on OpenVMS. On a lark, I hacked the inspect tool to check for too-long filenames and lo! found a bazillion. Most (but not all) violations are from doc files auto-generated by doxygen and docbook, but which nevertheless go out with the boost distribution and so should conform. (Right?) So, should we care? Considering that we have little control(?) over how doxygen and docbook generate their files? I have fixed the bug in question, but it feels like a token effort. Should we just drop support for niche filesystems like ODS-2, and close all future bugs "won't fix"? [1] http://www.boost.org/development/requirements.html [2] https://svn.boost.org/trac/boost/ticket/6196 -- Eric Niebler BoostPro Computing http://www.boostpro.com

10 14

[Assign][GIL] Boost Assign and GIL incompatibility in gcc 4.3.2
by Andrew Hundt 29 Mar '12

29 Mar '12

The following source code compiles under clang 3.1, but fails under gcc 4.3.2 with boost version 1.46. It doesn't look like there are updates to either library in the boost news list since then. #include <vector> #include <boost/assign/std/vector.hpp> // for 'operator+=()' #include <boost/gil/gil_all.hpp> int main(int argc, char** argv){ using namespace boost::assign; std::vector<int> values; values += 1, 2, 3, 4; typedef boost::gil::rgb8_pixel_t pt; std::vector<pt> pixValues; pixValues += pt(1,2,3),pt(2,3,4); } ------------------------------------- Compiler versions: FAILED: gcc (SUSE Linux) 4.3.2 [gcc-4_3-branch revision 141291] Copyright (C) 2008 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. SUCCEEDED: Apple clang version 3.1 (tags/Apple/clang-318.0.54) (based on LLVM 3.1svn) Target: x86_64-apple-darwin11.3.0 Thread model: posix Cheers! Andrew Hundt

3 3