- Boost - lists.preview.boost.org

[CMake] what to do now?
by boost＠glenstark.net 16 Apr '16

16 Apr '16

Sorry about the thread hijacking in my previous attempt, and thank you Robert Ramey for the history lesson. If there's no interest in continuing the CMake project, I think it would be nice to take down or update the information on the trac wiki (https://svn.boost.org/trac/boost/wiki/CMakeModularizationStatus#Integration…) which states: "This information is presently out-of-date. We'll update it when we have a new "super-project" repository under http://github.com/boostorg/." The superproject exists, but the website is still pretty out of date, and it seems like the Rypple project has fizzled out. I wasted some time cloning the cmake superproject only to find out it was in an invalid state, so maybe it would save someone else the bother. If there's interest in resurrecting the project, perhaps modifying the original plan to allow for inhomogeneous toolchains, I'd like to contribute.

17 106

[Root Pointer] New Documentation
by Phil Bouchard 15 Apr '16

15 Apr '16

Greetings, - I beefed up the tutorial in the following documentation and now it covers everything I know about it: http://philippeb8.github.io/root_ptr/ - As some of you already know I added a performance comparison chart in the introduction: http://philippeb8.github.io/root_ptr/root_ptr/intro.html - I fixed the deadlinks - I added a cast operation helper in the root_ptr class: https://github.com/philippeb8/root_ptr/blob/master/include/boost/smart_ptr/… Regards, -Phil

14 51

[variant] address of a variant type from the address of its sub-object?
by Andrzej Krzemienski 15 Apr '16

15 Apr '16

Hi, Is there a portable way (guaranteed by the interface) to do the following? I have an object 'ob' of type Ob and know its address. I know it is an active sub-object of a variant type, where Ob is one of the sub-types. Is there a way to compute the address of the containing variant object? The problem I am solving is to how to access the whole variant object from inside a static visitor: ``` using VariantOb = boost::variant<Ob>; struct MyVisitor : boost::static_visitor<> { void operator()(Ob const& ob) const { // --> get the address of the variant object ? boost::addressof(ob) + what_offset; ?? } }; ``` Regards, &rzej

6 10

Invoking a library's build//stage ignores --stagedir?
by Peter Dimov 14 Apr '16

14 Apr '16

Let's suppose that for some random reason I want to stage Boost.System into c:\stage with the current directory being outside the Boost root, which is at c:\projects\boost-git\boost: C:\Users\Peter Dimov>b2 -sBOOST_ROOT=c:\projects\boost-git\boost --stagedir=c:\stage c:/projects/boost-git/boost/libs/system/build//stage This doesn't work. Or rather, it works, but stages into C:\projects\boost-git\boost\libs\system\stage, ignoring the --stagedir. I have no idea why. I tried to debug with -d+7, and BOOST_STAGE_LOCATE is set correctly from --stagedir, but then Boost.System is staged to its local stage directory. Does anyone have an idea what's wrong here?

2 3

[multiprecision] Bug in double to cpp_bin_float conversion?
by Rob Conde 14 Apr '16

14 Apr '16

Consider the following code: #include <boost/multiprecision/cpp_bin_float.hpp> #include <iostream> int main() { typedef boost::multiprecision::cpp_bin_float_quad float128_t; float128_t f1(1e-9); float128_t f2("1e-9"); std::cout << std::setprecision(std::numeric_limits<float128_t>::max_digits10); std::cout << f1 << std::endl; std::cout << f2 << std::endl; return 0; } I'm getting as output: 1.000000000000000062281591457779856419e-09 9.999999999999999999999999999999999325e-10 The conversion of the double literal is not as expected. On wand box: http://melpon.org/wandbox/permlink/uSGNQZAEEytmb3ao Is this a bug? If not, what would be the correct way to get my expected behavior? Thanks, Rob Conde

3 3

[metaparse] how do I log a boost ticket?
by Aparna Kumta 13 Apr '16

13 Apr '16

I want to submit a Boost ticket at https://svn.boost.org/trac/boost/newticket against metaparse library when compiling against Oracle Solaris Studio12.5. However, I do not see 'metaparse' under the 'Component' tab. Should I be logging a bug elsewhere? I have gone ahead and submitted a PR. https://github.com/boostorg/metaparse/pull/6. Thanks, Aparna

2 4

Serialize a an image with Boost & GIL
by Visual Designer - Digital Team 13 Apr '16

13 Apr '16

Hi, I'm currently using boost serialization in order to save/load my data structure. The problem is that it contains some images and even with the ZIP compression the files are really big (4x bigger than the jpeg). So, I'm looking for a way to compress a RGB/A image (HDR or not) (without file operation) in memory. If possible without using any image compression library, we already use OpenImageIO but it is not possible for now ! Any idea ? I have found the GIL library, but can't find how to: 1) convert raw to GIL image 2) serialize the GIL image 1) deserialize the GIL image 2) convert the GIL to raw image Of course, the goal is to have a good compression without writing temporary file ! Thanks --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 3

[endian] Some suggestions
by Tatsuyuki Ishi 13 Apr '16

13 Apr '16

Mr. Beman, Here are some suggestions for the endian library. 1. Bring back float: make a proper reason for abandon You told about NaN: but it shouldn't apply since you store it in char buffer. Provide a proper reason: float is still needed since this is the only library that wraps details (platform endianness detection+compiler builtin optimizations). Float points are indispensable in data formats. I have to do a reinterpret_cast now as a workaround. 2. Remove n_bits(endian buffers): completely useless This just look like an alternative to sizeof, and always /8'd when used. What's the meaning of that? 3. Minor API suggestions Move operator type to endian_buffer: it's not related to arithmetic but just used because it can act like an integer. Non-const data(): I'm tired to do reinterpret_cast. Look at C++11 vector for a reference. Move stream operators to endian_arithmetic: I first thought that was for reading binary. That's basically unused.

9 19

Re: [boost] [endian] Some suggestions
by Tatsuyuki Ishi 13 Apr '16

13 Apr '16

> > 1. Bring back float: make a proper reason for abandon > > You told about NaN: but it shouldn't apply since you store it in char > > buffer. > > > > The problem isn't when storing into the char buffer, but later on a > different machine or compiler when the char buffer has to be converted to a > float type. I know nothing other than float format differences, and my target platforms are using iec559. I think reinterpret_cast should work: char data shouldn't be changed as long as stored as char. > > In testing, I even ran into a case were on the same machine and compiler > the float data failed to round-trip correctly if the program that created > the file was compiled with a different set of optimization options that the > program the read the file. > I will be happy if you provide some example. > > > > > 2. Remove n_bits(endian buffers): completely useless > > This just look like an alternative to sizeof, and always /8'd when used. > > What's the meaning of that? > > > > Please give a specific code example from the docs of what you think should > be changed. Or submit a pull request. > Since this is breaking API, I'd like you to make the decision to change it or not. For detail, this is the endian_buffer definition: template <order Order, class T, std::size_t n_bits, align A = align::no> class endian_buffer; n_bits looks quite useless here. It's basically sizeof*8. > > > > > 3. Minor API suggestions > > Move operator type to endian_buffer: it's not related to arithmetic but > > just used because it can act like an integer. > > > > Again, what code is it you think should be changed? Operator value_type()? > Please submit a pull request. > Exactly: operator value_type(). This will provide much more convenience. An example: when you specify the size for the array: endian_buffer size; dynarray d(size.value()); vs dynarray d(size); > > > Non-const data(): I'm tired to do reinterpret_cast. Look at C++11 vector > > for a reference. > > > > What is the motivation? What are the safety implications? What are the > alternatives? The C++11 (and also C++17) addition of non-cost data() > members to some standard library containers was supported by motivation and > safety analysis. > Seems endian_buffer is targeted for using in structs. Then is there any problem to provide a wrap of reinterpret_cast? At least, it should be safe by design. > > > Move stream operators to endian_arithmetic: I first thought that was for > > reading binary. That's basically unused. > > > > I must be missing something. Why wouldn't stream operators apply to endian > buffers? A code example might help. > Quite confusing. I first thought that was binary r/w operators that reads/writes the stream and store the value. The problem is that, there's no method provided for reading from binary, so this is also a reason for the previous data() suggestion.

2 1

[iostreams] Maintainer not working
by Tatsuyuki Ishi 13 Apr '16

13 Apr '16

Seems nobody is doing code review for iostreams since February. Basically I want a PR being merged: https://github.com/boostorg/iostreams/pull/25 This patch and some others looks good to me. It fixes a quite annoying warning. Can anybody with permission merge it?

1 0