- Boost - lists.preview.boost.org

[filesystem] How to remove specific files from a directory?
by Andrzej Krzemienski 14 Sep '16

14 Sep '16

Hi, I wonder what is boost::filesystem recommendation for solving the following problem. I want to remove all files from a given directory that satisfy a certain predicate, e.g., only these whose names start with letter "s". It is my understanding that the calling filesystem::remove may invalidate the iterator, and therefore the following solution is incorrect: fsys::directory_iterator it{path}, itEnd{}; for ( ; it != itEnd ; ++it ) { if (predicate(*it)) fsys::remove(it->path()); } But, is the following guaranteed to work?: fsys::directory_iterator it{path}, itEnd{}; for ( ; it != itEnd ; ) { if (predicate(*it)) fsys::remove((it++)->path()); else ++it; } If not, does there exist a dedicated solution for solving this problem that would not require of me N traversals through the directory? Thanks, &rzej;

6 11

[release] Boost 1.62.0 Beta 1
by Rene Rivera 14 Sep '16

14 Sep '16

The first beta packages for 1.62.0 beta 1 are now available: <https://sourceforge.net/projects/boost/files/boost/1.61.0.beta.1/> The SHA256 checksums are as follows: f7cc83e6a3b03cd7aa8822992aa3e36422cc2214644d69277ef55a4db51f44bd boost_1_62_0_b1.7z 4057993811e40b1fd4719675e44c2550b6c2379546192da2299c17fec9a3dddf boost_1_62_0_b1.tar.bz2 fb0c10b625c5ec47cc837b54740540e400c59571b2eabf427c00f32bffc6ca70 boost_1_62_0_b1.tar.gz b38ef21c43c5ff814a2144bc23871c134164e7f51c71672d0f49a44636fb50b5 boost_1_62_0_b1.zip As always, the release managers would appreciate it if you download the archive of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. Thanks! -- The release managers -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

4 4

Re: [boost] [Boost-users] [release] Boost 1.62.0 Beta 1
by Rene Rivera 13 Sep '16

13 Sep '16

On Mon, Sep 12, 2016 at 12:44 AM, Oliver Kowalke <oliver.kowalke(a)gmail.com> wrote: > 2016-09-12 0:00 GMT+02:00 Tom Kent <lists(a)teeks99.com>: > >> Since the fiber build was a failure, >> > > should be fixed > Could someone try a build of the master snapshot to see if it's really fixed? I'm still in favor of a beta 2 build to make sure that gets flushed out >> before going to RCs. >> > > +1 > We can certainly do that. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

2 1

[math] Undefined reference to promote_args
by Florian Lindner 13 Sep '16

13 Sep '16

Hello, when compiling a file that uses float_distance from #include <boost/math/special_functions/relative_difference.hpp> I get a linking error: undefined reference to `boost::math::tools::promote_args<double, double, float, float, float, float>::type boost::math::float_distance<double, double>(double const&, double const&)' I try to add all boost_math libs I could find, but none helped: -lboost_system -lboost_filesystem -lboost_math_tr1 -lboost_math_c99 -lboost_math_c99 Since float_distance is not a C99 / TR1 function, shouldn't boost.math work as header only? What is the problem here? Thanks, Florian

2 1

[qi][endian]BOOST_ENDIAN_FORCE_PODNESS is defined in Qi
by Takatoshi Kondo 12 Sep '16

12 Sep '16

Hi, I'm using Boost.Endian with Boost.Qi. It seems that BOOST_ENDIAN_FORCE_PODNESS is defined at boost/spirit/home/support/detail/endian.hpp http://www.boost.org/doc/libs/1_61_0/boost/spirit/home/support/detail/endia… And boost/spirit/include/qi.hpp includes boost/spirit/home/support/detail/endian.hpp According to the Boost.Endian document, endian_buffer's constructors are disappeared by BOOST_ENDIAN_FORCE_PODNESS. http://www.boost.org/doc/libs/1_61_0/libs/endian/doc/buffers.html I'd like to use both endian_buffer's constructors and Boost.Qi. Is there any good way to do that? I don't know much abour Boost.Qi, but defining BOOST_ENDIAN_FORCE_PODNESS in the header file makes big side effects. For my workaround, I changed my include order. Sucessfully compiled http://melpon.org/wandbox/permlink/gSijxeBFJorWpzSd Error ocuured http://melpon.org/wandbox/permlink/FVffqcw8JEKGFXU0 --- Takatoshi Kondo

1 0

[property_tree] arrays in info files ?
by alainm 11 Sep '16

11 Sep '16

Hi, Is there a simple way to specify an array value with the info format, something like arr { 42 "" 43 "" 44 "" } but without the empty strings. thanks

1 0

docca: C++ Documentation XSLT library
by Vinnie Falco 09 Sep '16

09 Sep '16

Hi. When I developed Beast for Boost.Asio (https://github.com/vinniefalco/Beast) I lifted the xsl transforms from Boost.Asio (thanks Chris!) and adapted them. These scripts take the output of Doxygen and transform them into Boost.Book code (or QuickBook code or whatever its called). In other words, it creates a file called reference.qbk. This file is included in the documentation, which gets processed through a Jamfile to produce the HTML documentation that you see here: http://vinniefalco.github.io/beast/index.html This is great, and I am using the same system for my new key/value database engine (https://github.com/vinniefalco/NuDB/) The problem is that now I want to start another project and use the same documentation, but there is a considerable amount of copying going on here. The entire reference.xsl file is copied and placed in the new project: https://github.com/vinniefalco/NuDB/blob/master/doc/reference.xsl This file has to be edited significantly because it has references to project-specific namespaces, prefixes, and various other annoying minutiae. Therefore, I have started a new project called "docca:" https://github.com/vinniefalco/docca This project aims to refactor my variant of Boost.Asio's reference.xsl file so that it can be re-used in other projects. The procedure would be to create your own empty .xsl file, and include docca's xsl file after defining some variables. For example: <?xml version="1.0" encoding="utf-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> <xsl:variable name="namespace" select="'ripple::'"/> <xsl:include href="../include/docca/doxygen.xsl"/> </xsl:stylesheet> Above is the file you provide, while include/docca/doxygen.xsl is provided by docca (This is very much a work in progress). By this point many of you have fallen asleep, XSLT is a great cure for insomnia. If you're still awake you're probably very excited at the prospects of a turn-key solution for making great looking docs out of Javadoc comments in your C++ headers so I'll move right on to the questions: 1. Is there already a system for doing this? 2. If not, is there any interest in such a system? Is this project worth the effort? 3. Is this approach viable? Or is there a different approach? 4. Are these the right tools for the job? 5. Is there anyone out there who is fairly knowledgeable with XSLT and Boost.Book / QuickBook? Disclaimer: I am by no means an expert at either Boost.Book, Quick.Book, XSLT, or bjam. My only experience with these tools is recently, to put the Beast repository together. -- Follow me on Github: https://github.com/vinniefalco

2 1

Header-only singletons (was Re: [config] RFC PR 82)
by Vinnie Falco 09 Sep '16

09 Sep '16

On Mon, Aug 1, 2016 at 4:13 PM, Vinícius dos Santos Oliveira >...I want my library header only and Boost.System requires the category to > be a single static object and it'll even use address comparison to test if the > categories are the same: > ... > Is it guaranteed the above code will return the same object even if this > code was included in different libraries used by the same program? Sorry for the late reply. This header-only idiom works: inline boost::system::error_category const& my_category() { struct my_error_category : boost::system::error_category { ... }; static my_error_category cat; return cat; } This idiom also works: template<class = void> boost::system::error_category const& my_category() { struct my_error_category : boost::system::error_category { ... }; static my_error_category cat; return cat; } Justification: >From the C++ standard (see https://isocpp.org/std/the-standard) 7.1.6 describes inline functions. It says they must exist in every TU that they are used in, and must be the same in all TUs (no diagnostic required). 7.1.6 p6 also states that the address of an (extern) inline function shall be the same in all TUs. Elsewhere, the standard specifies that inline functions are extern by default. Empirical evidence also supports these claims, both of the aforementioned idioms have been used extensively in my projects under gcc, clang, and msvc. This likely upcoming feature (maybe its already in?) further cements support for global variables in header-only libraries: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/n4424.pdf However, even in the absence of additional language features, the ability to have global variables in header-only libraries exists today, with nothing more than C++11 support. Hope this helps!

1 0

[config] recent change to suffix.hpp causing several failures for Oracle Developer Studio 12.5
by Aparna Kumta 09 Sep '16

09 Sep '16

A recent change to suffix.hpp seems to cause several tests to fail when compiling with Oracle Developer Studio12.5. The error is: "CC" -std=c++11 -xO4 -mt -erroff=%none -m32 -DBOOST_ALL_NO_LIB=1 -DBOOST_CHRONO_STATIC_LINK=1 -DBOOST_SYSTEM_NO_DEPRECATED -DBOOST_SYSTEM_STATIC_LINK=1 -DBOOST_TEST_NO_AUTO_LINK=1 -DBOOST_TIMER_STATIC_LINK=1 -DNDEBUG -D__typeof__=__typeof__ -I".." -c -o ./count.o" "../libs/accumulators/test/count.cpp" "../boost/config/suffix.hpp", line 628: Error: Badly formed constant expression. <snipped> See: http://www.boost.org/development/tests/develop/developer/output/oracle-spar… % diff ./suffix.hpp ./suffix.hpp_orig 626a627,630 > # elif defined(__has_cpp_attribute) > # if __has_cpp_attribute(noreturn) > # define BOOST_NORETURN [[noreturn]] > # endif % Thanks, Aparna

2 1

[test] Test failures for gcc 4.6
by Andrey Semashev 09 Sep '16

09 Sep '16

Hi, I'm seeing these test failures for gcc 4.6 (MinGW): http://www.boost.org/development/tests/develop/developer/output/igaztanaga-… Looks like the error originates from Boost.Test, and I can also see lots of failures in Boost.Test itself for that compiler. Is this a known problem? Any fixes planned?

2 5