June 2016 - Boost - lists.preview.boost.org

[boost.process] 0.6 Alpha
by Klemens Morgenstern 21 Jun '16

21 Jun '16

Hi all, the boost.process 0.6 library is now in alpha, that is: it has some (compiling) examples, a documentation and tests that pass on windows as well as on linux. It basically allows you to manage a process like this: pstream pipe; child c("some_prog", "--some-arg", env["PATH"]+="C:/stuff", std_in < "data.csv", std_out > pipe, std_err > null, start_dir="./bin"); std::string data; pipe >> data; c.wait(); cout << c.exit_code() << endl; You can find the documentation here: http://klemens-morgenstern.github.io/process/ Get the source code from here: https://github.com/klemens-morgenstern/boost-process If you want to use it on windows, you currently would need to clone my boost.winapi fork also: https://github.com/klemens-morgenstern/winapi As for the scope of the library, it is meant to implement a small, portable layer to allow platform-independent process management. Thereby it's functionality is (unless I missed something) basically what is possible on posix as well as on windows. There are some platform extension, but I would not recommend to use them. It is also possible (though not yet documented) to write extensions, and if they work on both platforms I will gladly add them. It is however not the goal of the library, to be the be-all and end-all of process management; in past disscussions, different ideas where brought up, like implementing a DSEL for that or only allowing asynchronous communication. This library will never be that, since it would be much more fitting to build this on-top of it. E.g. a DSEL could be written (e.g. boost.shell) using boost.process underneath, so the library could concentrate only on the DSEL. It doesn't depend on boost.iostreams anymore, though it still uses boost.asio, boost.fusion and boost.filesystem. As for the open issues: some error handling is still lacking (but that'd be something like being unable to duplicate a handle), which would be required for proper extension, which is also why it's not documented. Also there's still an open discussion about the naming of the class and functions (child, system, spawn), so that may change also. But I consider this simple enough for a easy refactoring. If anyone has naming ideas, please tell me. One Idea was 'subprocess' but 'process::subprocess' just looks too strange to me. I hope you try it out, and give me some feedbacks. Or write angry error reports, both helps. Thanks! Klemens

8 32

Checking interest in stacktrace library
by Antony Polukhin 21 Jun '16

21 Jun '16

Hi, I've got some prototype for getting stack traces: https://github.com/apolukhin/stacktrace It's design is based on the idea that class for stacktrace must be fully noexcept, without dynamic allocations in constructors and as simple as possible. Is there interest in it? What functionality would you like to have in it? -- Best regards, Antony Polukhin

9 10

Re: [boost] proposed new library "histogram"
by Bjorn Reese 20 Jun '16

20 Jun '16

On 05/05/2016 12:21 AM, Hans Dembinski wrote: > https://github.com/HDembinski/histogram I suggest that you use non-intrusive serialization and place that in separate headers, so there is no dependency on Boost.Serialization unless you need it.

2 4

Checking interest in clang-{format, tidy} configurations
by jerry.c.t＠web.de 19 Jun '16

19 Jun '16

Hi, is there an interest for common boost clang-format and clang-tidy (only the module readability-identifier-naming) configurations to inforce consistent layout and naming style? For clang-format there are predefined styles like llvm, google etc. I think about adding a new predefined style 'boost' to clang-format. But first i would start with a separate _clang-format file. For clang-tidy there are no predefined styles thus i would simply create a _clang-tidy file. Best regards, Jerry

2 1

Feature request: variant::view
by TONGARI J 19 Jun '16

19 Jun '16

Hi, Sometimes we need to view a value as a variant and we don't want to copy the value into a variant. It'd be great if there's a variant::view that works like a variant but holds a reference to the value instead. The constructor should allow any reference to the types as in the variant, and a constructor that takes a reference to the variant, e.g. template<class T1, class T2...> class variant<T1, T2...>::view { view(T1&); view(T2&); ... view(variant&); }; And we can use apply_visitor/get on a view as on a variant. Thoughts? Thanks.

2 2

Boost's List of improvements
by Зайцев Александр 19 Jun '16

19 Jun '16

Hello. I will prepared Boost's list of improvements. I can realize it. Maybe, some algorithms I only can't find in Boost. And i think, that if i will implement algorithms from this list, it's will be great. Improvement list for Boost.Algorithm Boost.Algorithm(String) 1) Manacker's Algorithm: finding all palindromes in string O(N). 2) Different algortihms based on suffix arrays and suffix trees: Boost.Algorithm(Numbers) 1) Checking for number's simplicity by BPSW test. O(logN). 2) Effective factorization algorithms: Po, Po-1, Bents algo, Po-Monte-Carlo, Ferms algo. 3) Longest increasing subsequence Boost. Container 1) Modifications of queue and stack for searching min/max element with O(1). Maybe, I forgot something. -- Best regards, Zaitsev Alexander

1 0

Book
by Robert Ramey 18 Jun '16

18 Jun '16

I've attached an epub version of my "book". You should be able to just click on it and have the apple book reader popup and then be able to read it. The apple book reader has some interesting features. a) the book looks pretty good considering I didn't have to put to much effort into the formatting etc. b) For our purposes the best part is that you can easily annotate the book! There are three icons in the upper left corner. One to display the table of contents and other one for "notes" You can highlight text and add a note to it then save the book !. This is perfect as far as I'm concerned. Please don't spend time "copy editing" it. The whole thing needs to be gone over with a fine tooth comb with the idea of making the text more readable and clear, that the examples are in sync with the text, probably more narrative etc. etc. I'm really mostly concerned that the concepts are readable and explained to the target reader. Since I discovered the notion of semiring I understand the my C++ type algebra fulfills all the requirements of a semiring. And there is a large list of theorms which apply to semirings. I don't intend to add too much to the section, at least for now. It is very interesting but but right not it doesn't yet have a practical application. I'm hoping that will change but for now I it's as far as I want to go with this. This section will also need some work as far at the math is concerned. There are some issues with the notion of an inverse of a type etc which are still not really finished. But for now I think I've got the concepts outlined. It generates a book 60 pages long.

4 4

Re: [boost] [Boost-users] Checking interest in stacktrace library
by Antony Polukhin 18 Jun '16

18 Jun '16

2016-06-18 17:49 GMT+03:00 Edward Diener <eldiener(a)tropicsoft.com>: > On 6/18/2016 6:34 AM, Antony Polukhin wrote: > >> Is there interest in it? >> What functionality would you like to have in it? >> > > Documentation is always helpful. > Yeep, that's currently missing :( If in short: namespace boost { namespace stacktrace { class stacktrace { public: BOOST_STATIC_CONSTEXPR std::size_t max_symbol_width = 256; typedef boost::array<char, max_symbol_width> frame_t; stacktrace() BOOST_NOEXCEPT; stacktrace(const stacktrace& bt) BOOST_NOEXCEPT; stacktrace& operator=(const stacktrace& bt) BOOST_NOEXCEPT; ~stacktrace() BOOST_NOEXCEPT; std::size_t size() const BOOST_NOEXCEPT; frame_t operator[](std::size_t frame) const BOOST_NOEXCEPT; }; template <class CharT, class TraitsT> std::basic_ostream<CharT, TraitsT>& operator<<(std::basic_ostream<CharT, TraitsT>& os, const stacktrace& bt); }} So you can construct stacktraces, copy them and output them to streams: std::cerr << stacktrace(); -- Best regards, Antony Polukhin

1 0

Library addition request
by Gerrit Daniels 18 Jun '16

18 Jun '16

Hello, I've written a library that implements automatic serialization of user defined types. You can find it here: https://github.com/gerritdaniels/ctrl. I was wondering if this is something that could be added to the boost library. Kind regards, Gerrit Daniels.

6 10

Stand-alone Boost.Python
by Stefan Seefeld 18 Jun '16

18 Jun '16

Hello, I have started working on a new SCons-based build infrastructure for Boost.Python that allows the Boost.Python code to be compiled stand-alone against a pre-installed Boost. I have checked in a first version to the develop branch, and have enabled Travis-CI to use that. While this works reasonably well, and provides a much simpler workflow for developers wanting to contribute to Boost.Python, it isn't (yet) entirely feature-complete. Notably, running this on Windows (using MSVC) produces errors. I'd appreciate any help with this, especially from Windows users who are more familiar with MSVC than I am (that shouldn't be hard, given I have next to no experience with using MSVC :-) ). Building Boost.Python is now very simple: * clone the repo via `git clone https://github.com/boostorg/python.git` and switch to the 'develop' branch * configure a build via `scons config --python=... --boost-prefix=...` * build and test via `scons test` Hopefully this will make it much simpler to contribute and test patches, so we can work down the list of accumulated PRs and issues. (For avoidance of doubt: for the immediate future I have no intentions to replacing the official bjam-based build system. But once the new one has proven to be stable enough, I expect to actually build stand-alone releases for Boost.Python.) Thanks, Stefan -- ...ich hab' noch einen Koffer in Berlin...

1 0

Using Boost with VS 14.0 update 3 RC and Clang 3.8.0 (from CodeBlocks IDE) compile fails in MS type_traits is_assignable
by Paul A. Bristow 15 Jun '16

15 Jun '16

I am trying to check a program that compiles on VS with 14.0 update 3 RC and on Codeblocks IDE GCC 5.3 compile OK, but CodeBlocks Clang 3.8.0 fails: C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\include\type_traits:524:45: error: '_To' does not refer to a value : integral_constant<bool, __is_assignable(_To, _From)> I:\modular-boost\boost\mpl\aux_\preprocessed\plain\or.hpp|58|error: pasting formed 'BOOST_PP_TUPLE_ELEM_O_3(', an invalid preprocessing token [-Winvalid-token-paste] and terminally many more. clang++.exe -Wall -std=c++14 -m64 -fexceptions -O4 -m64 -std=c++14 -fms-extensions -Wall -m64 -fms-compatibility-version=19.00 -II:\modular-boost -c J:\Cpp\hellos\fixed_point_constexpr\fixed_point_constexpr.cpp -o obj\Release\fixed_point_constexpr.o I see some discussion of similar problem on https://groups.google.com/forum/#!topic/boost-list/MvqaK4SDy_c and a possible apparent fix on https://github.com/boostorg/type_traits/pull/24 Any suggestions for working around this problem? Paul PS I may try to use a *nix platform for this. --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830

2 1

[density] new library
by Giuseppe Campana 14 Jun '16

14 Jun '16

Hi to all, I'm working to density, a C++11 header-only library for heterogeneous containers and lifo memory management. It is not complete, but it is very close (and usable already). Just to avoid confusion, the test project of density contains a sub-module called testity, that in a near future will become a separate library. I'm wondering if it may become a valid proposal for a new library. In any case, any kind of feedback is welcome. Source code at https://github.com/giucamp/density Documentation at http://peggysansonetti.it/tech/density/html/index.html Regards, Giuseppe Campana.

6 9

[property_tree] Quoting documentation
by alainm 13 Jun '16

13 Jun '16

Hi, I am using property_tree for a project, and I'd like to provide a description of the format. That text is exactly what I need: http://www.boost.org/doc/libs/1_61_0/doc/html/property_tree/parsers.html#pr… I am going to provide a link to the doc, but would need to insert the text into the documentation pdf too (some people actually still read paper). Is it possible and what kind of copyright text should I use ? Thanks Alain

2 1

Start to contribute to Boost.
by Зайцев Александр 11 Jun '16

11 Jun '16

Hello. I very want to start contribute to Boost library. I want to help this project. And... maybe for start i can try to fix some bugs. Can you give me some pieces of advice, what i can do at start? Thanks. -- С уважением, Зайцев Александр.

3 2

Pimpl Again?
by Vladimir Batov 10 Jun '16

10 Jun '16

Don't laugh but it is only fairly recently at work that I managed to move all our supported platforms to C++11. So, then, I started moving our code to C++11 (what a delight!) and stumbled upon my old pimpl which is used quite a bit around my workplace for all its good properties... :-) Now C++11-ed piml turned out to be very small and very basic. So basic it felt it did not have the right to exist. Still, it encapsulates and enforces the "proper" pimpl properties and behavior, reduces implementation minutia and offers a recognizable deployment pattern (helps other people reading the code). Over the years IMO the technique has been proven as legitimate and useful, a basic but important building block... rather than a curiosity item. Unfortunately, despite many articles and a few Sutter's GotWs about it there is nothing ready-to-go like std::unique_ptr. I feel that pimpl and its deployment pattern need to be codified, described, "standardized" and in our toolboxes to stop/avoid everyone re-inventing the pimpl and making the same mistakes. IMO Boost is best positioned for that. Do you think we might review what I've got and/or maybe collectively come up with something better... It's no MPL or Hana but as std::unique_ptr it's one of the first "little things" I personally reach out for in my everyday work. IMO having pimpl in Boost would save quite a few hours of frustration for many. Thoughts? No pressure. I am easy either way. :-) https://github.com/yet-another-user/pimpl Docs are freshened up but still somewhat out of date. Apologies.

15 84

[config] Changes needed for VC++ 2015 Update 3?
by Beman Dawes 09 Jun '16

09 Jun '16

The VS 2015 Update 3 release candidate has been announced. See https://blogs.msdn.microsoft.com/vcblog/2016/06/07/compiler-improvements-in… (The following is partially for Boost developers who care about msvc, and partially to remind myself of what may need to be done to support update 3. It will be several weeks before I can work on this, so if any of the other config maintainers want to step in, please do so.) Update 3 supports standards versioning switches similarly to gcc, clang, and other compilers. We probably want to update Boost.Config accordingly. See https://blogs.msdn.microsoft.com/vcblog/2016/06/07/standards-version-switch… Update 3 fixes lots of constexpr bugs, so we need to review whether or not BOOST_NO_CXX11_CONSTEXPR is still required. Note that in develop there is an undocumented config macro BOOST_MSVC_CXX11_CONSTEXPR that turns off BOOST_NO_CXX11_CONSTEXPR to facilitate testing. Update 3 fixes the expression SFINAE issues that were causing most of the Boost develop test failures. https://blogs.msdn.microsoft.com/vcblog/2016/06/07/expression-sfinae-improv… Quoting from that: There are still three failing tests in the Boost [develop] test suite when compiling with MSVC. Two test failures relate to using the noexcept operator in a template type argument. We currently parse it immediately, even in a dependent context. One test failure is a Boost library issue that we’ve reported to the [library's] maintainers. There are still known update 3 expression SFINAE issues (see "What remains to be done?" in the blog article) so do we continue to define BOOST_NO_SFINAE_EXPR? There is an undocumented BOOST_MSVC_SFINAE_EXPR macro in develop that turns off BOOST_NO_SFINAE_EXPR, so it is easy for developers to use msvc expression SFINAE if the want to. But our usual criteria for a _NO_ macro is not full compliance, but whether or not Boost code works with a feature. So using that criteria for update 3 we would remove BOOST_NO_SFINAE_EXPR. Opinions? --Beman <aside> We always urged Microsoft to test their releases against Boost. For update 3 expression SFINAE, they did exactly that. Thanks to Microsoft's Andrew Pardoe for coordinated the effort and to Xiang Fan for running the tests and tracking down the reason for each test failure. An undocumented Boost.Config macro BOOST_MSVC_SFINAE_EXPR to support their testing. The approach was to run tests for all libraries with the normal test setup, and then run again with BOOST_MSVC_SFINAE_EXPR defined. If the problem was with the Boost library, Xiang then reported it to me. I need to review a long series of email exchanges with him to make sure I alerted library maintainers to any Boost problems. </aside>

5 9

Boost Best Practice text download option fails.
by Fletcher, John P 08 Jun '16

08 Jun '16

This is a very interesting item to me. https://svn.boost.org/trac/boost/wiki/BestPracticeHandbook This has an option at the end to download as plain text. This fails on my browser (Firefox) with "Corrupted Content Error" which I have never seen before. Please sort this out someone. John

2 1

[variant] spirit broken
by Jürgen Hunold 08 Jun '16

08 Jun '16

Hi Antony, according to git bisect, your commit ----------- commit b3650685f941a0c35cadfd878a185f274e132788 Author: Antony Polukhin <antoshkka(a)gmail.com> Date: Sat May 28 01:29:52 2016 +0300 Variant constructors and assignment operators now do not participate in overload resolutions if variant can not hold the input type (trac 5871, trac 11602) ------------ broke Boost.Spirit. The test failures can be seen in the regression matrix. For example: http://www.boost.org/development/tests/develop/developer/output/Flast-FreeB… fails with ../boost/variant/variant.hpp:1152:7: note: while substituting deduced template arguments into function template 'operator=' [with T = boost::variant<boost::spirit::info::nil_, std::__1::basic_string<char>, boost::recursive_wrapper<boost::spirit::info>, boost::recursive_wrapper<std::__1::pair<boost::spirit::info, boost::spirit::info> >, boost::recursive_wrapper<std::__1::list<boost::spirit::info, std::__1::allocator<boost::spirit::info> > > >] class variant ^ ../boost/spirit/home/support/info.hpp:29:12: note: definition of 'boost::spirit::info' is not complete until the closing '}' struct info It seems that the commit somehow disabled support for recursive variant usage. To reproduce this, just run the Spirit regression test. 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

2 5

[Spirit] real_policies<> and 1.0#NAN
by Pete Bartlett 08 Jun '16

08 Jun '16

Hi, Boost.Spirit is not sure of itself when it comes to parsing representations of infs and nans such as “1.0#NAN”. The docs [1] for the default real_policies<T> for parsing numbers say: “[…] with the additional detection of NaN and Inf as mandated by the C99 Standard and proposed for inclusion into the C++0x Standard: nan, nan(...), inf and infinity (the matching is case-insensitive). This corresponds to the following grammar:” The first sentence suggests that 1.0#NAN etc will not be parsed. But the grammar itself then says: <quote> nan = -lit("1.0#") >> no_case["nan"] >> -('(' >> *(char_ - ')') >> ')') ; inf = no_case[lit("inf") >> -lit("inity")] ; </quote> suggesting that "#1.0NAN" is intended to parsed, but "#1.0INF" is not! Then the in-code docs [2] however suggest that both "1.0#NAN" and "1.0#INF" are intended to be parsed: <quote> // The second call allows to recognize representation formats starting // with a 1.0 (such as 1.0#NAN or 1.0#INF etc.). </quote> However, the actual code fails to parse either of these these. This is because in [3] the presence of the "0" causes frac_digits to be non-zero and so the "traits::is_equal_to_one(..)" condition is never tested. In the case "1.#NAN" (without a zero) frac_digits is zero so the condition is tested and we enter the traits::parse_nan code, but now the text parsed to this sub-parser is "#NAN" and the parser does not cater for the initial "#". Could the maintainers state which behaviour is intended...hopefully I may be able to supply a patch to docs/code/tests knowing that. Regards, Pete [1] http://www.boost.org/doc/libs/1_61_0/libs/spirit/doc/html/spirit/qi/referen… [2] <boost/spirit/home/qi/numeric/real_policies.hpp> [3]<boost/spirit/home/qi/numeric/detail/real_impl.hpp>

2 1

RFC : About forking a C++11 standard library and adapt it to C++98 compilers
by Vicente J. Botet Escriba 07 Jun '16

07 Jun '16

Hi, Some of us have to work yet with C++98 compiler at work (due to well know reasons) and this for a long time. This is a reality. I was wondering about forking a public domain C++11/14/17 standard library and adapt it to C++98 compilers. This library could be seen as another TR1, an extension of the C++03 standard library. Does this make any sens? Would this project be of interest for the Boost/C++ community? I have not a clear idea of the cost of doing this work, how it should be done, what would be the limitations, ... but I'm sure that this would be quite useful on the projects that are forced to use C++98 and an excellent bridge to those that will move from C++98 to C++11 compilers. There are some Boost libraries that could be used to reduce the limitations, as Boost.Config/Predef, Boost.Move, ...and others that could be used as inspiration on how to implement them using C++98. Anyway, if you find that this will be useful to you at your work we will need your participation. Would you be interested in working on it? as a Boost community project? outside Boost, as an independent project? Comments and suggestion welcome. Best, Vicente P.S. The same can be done for C++14 standard libraries and the future standard C++17 libraries P.S.S. The same can be done for C++14 libraries and the future C++17 libraries but this time adapting to C++11 compilers (this will be much easier but the concerned community will be quite different ).

5 7

Make libs/maintainers.txt a template file
by Daniel James 07 Jun '16

07 Jun '16

Hi, If you haven't noticed, on develop libs/libraries.htm is now a template which gets filled in as part of the documentation build. You can see the template and generated files at: https://github.com/boostorg/boost/blob/develop/libs/libraries.htm http://www.boost.org/doc/libs/develop/libs/libraries.htm This will be merged to master pretty soon. The only obstacle is updating the website automatically from the latest build, which should be happening very soon. The file libs/maintainers.txt is also automatically updated, but that's done in the repo itself, so that you have the full copy in you normal checkout. But I'm finding that people don't realise this, and we've had a few pull requests to update it manually. So instead, I think it might be a good idea to convert it to a template as well. This means you won't have a local copy, but will still be able to see a reasonably up to date copy online at: http://www.boost.org/doc/libs/develop/libs/maintainers.txt Any objections? I'm think of using similar templates for some other files, such as the root index.html (for the version number and new libraries). thanks, Daniel

2 2

Cxx dual library
by Edward Diener 06 Jun '16

06 Jun '16

I have finished all the main work on the Cxx dual library at https://github.com/eldiener/cxx_dual. The library is also in the Boost Library Incubator at http://rrsd.com/blincubator.com/bi_library/cxx_dual-2/?gform_post_id=1597. The Cxx dual library, or CXXD for short, is a C++ macro header-only library which chooses between using a Boost library or its C++ standard equivalent library for a number of different C++ implementations, while using the same code to program either choice. An 'implementation' is a Boost library which has a C++ standard library equivalent whose public interfaces are nearly the same in both cases. An 'implementation' is called a 'dual library' in this documentation, or 'CXXD-mod' for short. The library does this by defining object-like macros for including the appropriate header file and namespace or using either the Boost library version or the C++ standard library version of a particular dual library. CXXD currently supports twenty eight different dual libraries, where the Boost version and the C++ standard version is nearly interchangeable in some respects. CXXD also provides a macro-based solution for distinguishing between the Boost version and the C++ standard version of a dual library so that specific code for a particular dual library choice may be written in those cases where the public interfaces diverge. The library came out of my initial PR to add such a feature to Boost.Config, and then I decided to create a separate library and expand on the functionality. The gist of the library is to write a single set of code for a particular implementation and have it work whether or not that code targets a Boost implementation or its C++ standard equivalent. The default algorithm will choose the C++ standard implementation if it is available, otherwise it chooses the Boost implementation. The default can be overriden for any of the 28 different implementations which CXXD supports. With all the talk about supporting C++11 or C++14 in new code, the library offers a way of supporting C++11 or C++14 standard libraries if available whether one writes in C++03 dialect or uses the new language features of C++11 on up. The Cxx dual library itself, being macro based, should work with any C++ code at that code's language level. The library itself is NOT, repeat NOT, an attempt to enforce a C++ language level for anybody who wants to use it. I have a little more work I am doing on increasing the support for Boost Build in the library, but all the central implementation of the library is complete in my mind. Questions, comments, or bug reports are always welcome, either here in this mailing list, in the Boost Library Incubator, or as Github issues, by those who are interested in trying the library out or reading the documentation. I will be using CXXD in another library on which I am working but hopefully others will find a use for it in their own code.

5 30

[exception] Broken in master?
by John Maddock 06 Jun '16

06 Jun '16

Anything that includes Boost.Exception is currently broken on master for all compilers, for example: http://www.boost.org/development/tests/master/developer/output/teeks99-09j-… http://www.boost.org/development/tests/master/developer/output/Flast-FreeBS… The cause is the use of a partial-template specialization in info.hpp with no previous definition of class set_info_rv. Thanks, John.

2 1

Boost.Fiber mini-review May 23 - June 1: review report
by Nat Goodspeed 05 Jun '16

05 Jun '16

The Boost.Fiber mini-review is now closed. Results: Bjorn Reese: YES Niall Douglas (private): YES Agustín K-ballo Bergé: YES Niall Douglas reminds me that in a previous mini-review he already voted to accept the Fiber library. Unless he stated that he had changed his mind, it would be reasonable to carry forward that "yes" vote. However, he did reaffirm his previous stance. In that spirit, let me remind the community of another couple previous positive votes: Eugene Yakubovich Antony Polukhin Significantly, there were no remaining NO votes. I therefore conclude that the Boost community ACCEPTS the Fiber library into the Boost family of libraries. On behalf of the Boost community, I would like to congratulate Oliver Kowalke not only for his engineering work, but for considerable patience in working to improve the library and its documentation. Thank you, Oliver!

3 2

Re: [boost] Checking interest in std::get for PODs
by Bjorn Reese 04 Jun '16

04 Jun '16

On 06/03/2016 08:27 AM, Antony Polukhin wrote: > There's a C++14 library that is able to do basic reflections for PODs > without any macro magic or markup: https://github.com/apolukhin/magic_get Could the "Enums will be returned as their underlying type" limitation be partially worked around by allowing users to register their own enums?

3 2