- Boost - lists.boost.org

[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

Arena/Linear allocators
by Olaf van der Spek 29 Mar '12

29 Mar '12

Hi, I'm looking for arena/linear allocators, for use with multi_index, unordered_map and others. Does Boost provide anything like this? There's Boost Pool, but it only provides a singleton pool allocator. -- Olaf

2 2

[contract] nothing special about nested classes
by lcaminiti 29 Mar '12

29 Mar '12

Hello all, In the _many_ Contract Programming references that I have read (including N1962): http://contractpp.svn.sourceforge.net/viewvc/contractpp/trunk/doc/html/cont… I didn't find anything special about contracts for nested classes. I think that is because nested classes are executed at run-time "orthogonally" with respect to their enclosing classes. In other words, nesting a class only nests it's name (and changes some visibility rules) but it does not effect the run-time execution of the class and therefore it does not affect the contracts checked for the nested class. For example, the execution of a nested class y should only check y's invariants and not also the invariants of its enclosing class x: #include <contract.hpp> #include <iostream> CONTRACT_CLASS( struct (x) // enclosing class ) { CONTRACT_CLASS_INVARIANT( std::cout << "x's invariant" << std::endl ) CONTRACT_CLASS( public struct (y) // nested class ) { CONTRACT_CLASS_INVARIANT( std::cout << "y's invariant" << std::endl ) CONTRACT_FUNCTION( public void (f) ( void ) ) {} }; }; int main ( void ) { x::y yy; yy.f(); // checks y's invariant but not x's invariant return 0; } In fact in this example an object of x is not even created. Of course, if y was to create or get an object of x and invoke x's member functions then x's contracts will be checked as usual. This makes sense to me but I thought to share it with the ML. Thanks. --Lorenzo -- View this message in context: http://boost.2283326.n4.nabble.com/boost-contract-nothing-special-about-nes… Sent from the Boost - Dev mailing list archive at Nabble.com.

1 0

Boost Optional
by Rafael Justo 29 Mar '12

29 Mar '12

Hello! This is my first post in this list. =) I was looking today at Boost Optional (great work!). And I was wondering how could I do something like the bellow code. -------------------------------- #include <boost/optional.hpp> class Test {}; boost::optional<Test> get() { return boost::optional<Test>(); } int main() { if (get() == true) { // OK } else if (get() == false) { // ERROR } return 0; } -------------------------------- But there's no "operator==" with bool in optional.hpp, so the above code don't compile (i have checked version 1.49). Is it possible to add the patch described bellow in optional.hpp to solve this problem? -------------------------------- --- boost_1_49_0/boost/optional/optional.hpp 2010-12-18 19:29:39.000000000 -0200 +++ boost_1_49_0_new/boost/optional/optional.hpp 2012-03-28 16:03:53.417578997 -0300 @@ -616,6 +616,11 @@ return *this ; } + bool operator== (const bool condition) + { + return ((*this && condition) || (!*this && !condition)); + } + void swap( optional & arg ) { // allow for Koenig lookup -------------------------------- Best regards, Rafael Justo

4 4