- Boost-users - lists.boost.org

Re: [Boost-users] [boost] Stacktrace library starts review today 14th Dec
by Antony Polukhin 17 Dec '16

17 Dec '16

2016-12-17 20:51 GMT+03:00 Andrey Semashev <andrey.semashev(a)gmail.com>: <...> > That said, I'd like to thank Antony for the submission and encourage > him to continue his work on the library. The library does try to fill > an important gap. Thank you for the review! I'd like to discuss a proposed changes. Thing that I'm worried about: * replacing class `stacktrace` with vector<void*> will definitely break the most common use case std::cout << get_stacktrace(); as it's not a good idea to overload ostream operator for vector of void pointers * addr2line and forking is not nice. Is linking with a GPL licensed code an acceptable alternative? * removing `basic_stacktrace` will definitely remove all the possibilities for optimization of caching COM/parsed DWARF. This is a quick win that later may turn into big troubles. -- Best regards, Antony Polukhin

1 0

Trouble with std::forward and fusion vector using clang 3.4 and older library - is there a workaround?
by Stan Blakey 16 Dec '16

16 Dec '16

I am trying to compile using clang 3.4 and -std=c++11. With the -std=c++11 it compiles and runs without any issue. With -std=c++11 I get boost_1_60_0\boost/fusion/container/vector/vector.hpp:126:20: error: no template named 'forward' in namespace 'std'; did you mean 'advance_detail::forward'? return std::forward<result>(*advance_c<N>(begin(seq))); and many similar errors. I have tried all the boost BOOST_NO_CXX11_HDR_ macros but not found one that resolves this issue. I don't have any choice about compiler version or library version due to other constraints. Any suggestions appreciated, Stan *#include* <boost/fusion/tuple.hpp> *#include* <boost/fusion/algorithm.hpp> *#include* <string> *#include <iostream>* *using* *namespace* boost::fusion; *struct* print { *template* <*typename* *T*> *void* *operator()*(*const* *T* &t) *const* { std::cout << std::boolalpha << t << '\n'; } }; *int* *main*() { *typedef* tuple<*int*, std::string, *bool*, *double*> tuple_type; tuple_type t(10,"Boost", *true*, 3.14); for_each(t, print()); }

2 4

Boost 1.63.0 Release Candidate 1
by Marshall Clow 15 Dec '16

15 Dec '16

The release candidates for the 1.63.0 release are now available at: https://sourceforge.net/projects/boost/files/boost/1.63.0/ The SHA256 checksums are as follows: 010699561c6011e6d97dc453d55bc5e54cdc192622434eff7b8ac559efac846c boost_1_63_0_rc1.7z d8ebf8d90b2f823f04119445ac339d704395d655907333ec0fab863040119d24 boost_1_63_0_rc1.tar.bz2 dabe29b8a60369ae7c15c20681a32717f3c37d97e5dc6d39c5b2fd0494b8e995 boost_1_63_0_rc1.tar.gz 1683942022fd63c205c48fb2155af6094c67ef67aa13ffb3e1db78fecf817efe boost_1_63_0_rc1.zip As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The release managers

7 12

Stacktrace library starts review today 14th Dec
by Niall Douglas 15 Dec '16

15 Dec '16

The formal review of the Stacktrace library by Antony Polukhin starts today 14th Dec and will conclude before Christmas. I appreciate we are likely a bit tired out from the many library reviews recently and of course it's Christmas, but given the lack of a portable way to work with stack backtraces, which you inevitably need to do eventually in any non-toy production application, Stacktrace needs your review! Stacktrace is an optionally header-only library providing four implementation backends, libunwind (POSIX only), windbg (Windows only), backtrace (from the C library on most POSIX implementations) and a null backend. At its very simplest it lets you capture the stack backtrace for the calling thread and to print it to a std::ostream& of your choice. The basic_stacktrace<> class quacks like a STL container of frame object instances. The rest of the API pretty much follows STL design principles for the most part. Use is therefore unsurprising. You can find the documentation at http://apolukhin.github.io/stacktrace/index.html and the github repo at https://github.com/apolukhin/stacktrace. Review guidelines ================= Reviews should be submitted to the developer list (boost(a)lists.boost.org) preferably with '[stacktrace]' in the subject. Or if you don't wish to for some reason or are not subscribed to the developer list you can send them privately to me at 's_sourceforge at nedprod dot com'. If so, please let me know whether or not you'd like your review to be forwarded to the list. For your review you may wish to consider the following questions: - What is your evaluation of the design? - What is your evaluation of the implementation? Most of my personal concerns with this library are with the implementation and I would hugely appreciate feedback from others with substantial experience of using stacktracing "in anger" in non-trivial use case scenarios. - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? And finally, every review should attempt to answer this question: - Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. Even if you do not wish to give a full review any technical comment regarding the library is welcome as part of the review period and will help me as the review manager decide whether the library should be accepted as a Boost library. Any questions about the use of the library are also welcome. Finally, thanks to Edward whose announcement of the Synapse library review I borrowed heavily from as I thought it very well structured. Hopefully the above is just as clear. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

3 3

SSDLC Compliance - Boost C++ Libraries
by GAN Kok Leong, Adrian 14 Dec '16

14 Dec '16

Hi, We have a cybersecurity requirement for all software. We would like to know whether Boost C++ Libraries is developed and comply with Secure Software Development Life Cycle (SSDLC)? Regards Adrian Gan [This e-mail is confidential and may be privileged. If you are not the intended recipient, please kindly notify us immediately and delete the message from your system; please do not copy or use it for any purpose, nor disclose its contents to any other person. Thank you.] ---ST Electronics Group---

2 1

question
by David Bergman 13 Dec '16

13 Dec '16

Is boost capable of parallel processing. That is do wrappers or interfaces exist to call existing parallel versions of functions to help the user/programmer?Thank you, David

2 1

question
by David Bergman 13 Dec '16

13 Dec '16

Does boost handle Bessel functions with imaginary or complex index?Thank you, David

1 0

[C++ Libraries] Is it develop according to SSDLC?
by GAN Kok Leong, Adrian 13 Dec '16

13 Dec '16

Hi, I would like to know whether Boost C++ Libraries version 1.36.0-11.17 is developed and comply with Secure Software Development Life Cycle (SSDLC)? Regards Adrian Gan [This e-mail is confidential and may be privileged. If you are not the intended recipient, please kindly notify us immediately and delete the message from your system; please do not copy or use it for any purpose, nor disclose its contents to any other person. Thank you.] ---ST Electronics Group---

1 0

Unexpected static libraries in Windows build
by Christian Ullrich 07 Dec '16

07 Dec '16

Hello, I have a question about compiling Boost (1.62.0) itself on Windows, with Visual Studio 2015. I want to build DLLs only, but after I run .\b2 link=shared runtime-link=shared [...] install , I have a number of static libraries (libboost_...-mt-1_62.lib) in the lib directory. Specifically: - system - chrono - timer - unit_test_framework - test_exec_monitor - exception The first four also exist as the DLLs I expected to get. From testing some previous Boost releases, it seems that the number of unexpected static libraries increases over time (1.58 only produces two, and more appear with the versions in between that and 1.62). Why are these static libraries built in a shared/shared configuration? Do I need to keep them, or are they some kind of temporary build artifact (used to build others, perhaps)? I have looked through the documentation, mailing list archive, bug tracker, etc., but could not find anything on the subject. If I have not looked hard enough, any pointers will be welcome. I even looked at b2's dependency graph (-d +12), and from that, it appears they are top-level dependencies, but I cannot figure out where _any_ top-level dependencies are defined, let alone these. Thanks for any hints, -- Christian

2 2

[boost.build] how to install boost for arduino ide
by uğur aykar 06 Dec '16

06 Dec '16

>Hello everyone; >I am trying to figure out how to use boost libraries for arduino (avr-gcc). I am so >new to the boost. >I especially want to use lorenz example and compile it with arduino ide. >it requires the odeint library inside the "Boost/numeric/odeint. " which i >downloaded from https://www.codeproject.com/articles/268589/odeint-v-solving-ordinary-diffe… >and dowloaded the whole boost library version boost_1_62_0. >but i couldn't understand how to install for arduino ide. >where should i start? I feel so lost here. Thank you all Ugur Aykar uguraykar(a)hotmail.com

1 0