- Boost - lists.boost.org

[Block Pointer][Container] Works - Take 2
by Phil Bouchard 06 Mar '16

06 Mar '16

Sorry for all the confusion but I was very confused myself. Now the block_ptr<> works in all cases with Linux x86: - I removed the usage of an allocator. Now there is no need for any allocator anymore. - I removed the usage of the strange pointer proxy optimization. Now the memory manager might take more memory but the class is clean and correctly abstracted. - I removed the usage of weak references. This is just too error-prone. But I need to tell whether an address is on the stack or on the heap. There is no portable way to do this except from marking the heap boundaries by overloading an allocator or write assembly code for each architecture / OS. I prefer the latter and I think this should eventually be part of the standards. Once again the working examples are here: https://github.com/philippeb8/block_ptr/blob/master/example/benchmark.cpp https://github.com/philippeb8/block_ptr/blob/master/example/block_ptr_test1… https://github.com/philippeb8/block_ptr/blob/master/example/block_ptr_test2… Regards, -Phil

3 6

merge to master?
by Robert Ramey 05 Mar '16

05 Mar '16

I've (finally!) got the latest version of the serialization library to pass all the tests on develop. I would like to merge develop to master. May I do this? Robert Ramey

2 4

[Block.Pointer][Container] Works!
by Phil Bouchard 05 Mar '16

05 Mar '16

Ok now everything works!! https://github.com/philippeb8/block_ptr/blob/master/example/block_ptr_test2… So now block_ptr<> is Boost.Container compliant! I still need to fix an issue but it's moving forward! Thanks, -Phil

3 7

[test] Boost.Test fails to build with gcc-4.6
by John Maddock 05 Mar '16

05 Mar '16

See http://www.boost.org/development/tests/develop/developer/output/igaztanaga-…

3 2

[Fit] pipable order of the arguments
by Vicente J. Botet Escriba 05 Mar '16

05 Mar '16

Hi, I would like to know what other think about the order of the pipe (See this issue https://github.com/pfultz2/Fit/issues/5) What would be the expected meaning of auto r1 =1 | pipable(f)(2); f(1,2) or f(2,1)? What would be the expected meaning of auto f2 = partial(f)(2); auto r1 =1 | pipable(f2); f(1,2) or f(2,1)? As the operator| has left-to-right associativity, we can not do auto x = 1 | 2 | pipable(f); We would need a way to pack the parameters auto x = forward_as_tuple(1, 2) | pipable(f); but this wouldn't compile as f has two parameters. or use parenthesis auto x = 1 | (2 | pipable(f)); and the result will be f(2, 1). Any ideas? Best, Vicente Vicente

1 1

[fusion] getting type of attribute_proxy for BOOST_FUSION_ADAPT_ADT
by Jens Weller 05 Mar '16

05 Mar '16

Hello, Code below, first what I'm trying to do is... assign a value to a adapted struct (BOOST_FUSION_ADAPT_ADT), which works fine if both are of the same type or convertible: template<int I, class Seq, class V> typename std::enable_if< std::is_convertible< typename fusion::result_of::at_c<Seq, I>::type, V>::value ,void>::type assign(Seq& s, V& v) { fusion::get<I>(s) = v; } Some of my input is string, and the struct member is bool, unsigned int etc. In this case I'd need to know the type to convert from string. boost::fusion::get returns the attribute_proxy for the adapted struct, so does at_c<>::type. template<int I, class Seq, class V> typename std::enable_if< !std::is_convertible< typename fusion::result_of::at_c<Seq, I>::type, V>::value /*&& !std::is_same<typename std::decay<V>::type,std::string>::value*/ ,void>::type assign(Seq& s, V& v) { std::stringstream ss; ss << v; ss >> fusion::get<I>(s); } Obviously this does not compile. Is there any trick to get to the type of the proxy? One idea I have is decltype(fusion::get<I>(s).get()), but not sure if I can get this to work in an enable_if... thanks, Jens Weller

3 5

[operators] permission to merge develop to master
by Daniel Frey 05 Mar '16

05 Mar '16

May I merge the ADL protection from develop to master for utility/operators?

2 3

[optional] Why was optional<T>::reset() deprecated?
by Nevin Liber 04 Mar '16

04 Mar '16

Does anyone know? We are considering adding it to std::optional this week. Thanks, -- Nevin ":-)" Liber <mailto:nevin@cplusplusguy.com <nevin(a)eviloverlord.com>> +1-847-691-1404

7 15

[type_traits] is_base_of<B, D> should work when B is incomplete
by Andrzej Krzemienski 04 Mar '16

04 Mar '16

Hi, I have filed the following ticket: https://svn.boost.org/trac/boost/ticket/12027 The Standard ([meta.rel]) requires that in std::is_base_of<B, D> D must be a complete type, but it does not require the same of B. This makes sense, because if we compare a complete type D and an incomplete type B, the former is surely not derived from the latter. In contrast, boost::is_base_of imposes an additional constraint that B must also be complete. Could this restriction be lifted? Regards, &rzej

8 14

[range] merge to master?
by Jürgen Hunold 04 Mar '16

04 Mar '16

Hi Neil, could you please merge Boost.Range to master? There are some merged PRs fixing bugs in develop which I'd like to see in 1.61.0 Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! * voice: ++49 4257 300 ! Fährstraße 1 * fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen * jhunold(a)gmx.eu ! Germany

1 0