- Boost - lists.preview.boost.org

Boost.GSL?
by David Sankel 05 Oct '15

05 Oct '15

As you may or may not know, Bjarne Stroustrup, Herb Sutter, and others have announced a new set of C++ guidelines[1] and an accompanying library[2] that supports them. For many folks, it would be difficult to incorporate a new library into their organizations, but there is a strong desire to make use of the guidelines. I floated the idea of including GSL in Boost as a distribution mechanism to Bjarne and he said he doesn't have any objection to the idea in principle, although he is hesitant to having to go through an extensive review process where some of these basic structures would change. What do you all think? Would it be appropriate and/or desirable to have a Boost.GSL library? -- David Sankel [1] https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md [2] https://github.com/Microsoft/GSL

9 16

Re: [boost] boost.test regression or behavior change (was Re: Boost.lockfree)
by Brian Wood 04 Oct '15

04 Oct '15

Bjorn Reese writes >On 10/04/2015 12:18 PM, Gennadiy Rozental wrote: > >> Sooner rather than later we should have this discussion and setup timeline. >> IMO it had very little sense to continue to maintain c++03 workarounds. >> Boost code should be an example how modern c++ libraries should look like. >> And c++03 compatibility is directly in a way of this goal. > > You appear to have missed the many discussions on this topic. > > While Boost started out to design cutting-edge libraries, it has been > caught by its own success. Today there is a large user-base that still > uses C++03, and that are unlikely to upgrade in the foreseeable future. > > Therefore, the current consensus is that existing libraries should not > increase their standards requirements. New libraries are free to decide > their standards requirements (although it will probably be questioned > during a formal review.) > Support for that is dwindling as more projects adopt 2011 or newer versions of C++. I understand Gennadiy and Raffi's desire to discuss this issue again. C++ 2011 is required to use my software. That decision was also based on limited resources and the belief that C++ 2011 had some helpful things for on line code generation. If I had more resources, I could support C++ 2003, but at this point I'm happy to not have to support that. As time goes on, more people are using C++ 2011 or newer. -- Brian Ebenezer Enterprises - In G-d we trust. http://webEbenezer.net

1 0

Boost perf tests?
by Stephan T. Lavavej 03 Oct '15

03 Oct '15

Hi Boost devs, Does Boost have any runtime perf tests? We (MSVC) are looking for something that uses modern C++, which would reveal areas where our optimizer and libraries could be improved. I looked around briefly, but didn't find anything. Thanks, STL

6 6

[optional] Specializing optional to save space
by David Stone 03 Oct '15

03 Oct '15

Andrzej posted another thread about creating a new compact_optional class. The goal of this class is to make it easy to create a new optional type with a special sentinel value. This allows easy customization per instance of an optional value. This post is about the opposite approach: making it easier to specialize optional to provide special behavior for all instances of a given optional type. When I bring this up, people often compare it to the vector<bool> specialization, but this is a completely different issue. The problem of vector<bool> is that it does not actually store a bool anywhere, so it cannot return a reference to one. This would still store a T somewhere. For the rest of the discussion, I will be assuming a typical standard library implementation on a 64-bit system. Whenever I talk about specific sizes of objects, mentally insert "on most common systems". The principles apply generally. Consider the case of optional<std::string>. Using the naive implementation, this object is 8 bytes larger than std::string, due to alignment requirements. However, there are certain representations of std::string that are not actually possible. For instance, for common implementations of std::string you cannot have std::string::size() == std::numeric_limits<std::string::size_type>::max() *. We can take advantage of this if our std::string implementation stores the capacity as an integer value, rather than a pointer to the end of the storage. Therefore, we could have implementations that look something like this: class string { friend optional<string>; }; template<> class optional<std::string> { optional(none_t) { // Use friendship to just set capacity to sentinel value } explicit operator bool() const { return m_data.capacity() == std::numeric_limits<std::string::size_type>::max(); } }; optional<std::string> still stores std::string in it, so operator*() works just fine. The initialized check is still just comparing a field against a compile-time constant. This makes this purely a space optimization that cannot be detected by the user, unless they use sizeof(optional<std::string>). I believe all of this is possible today with the current specification of boost::optional (and would definitely be allowed for the proposed std::experimental::optional). However, this requires the creator of each specialization to implement the full optional interface. What's more, it is especially tricky to specialize optional for a class template when you only want to specialize on certain specializations of the class template. My use case for this is my bounded::integer library. This library lets you specify the bounds of your integer as template parameters. If your bounded::integer has a narrower range than its underlying integer, you can take advantage of this to make a more space-efficient optional. If, however, the bounded::integer min and max are equal to that of the underlying type, there is no extra space and we want the default optional implementation. With the current specialization approach, it is the responsibility of the specializer to reimplement all of optional. A better approach to easily support this space optimization is as follows: optional contains an instance of optional_storage<value_type>. optional_storage has a much narrower interface: * optional_storage() leaves it uninitialized * optional_storage(in_place_t, T && ...) constructs the value directly with the variadic arguments * emplace(T && ...) constructs an object when there may be one in existence already * reset() destroys the contained object and sets the storage to uninitialized * is_initialized() says whether the contained object is initialized. This could be replaced with explicit operator bool(); I have no preference. * value() returns a reference to the value We need both the constructor and the emplace function to allow literal optional types. This is because for the general case, emplace calls placement new, which is not allowed in a constexpr function. This solves the problem of specializers having to implement the entire interface of optional just to change how the uninitialized state is stored. However, it still does not solve the problem I mentioned earlier about allowing easy use of the default storage policy for some specializations of your own class template. To solve that, we need one more class: default_optional_storage. default_optional_storage<T> is a literal type if T is a literal type (in practice, std::is_trivially_destructible<T>::value is all you really need to test). It implements the same interface as optional_storage<T>. The default implementation of optional_storage<T> is template<typename T> struct optional_storage : default_optional_storage<T> { private: using base = default_optional_storage<T>; public: using base::base; }; This means that the optional library would have at least three classes in its public interface: * optional * optional_storage * default_optional_storage To see a working example of this (including a specialization for bounded::integer), see https://bitbucket.org/davidstone/bounded_integer/src/2defec41add2079ba023c2… https://bitbucket.org/davidstone/bounded_integer/src/2defec41add2079ba023c2… * The reason is that std::string::size_type is a typedef for std::size_t, which is equivalent in range to std::uint64_t. However, std::iterator_traits<std::string::iterator>::difference_type is std::ptrdiff_t, which is equivalent in range to std::int64_t. This means that for the largest std::string, std::distance(begin(), end()) cannot be more than std::numeric_limits<std::ptrdiff_t>::max(), which is less than std::numeric_limits<std::size_t>::max().

6 15

[type_traits] common_type errors with Oracle compiler
by Andrey Semashev 03 Oct '15

03 Oct '15

Hi, Both oracle-intel-S2-next-cpp11 and oracle-sparc-S2-next-stlport4 testers fail to compile common_type as it is being used in Boost.Chrono. This in turn affects compilation of Boost.Thread and multiple other library tests. The error can be seen here: http://www.boost.org/development/tests/develop/developer/output/oracle-inte… Just in case if the test results go down, I'm copying the error inline below. Could it be fixed? "CC" -std=c++11 -temp=/tmp/bn -xO4 -mt -erroff=%none -m32 -KPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_DYN_LINK=1 -DBOOST_CHRONO_DYN_LINK=1 -DBOOST_SYSTEM_DYN_LINK=1 -DBOOST_SYSTEM_NO_DEPRECATED -DBOOST_THREAD_BUILD_DLL=1 -DBOOST_THREAD_POSIX -DBOOST_THREAD_USE_DLL=1 -DNDEBUG -D__typeof__=__typeof__ -I".." -c -o "/export/home/sstrunk-tester/boost_regression/boost_regression_develop/boost_intel-S2_cpp11/results/boost/bin.v2/libs/atomic/test/atomicity.test/sun-next_cpp11/release/threading-multi/atomicity.o" "../libs/atomic/test/atomicity.cpp" "../boost/chrono/duration.hpp", line 405: Error: type is not a member of boost::common_type<long long, long long>. "../boost/thread/pthread/timespec.hpp", line 52: Where: While specializing "boost::common_type<boost::chrono::duration<long long, boost::ratio<1, 1000000000>>, boost::chrono::duration<long long, boost::ratio<1, 1>>>". "../boost/thread/pthread/timespec.hpp", line 52: Where: Instantiated from boost::chrono::operator-<Rep1, Period1, Rep2, Period2>(const duration<Rep1, Period1>&, const duration<Rep2, Period2>&). "../boost/thread/pthread/timespec.hpp", line 52: Where: Instantiated from non-template code. "../boost/chrono/duration.hpp", line 406: Error: A declaration does not specify a tag or an identifier. "../boost/thread/pthread/timespec.hpp", line 52: Where: While specializing "boost::common_type<boost::chrono::duration<long long, boost::ratio<1, 1000000000>>, boost::chrono::duration<long long, boost::ratio<1, 1>>>". "../boost/thread/pthread/timespec.hpp", line 52: Where: Instantiated from boost::chrono::operator-<Rep1, Period1, Rep2, Period2>(const duration<Rep1, Period1>&, const duration<Rep2, Period2>&). "../boost/thread/pthread/timespec.hpp", line 52: Where: Instantiated from non-template code. "../boost/chrono/duration.hpp", line 406: Error: Use ";" to terminate declarations. "../boost/thread/pthread/timespec.hpp", line 52: Where: While specializing "boost::common_type<boost::chrono::duration<long long, boost::ratio<1, 1000000000>>, boost::chrono::duration<long long, boost::ratio<1, 1>>>". "../boost/thread/pthread/timespec.hpp", line 52: Where: Instantiated from boost::chrono::operator-<Rep1, Period1, Rep2, Period2>(const duration<Rep1, Period1>&, const duration<Rep2, Period2>&). "../boost/thread/pthread/timespec.hpp", line 52: Where: Instantiated from non-template code. "../boost/chrono/duration.hpp", line 406: Error: "}" expected instead of ">". "../boost/thread/pthread/timespec.hpp", line 52: Where: While specializing "boost::common_type<boost::chrono::duration<long long, boost::ratio<1, 1000000000>>, boost::chrono::duration<long long, boost::ratio<1, 1>>>". "../boost/thread/pthread/timespec.hpp", line 52: Where: Instantiated from boost::chrono::operator-<Rep1, Period1, Rep2, Period2>(const duration<Rep1, Period1>&, const duration<Rep2, Period2>&). "../boost/thread/pthread/timespec.hpp", line 52: Where: Instantiated from non-template code. "../boost/thread/pthread/timespec.hpp", line 52: Error: The operation "const boost::chrono::duration<long long, boost::ratio<1, 1000000000>> - boost::chrono::duration<long long, boost::ratio<1, 1>>" is illegal. 5 Error(s) detected.

3 4

Compiler warnings after boost update
by Auer, Jens 03 Oct '15

03 Oct '15

Hi, we compile with high compiler warnings setting (-Wall, -Wpedantic), and treat compiler warnings as errors. Recently, I had to upgrade the boost library version from 1.53 to at least 1.55. Since there was no package available, I compiled it by hand from the source code. With 1.53, everything compiled fine, but with the newer version my builds now break because the boost library generates a lot of warnings, e.g. /cots/boost-1.55/include/boost/iterator/iterator_concepts.hpp: At global scope: /cots/boost-1.55/include/boost/mpl/assert.hpp:288:54: error: use of old-style cast [-Werror=old-style-cast] boost::mpl::assert_arg( (void (*) pred)0, 1 ) \ ^ /cots/boost-1.55/include/boost/mpl/assert.hpp:59:58: note: in definition of macro ‘BOOST_MPL_AUX_ASSERT_CONSTANT’ # define BOOST_MPL_AUX_ASSERT_CONSTANT(T, expr) enum { expr } /cots/boost-1.55/include/boost/range/algorithm/equal.hpp: In function ‘bool boost::range::equal(const SinglePassRange1&, const SinglePassRange2&, BinaryPredicate)’: /cots/boost-1.55/include/boost/concept/detail/general.hpp:71:20: error: typedef ‘boost_concept_check185’ locally defined but not used [-Werror=unused-local-typedefs] BOOST_PP_CAT(boost_concept_check,__LINE__) /cots/boost-1.55/include/boost/property_tree/xml_parser.hpp:52:59: required from ‘void boost::property_tree::xml_parser::read_xml(std::basic_istream<typename Ptree::key_type::value_type>&, Ptree&, int) [with Ptree = boost::property_tree::basic_ptree<std::basic_string<char>, std::basic_string<char> >; typename Ptree::key_type::value_type = char; typename Ptree::key_type::value_type = char]’ /home/auerj/MDAF/src/commons/src/crypto/KeyFileReader.cpp:43:34: required from here /cots/boost-1.55/include/boost/property_tree/detail/rapidxml.hpp:1204:33: error: zero as null pointer constant [-Werror=zero-as-null-pointer-constant] if (first_attribute()) ^ /cots/boost-1.55/include/boost/property_tree/detail/rapidxml.hpp:1204:33: error: zero as null pointer constant [-Werror=zero-as-null-pointer-constant] /cots/boost-1.55/include/boost/property_tree/detail/rapidxml.hpp:1211:45: error: zero as null pointer constant [-Werror=zero-as-null-pointer-constant] These are just some examples, there are literally hundreds of warnings. It is enough to just include ptree.hpp, but other headers have the same issue. I am wondering why this came up after the update. Is it a configuration problem during the build of the boost libraries, or is it an issue in the boost libraries? I find it hard to believe that the code quality changed so much between the versions. What is the policy of the boost project concerning compiler warnings in installation headers? I would assume that the libraries should compile without warnings on supported compilers, either because there are no issues, or because warnings are disabled in the boost headers. Best wishes, Jens -- Jens Auer | CGI | Software-Engineer CGI (Germany) GmbH & Co. KG Rheinstraße 95 | 64295 Darmstadt | Germany T: +49 6151 36860 154 jens.auer(a)cgi.com<mailto:jens.auer@cgi.com> Unsere Pflichtangaben gemäß § 35a GmbHG / §§ 161, 125a HGB finden Sie unter de.cgi.com/pflichtangaben<http://de.cgi.com/pflichtangaben>. CONFIDENTIALITY NOTICE: Proprietary/Confidential information belonging to CGI Group Inc. and its affiliates may be contained in this message. If you are not a recipient indicated or intended in this message (or responsible for delivery of this message to such person), or you think for any reason that this message may have been addressed to you in error, you may not use or copy or deliver this message to anyone else. In such case, you should destroy this message and are asked to notify the sender by reply e-mail.

10 14

[build][regression] Problems when trying to run automated regression tests for MSVC-7.1
by Ion Gaztañaga 03 Oct '15

03 Oct '15

Hi, Since Boost 1.55 minimum requirements include Visual C++ 2003. Since currently there is no regression report for this compiler, I'm trying to follow the steps detailed here and try to fill the gap: http://www.boost.org/development/running_regression_tests.html All the source code is downloaded, my user-config.jam only contains "using msvc ;" but it seems that Boost.Build continues to be broken for MSVC-7.1: <output> notice: Loading user-config configuration file 'user-config.jam' from 'C:/Users/igaztanaga'. notice: [msvc-cfg] msvc-7.1 detected, command: 'C:\Program Files (x86)\Microsoft Visual Studio .NET 2003\Vc7\bin\cl.exe' notice: will use 'C:\Program Files (x86)\Microsoft Visual Studio .NET 2003\Vc7\bin\cl.exe' for msvc, condition <toolset>msvc-7.1 C:/boost/develop/boost_bb/src/tools\msvc.jam:1072: in configure-really *** argument error * rule generate-setup-cmd ( version : command : parent : options * : cpu : global-setup : default-global-setup-options : default-setup ) * called with: ( 7.1 : C:\Program Files (x86)\Microsoft Visual Studio .NET 2003\Vc7\bin : C:\Program Files (x86)\Microsoft Visual Studio .NET 2003\Vc7 : <command>C:\Program Files (x86)\Microsoft Visual Studio .NET 2003\Vc7\bin\cl.exe : i386 : : x86 : vcvars32.bat ) * missing argument global-setup C:/boost/develop/boost_bb/src/tools\msvc.jam:798:see definition of rule 'generate-setup-cmd' being called C:/boost/develop/boost_bb/src/tools\msvc.jam:201: in configure C:/boost/develop/boost_bb/src/tools\msvc.jam:153: in msvc.init C:/boost/develop/boost_bb/src/build\toolset.jam:43: in using C:\Users\igaztanaga\user-config.jam:49: in modules.load c:/boost/develop/boost_bb/src\build-system.jam:249: in load-config c:/boost/develop/boost_bb/src\build-system.jam:389: in load-configuration-files c:/boost/develop/boost_bb/src\build-system.jam:524: in load C:\boost\develop\boost_bb\src/kernel\modules.jam:295: in import C:\boost\develop\boost_bb\src/kernel/bootstrap.jam:139: in boost-build C:\boost\develop\boost_regression\boost-build.jam:57: in module scope </output> I can't figure out what's wrong in msvc.jam. Comments on that file suggest that MSVC-7.1 should be supported although it seems that since MSVC-8.0 the configuration script architecture changed. I'd be glad if any Boost.Build expert could have a look at this issue. Many thanks, Ion PS: Full output for command... python run.py --runner=igaztanaga --toolsets=msvc-7.1 --tag=develop --incremental --libraries=move --have-source > output.txt ...attached.

2 4

compact_optional -- prompting interest
by Andrzej Krzemienski 02 Oct '15

02 Oct '15

Hi Everyone, I would like to inquire if there would be an interest in Boost in another library for storing optional objects, but working under different design goals. Compact optional T has (or can have) the same sizeof as T. It uses one indicated value of T to represent the "empty" (or "singular") value. You can declare it like this: compact_optional<evp_int<int, -1>> oi; This reads: we have an optional int, with type int inside, where -1 represents the empty value. It can never have a genuine (non-empty value -1). This can be used, for instance, to wrap the std::string::npos into: compact_optional<evp_int<string::size_type, string::npos>> With the same memory layout as std::string::size_type, but with the special syntax for managing the singular value. It is not meant to be an alternative to Boost.Optional: it targets a different application space. The (single-header) implementation is at: https://github.com/akrzemi1/compact_optional The documentation is at: https://github.com/akrzemi1/compact_optional/blob/master/documentation.md For the motivation and design rationale see this article: https://akrzemi1.wordpress.com/2015/07/15/efficient-optional-values/ Any feedback is welcome. Regards, &rzej

17 43

[build] Issue with -- argument
by Gennadiy Rozental 01 Oct '15

01 Oct '15

Hi, Due to the change in Boost.Test parameter handling I needed update Boost.Test Jamfile, since I was passing baseline pattern file names as arguments to the test module. Here is snippet from my Jamfile: return [ $(test-rule) $(source_files) ../build//$(usage-variant) $(extra-libs) : -- <============= Note: I added '--' : $(pattern_file) ... Unfortunately -- disappears for some reason from command line. I found that the following works: return [ $(test-rule) $(source_files) ../build//$(usage-variant) $(extra-libs) : -- "" <============= Note "" : $(pattern_file) ... Can we fix it so that "" is not required? Is there a different workaround? Gennadiy

1 0

Re: [boost] [regression] Tests for 'develop' not showing
by Tom Kent 30 Sep '15

30 Sep '15

On Wed, Sep 23, 2015 at 8:16 AM, Tom Kent <lists(a)teeks99.com> wrote: > > On Tue, Sep 22, 2015 at 9:53 PM, Rene Rivera <grafikrobot(a)gmail.com> > wrote: >> >> > On Wed, Sep 9, 2015 at 4:35 PM Edward Diener <eldiener(a)tropicsoft.com> >>>> > wrote: >>>> > >>>> > > Trying >>>> > > >>>> http://www.boost.org/development/tests/develop/developer/summary.html I >>>> > > get: >>>> > > >>>> > > "Error extracting file: The specified zipfile was not found." >>>> > > >>>> >>>> And they are messed up again. Tom can you look into your side of this? >> When I generated the results I got the ZIP files to be 1.5GiB and 2.0GiB, >> approximately, for develop and master, respectively. Yet what I see on the >> web site now is 1.5GiB and 200MiB. Which is clearly incorrect. And it's >> precisely the shorter ZIP, i.e. master.zip, that now doesn't work. I.e >> browsing develop results works, but not browsing master results. >> > > Over the last week I've seen both the master and develop results showing > the zip error message. > > I just noticed that in the last master run, I had a segfault in the > processing: > > tomkent@eddie:~/tmp/boost_reports/boost-reports⟫ tail master.log > Reading failures markup > Reading > /home/tomkent/tmp/boost_reports/boost-reports/master/incoming/master/processed/BP > x86_64 C++11.xml > Merging expected results > Generating links pages > Reading > /home/tomkent/tmp/boost_reports/boost-reports/master/incoming/master/processed/CrystaX.NET-apilevel-19-armeabi-v7a-hard.xml > Merging expected results > Generating links pages > Reading > /home/tomkent/tmp/boost_reports/boost-reports/master/incoming/master/processed/CrystaX.NET-apilevel-19-armeabi-v7a.xml > Merging expected results > Segmentation fault (core dumped) > > I'll look into it more tonight. > Tom > It looks like running the reports (esp master) is taking much longer...up to 2hrs. I had a cron job running every hour, which corrupted things when it was kicked off a second time while the first was still running. I've made a change in the script to setup a lock file, so that only one instance will run and submitted a pull request against the regression repo. It's already running on my report generator, so hopefully the problem won't show up again. If anyone sees it please let me know. Tom

4 6

[git] Testing and Pushing updates to library
by Artyom Beilis 30 Sep '15

30 Sep '15

Hello, I'm back to Boost after my last commits were in svn and now I need to make sure I do stuff correctly in git/github. In boost-svn there were trunk for development and release for up-to date release, currently master is what "release branch" is svn was and develop is what trunk? Q: Is it correct. I have several fixes - I pushed them to master branch of Boost.Locale library. https://github.com/boostorg/locale/compare/26482aa844...ea55386441 I did same for develop (I hope correctly) Q: Is pushing changes to master it enough to get them into next boost release? I had some strange behavior of "detached Head" so I needed to create small temporary local branch and than merge it to master... Q: is it normal? Can't I commit/push directly to master without temporary branch? Testing - in svn there were regression tests for both release and trunk branches of svn... Q: What happens now with regression tests I cound't find the information in the wiki. Thanks. Artyom Beilis -------------- CppCMS - C++ Web Framework: http://cppcms.com/ CppDB - C++ SQL Connectivity: http://cppcms.com/sql/cppdb/

2 1

how to pass -std=c++14 to b2 while building boost libraries
by Frédéric Bron 30 Sep '15

30 Sep '15

Hi, I would like to build a c++14 version of boost libraries on my system. I have the intel compiler (15.0.3) on a x86_64 linux machine (2.6.32-279.19.1.el6.x86_64). I do the following: 1. build b2 CC="icc" CFLAGS="-O2 -DNDEBUG -xhost" CXX="icpc" CXXFLAGS="-O2 -DNDEBUG -xhost -std=c++14" AR="ar" AS="as" RANLIB="ranlib" ./bootstrap.sh --without-icu --prefix=/myusr/icc-15.0.3-c++14-release/boost --with-toolset=intel-linux 2. edit user-config.jam My user-config.jam, located in the boost source directory contains: using intel-linux : : icpc : <compilerflags>-xhost <compilerflags>-std=c++14 ; 3. run b2 ./b2 -d2 -j16 -sBZIP2_INCLUDE=/myusr/icc-15.0.3-c++14-release/bzip2/include -sBZIP2_LIBPATH=/myusr/icc-15.0.3-c++14-release/bzip2/lib -sZLIB_INCLUDE=/myusr/icc-15.0.3-c++14-release/zlib/include -sZLIB_LIBPATH=/myusr/icc-15.0.3-c++14-release/zlib/lib --layout=system --user-config=user-config.jam --without-mpi --without-python --without-context --without-coroutine link=static threading=multi runtime-link=shared target-os=linux address-model=64 variant=release install The problem I see is that the flag -std=c++14 is not passed to the compiler. For example, this is an output of b2: "icpc" -c -xc++ -w1 -inline-level=2 -O3 -ip -pthread -m64 -DBOOST_ALL_NO_LIB=1 -DBOOST_FILESYSTEM_STATIC_LINK=1 -DBOOST_SYSTEM_STATIC_LINK=1 -DNDEBUG -I"." -c -o "bin.v2/libs/filesystem/build/intel-linux/release/link-static/threading-multi/codecvt_error_category.o" "libs/filesystem/src/codecvt_error_category.cpp" no trace of -std=c++14 flag. How can I send that flag to the compiler? Apparently, the problem is the same when using g++ 5.2.0. Frédéric

2 2

[boost.build] broken link
by Frédéric Bron 30 Sep '15

30 Sep '15

On this page: http://www.boost.org/doc/libs/1_59_0/tools/build/index.html the link to the documentation is broken: http://www.boost.org/doc/libs/1_59_0/tools/build/doc/html/index.html error message: 404 Not Found File "/home/www/live.boost.org/common/code/../../doc/archives/boost_1_59_0/tools/build/doc/html/index.html" not found. Unable to find file. Cheers, Frédéric

2 1

develop tests
by Robert Ramey 29 Sep '15

29 Sep '15

When I try to look at the tests of the develop branch at http://www.boost.org/development/tests/develop/developer/serialization.html I get an error message. Has this been resolved yet? Is there anything I have to do? Robert Ramey

1 0

Variadics bug in MSVC-12.0
by Gennadiy Rozental 29 Sep '15

29 Sep '15

Hi, While working on improving of implementation of data driven tests, I found rather annoying bug in MSVC-12.0 with variadic templates. The code seems to work fine with msvc-14.0, gcc 4.8 and clang 3.4. I did not try msvc- 13.0. Does anyone know a workaround? Example follows (try to comment on/off line: auto const& t3). Gennadiy // C++ 14 index_sequence template <std::size_t... Ns> struct index_sequence {}; template<typename IS1, typename IS2> struct merge_index_sequence; template <std::size_t... Ns1, std::size_t... Ns2> struct merge_index_sequence<index_sequence<Ns1...>, index_sequence<Ns2...>> { typedef index_sequence<Ns1..., Ns2...> type; }; template <std::size_t B, std::size_t E, typename Enabler = void> struct make_index_sequence { typedef typename merge_index_sequence< typename make_index_sequence<B, (B + E)/2>::type, typename make_index_sequence<(B + E)/2, E>::type>::type type; }; template <std::size_t B, std::size_t E> struct make_index_sequence<B, E, typename std::enable_if<E == B + 1, void>::type> { typedef index_sequence<B> type; }; template <typename... T> using index_sequence_for = typename make_index_sequence<0, sizeof...(T)>::type; ////////////////////////////////////////////////////////////////////////// template<typename T1, typename T2> struct merged_tuple { typedef std::tuple<T1,T2> type; typedef std::tuple<T1 const&,T2 const&> ref; }; template<typename T1, typename ...T> struct merged_tuple<T1, std::tuple<T...>> { typedef std::tuple<T1, T...> type; typedef std::tuple<T1 const&, T const&...> ref; }; template<typename ...T, typename T1> struct merged_tuple<std::tuple<T...>, T1> { typedef std::tuple<T..., T1> type; typedef std::tuple<T const&..., T1 const&> ref; }; template<typename ...T1, typename ...T2> struct merged_tuple<std::tuple<T1...>, std::tuple<T2...>> { typedef std::tuple<T1..., T2...> type; typedef std::tuple<T1 const&..., T2 const&...> ref; }; template<typename ...T1, typename ...T2, std::size_t ...I1, std::size_t ...I2> inline typename merged_tuple<std::tuple<T1...>, std::tuple<T2...>>::ref tuple_merge_impl( std::tuple<T1 const&...> const& a1, std::tuple<T2 const&...> const& a2, index_sequence<I1...> const& , index_sequence<I2...> const& ) { using ref_type = typename merged_tuple<std::tuple<T1...>, std::tuple<T2...>>::ref; return ref_type( std::get<I1>(a1)..., std::get<I2>(a2)... ); } template<typename ...T1, typename ...T2> inline typename merged_tuple<std::tuple<T1...>, std::tuple<T2...>>::ref tuple_merge_impl( std::tuple<T1 const&...> const& a1, std::tuple<T2 const&...> const& a2 ) { return tuple_merge_impl( a1, a2, index_sequence_for<T1...>{}, index_sequence_for<T2...>{} ); } template<typename T> inline std::tuple<T const&> as_tuple( T const& arg ) { return std::tuple<T const&>( arg ); } template<typename ...T> inline std::tuple<T...> const& as_tuple( std::tuple<T...> const& arg ) { return arg; } template<typename T1, typename T2> inline typename merged_tuple<T1, T2>::ref tuple_merge( T1 const& a1, T2 const& a2 ) { return tuple_merge_impl( as_tuple( a1 ), as_tuple( a2 ) ); } int main() { auto const& t1 = tuple_merge( 1, 2 ); auto const& t2 = tuple_merge( 3, 4 ); auto const& t3 = tuple_merge( t1, 5 ); auto const& t4 = tuple_merge( 6, t2 ); return 0; }

1 0

Boost.Test: runtime parameter framework update
by Gennadiy Rozental 29 Sep '15

29 Sep '15

Hi, Over the years there were complains about the interface and functionality of the Boost.Test Unit Test Framework(UTF)'s runtime parameters. Primarily command line arguments handling, but also documentation and few other concerns. This update addresses all these issues, introduces few new features and makes runtime parameters much more user friendly. In addition new implementation significantly simpler. Here is short summary of fixed issues and significant new features: * (new) UTF now requires all user defined arguments to follow UTF specific arguments. They are separated by "--" marker. For example: test.exe --random -- /myarg:17 * (bug) UTF now properly supports arguments with spaces. For example: test.exe --log_sink="file name.txt" * (bug) UTF now reports missing value in arguments. For example: test.exe --log_sink=, produces: Missing an argument value for the parameter log_level in the argument -- log_level= * (bug/new) UTF now reports invalid parameters. Moreover, UTF now supports hints with possible typos. For example: test.exe --colour, produces: An unrecognized parameter in the argument --colour Did you mean one of these? color_output Suggestion is shown when close (1 char distance from unambiguous parameter name) exists. * (new) UTF now report possible ambiguous parameters. For example: test.exe --log=all, produces: An ambiguous parameter name in the argument --log=all Did you mean one of these? log_format log_level log_sink * (new) UTF parameter help now accepts optional parameter name. Moreover you can actually "guess" the name by providing just unambiguous prefix. In this case it shows detailed information about requested parameter, including semantic, possible values and formats. For example: test.exe --help=list_con, produces: Parameter: list_content Lists the content of test tree - names of all test suites and test cases. Command line formats: --list_content[=<HRF|DOT>] Environment variable: BOOST_TEST_LIST_CONTENT Parameter list_content instructs the framework to list the content of the test module instead of executing the test cases. Parameter accepts optional string value indicating the format of the output. Currently the framework supports two formats: human readable format (HRF) and dot graph format (DOT). If value is omitted HRF value is assumed. The changes will be released with next release of boost. Any comments are welcome. Gennadiy

1 0

Graphical debugging extension for VS2015 (Container, Geometry, Polygon, Variant, ...)
by Adam Wulkiewicz 29 Sep '15

29 Sep '15

Hi, For some time now I've been thinking about extending the capabilities of a debugger and to visualize data in more convenient way than the raw numbers. It's obvious to me that in many cases variables could be graphically visualized, in many cases this is the "natural" representation, this would greately simplify the debugging. I haven't found anything like it so I've decided to play with the VS2015 extensions, mostly because they're easy to write. This is what I came up with (see the readme): https://github.com/awulkiew/graphical-debugging Besides adding commonly used native visualizers for types from some Boost libraries it allows to display their graphical representation. The extension support Boost.Geometry models and other types used internally in this library, Boost.Polygon models (polygon_set_data is missing) and boost::variant storing geometries. As a bonus, it's possible to watch containers of values (some STL containers as well as boost::array and contiguous containers from Boost.Container) as charts. Maybe if there were enough interest it'd be worth to extend it and/or to add to the official VS extensions gallery. I'm a Boost.Geometry developer so in the future I plan to support all of the coordinate systems supported by the library, maybe other internals and basically anything that helps me with the development. But I can imagine that variables of types from various Boost libraries could also be visualized, e.g. Polygon's voronoi diagram and internals, Math's quaternions as 3D Axis-Angle, std::complex as a point on a plane, containers of complex numbers and in general arbitrary types represented somehow as a 1D, 2D or 3D objects, CircularBuffer e.g. as a pie chart, BGL's graphs, maybe GIL's images, Interprocess' shared memory blocks?, etc. So feel free to share suggestions and contribute if you like. Regards, Adam

3 5

Trying out CLion.. Free license..
by Rene Rivera 29 Sep '15

29 Sep '15

As some of you are aware JetBrains recently release a new IDE that has some rather cool features (re: <https://www.jetbrains.com/clion/>) for C++ programmers. I am personally interested in using CLion for Boost work. In particular I'm hoping to write a CLion plug-in that integrates Boost Build into the IDE. And hence I've have taken it upon myself to arrange for Boost developers to get licenses for library authors to use, if they so wish. If you are interested in getting a CLion license and are a current Boost Library author here's what I need: * An email from you requesting that you want a license. * In that email indicate which Boost libraries you are an author, or maintainer, of. * Send the email from an account that you want me to send you the license when we get it. I want to avoid having to update email information a year from now when I need to renew the licenses. * You have until the end of this week, roughly, to send that email. I'll collect that and request the Boost licenses from JetBrains. And "pass" them out with instructions as needed. Rene. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

6 7

CLion plug-in for Boost.Build (was: Trying out CLion.. Free license..)
by Mateusz Loskot 28 Sep '15

28 Sep '15

On 28 September 2015 at 21:19, Rene Rivera <grafikrobot(a)gmail.com> wrote: > On Mon, Sep 28, 2015 at 2:14 PM, Robert Ramey <ramey(a)rrsd.com> wrote: >> On 9/28/15 11:45 AM, Rene Rivera wrote: >> >>> As some of you are aware JetBrains recently release a new IDE that has >>> some >>> rather cool features (re: <https://www.jetbrains.com/clion/>) for C++ >>> programmers. I am personally interested in using CLion for Boost work. In >>> particular I'm hoping to write a CLion plug-in that integrates Boost Build >>> into the IDE. And hence I've have taken it upon myself to arrange for >>> Boost >>> developers to get licenses for library authors to use, if they so wish. >>> >> >> Hmm - wouldn't it be easier just to use CMake. You wouldn't have to write >> any plugin. The serialization library includes CMake files for that >> library's build and test and it works quite well. >> > > IMO no.. But I know that opinions differ ;-) Some time ago, I developed basic Boost.Build plugin for Qt Creator https://github.com/mloskot/qt-creator-plugin-boostbuild/ which interacts with the b2.exe command line. At that time, I also briefely discussed some API ideas with Volodya. Later, Volodya implemented the Boost.Build API and server mode http://lists.boost.org/boost-build/2015/03/27906.php May I ask, which option are you going to choose for your plugin? Is it going to be the command line approach, the new BB API or anything else? Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

2 2

[test] Regression - overloaded virtual function "boost::unit_test::test_observer::test_unit_skipped" is only partially overridden
by Vicente J. Botet Escriba 25 Sep '15

25 Sep '15

Hi, there is a regression in Boost.Test. Test output: boost/bin.v2/libs/test/build/intel-linux/release/link-static/threading-multi Rev 32fc9643eb674d60616412bb427bb6e0f0300cc0 / Thu, 24 Sep 2015 19:13:08 +0000 Compile [2015-09-24 20:55:11 UTC]: succeed "icpc" -c -xc++ -w2 -inline-level=2 -O3 -ip -pthread -m64 -DBOOST_ALL_NO_LIB=1 -DBOOST_CHRONO_STATIC_LINK=1 -DBOOST_SYSTEM_NO_DEPRECATED -DBOOST_SYSTEM_STATIC_LINK=1 -DBOOST_TIMER_STATIC_LINK=1 -DNDEBUG -I".." -c -o "/boosttest/develop/results/boost/bin.v2/libs/test/build/intel-linux/release/link-static/threading-multi/test_tools.o" "../libs/test/src/test_tools.cpp" In file included from ../boost/test/impl/test_tools.ipp(19), from ../libs/test/src/test_tools.cpp(16): ../boost/test/unit_test_log.hpp(88): warning #654: overloaded virtual function "boost::unit_test::test_observer::test_unit_skipped" is only partially overridden in class "boost::unit_test::unit_test_log_t" class BOOST_TEST_DECL unit_test_log_t : public test_observer, public singleton<unit_test_log_t> { ^ remark #11074: Inlining inhibited by limit max-size remark #11074: Inlining inhibited by limit max-total-size remark #11076: To get full report use -qopt-report=4 -qopt-report-phase ipo Vicente

1 0

boost_1_59_0 build failures
by Karen Shaeffer 24 Sep '15

24 Sep '15

Hello, I downloaded boost_1_59_0 and built the whole set of libraries. gcc --version gcc (Ubuntu 4.8.4-2ubuntu1~14.04) 4.8.4 ./b2 install warning: No toolsets are configured. warning: Configuring default toolset "gcc". warning: If the default is wrong, your build may not work correctly. warning: Use the "toolset=xxxxx" option to override our guess. warning: For more configuration options, please consult warning: http://boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html Performing configuration checks - 32-bit : no (cached) - 64-bit : yes (cached) - arm : no (cached) - mips1 : no (cached) - power : no (cached) - sparc : no (cached) - x86 : yes (cached) - symlinks supported : yes (cached) - lockfree boost::atomic_flag : yes (cached) - has_icu builds : yes (cached) warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam - zlib : yes (cached) - iconv (libc) : yes (cached) - icu : yes (cached) - compiler-supports-visibility : yes (cached) - compiler-supports-ssse3 : yes (cached) - compiler-supports-avx2 : yes (cached) - gcc visibility : yes (cached) - long double support : yes (cached) warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. - zlib : yes (cached) Component configuration: - atomic : building - chrono : building - container : building - context : building - coroutine : building - coroutine2 : building - date_time : building - exception : building - filesystem : building - graph : building - graph_parallel : building - iostreams : building - locale : building - log : building - math : building - mpi : building - program_options : building - python : building - random : building - regex : building - serialization : building - signals : building - system : building - test : building - thread : building - timer : building - wave : building ...patience... ...patience... ...patience... ...patience... ...patience... ...patience... ...found 34509 targets... ...updating 8 targets... gcc.compile.c++ bin.v2/libs/iostreams/build/gcc-4.8/release/link-static/threading-multi/bzip2.o libs/iostreams/src/bzip2.cpp:20:56: fatal error: bzlib.h: No such file or directory #include "bzlib.h" // Julian Seward's "bzip.h" header. ^ compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -m64 -DBOOST_ALL_NO_LIB=1 -DBOOST_IOSTREAMS_USE_DEPRECATED -DNDEBUG -I"." -c -o "bin.v2/libs/iostreams/build/gcc-4.8/release/link-static/threading-multi/bzip2.o" "libs/iostreams/src/bzip2.cpp" ...failed gcc.compile.c++ bin.v2/libs/iostreams/build/gcc-4.8/release/link-static/threading-multi/bzip2.o... ...skipped <pbin.v2/libs/iostreams/build/gcc-4.8/release/link-static/threading-multi>libboost_iostreams.a(clean) for lack of <pbin.v2/libs/iostreams/build/gcc-4.8/release/link-static/threading-multi>bzip2.o... ...skipped <pbin.v2/libs/iostreams/build/gcc-4.8/release/link-static/threading-multi>libboost_iostreams.a for lack of <pbin.v2/libs/iostreams/build/gcc-4.8/release/link-static/threading-multi>bzip2.o... ...skipped <p/usr/local/lib>libboost_iostreams.a for lack of <pbin.v2/libs/iostreams/build/gcc-4.8/release/link-static/threading-multi>libboost_iostreams.a... gcc.compile.c++ bin.v2/libs/iostreams/build/gcc-4.8/release/threading-multi/bzip2.o libs/iostreams/src/bzip2.cpp:20:56: fatal error: bzlib.h: No such file or directory #include "bzlib.h" // Julian Seward's "bzip.h" header. ^ compilation terminated. "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -m64 -DBOOST_ALL_NO_LIB=1 -DBOOST_IOSTREAMS_DYN_LINK=1 -DBOOST_IOSTREAMS_USE_DEPRECATED -DNDEBUG -I"." -c -o "bin.v2/libs/iostreams/build/gcc-4.8/release/threading-multi/bzip2.o" "libs/iostreams/src/bzip2.cpp" ...failed gcc.compile.c++ bin.v2/libs/iostreams/build/gcc-4.8/release/threading-multi/bzip2.o... ...skipped <pbin.v2/libs/iostreams/build/gcc-4.8/release/threading-multi>libboost_iostreams.so.1.59.0 for lack of <pbin.v2/libs/iostreams/build/gcc-4.8/release/threading-multi>bzip2.o... ...skipped <p/usr/local/lib>libboost_iostreams.so.1.59.0 for lack of <pbin.v2/libs/iostreams/build/gcc-4.8/release/threading-multi>libboost_iostreams.so.1.59.0... ...skipped <p/usr/local/lib>libboost_iostreams.so for lack of <p/usr/local/lib>libboost_iostreams.so.1.59.0... ...failed updating 2 targets... ...skipped 6 targets... Is that expected? thanks, Karen -- Karen Shaeffer Be aware: If you see an obstacle in your path, Neuralscape Services that obstacle is your path. Zen proverb

2 1

Fwd: [sort][container] Challenge for sorting experts, an improved stable sort
by Francisco José Tapia 23 Sep '15

23 Sep '15

Hi Jon, If the elements in the flat associative container are sorted, you need only to sort the elements to insert and after do a fusion of the two parts. If your container admit repeated elements, you can use the std::sort, if not, you must use an stable sort , and delete the repeated. You have several algorithms for to do a stable sort. In the library we are developing (https://github.com/fjtapia/sort_parallel ) you have a smart_merge_sort, which is a very fast stable sort and use only one half of the memory used by the data, is exception safe and use the move semantics I didn't see any implementation of the stable sort algorithms without additional memory, in any library GCC, TBB, IPP … I suppose because they are slow. If you have 100 elements and want to insert 30 elements, need to resize the vector to 130 elements, the last 30 are empty. If you have other vector with the data to insert, you can use smart_merge_sort, and use as auxiliary memory the last 15 elements of the main vector. After sort, delete the repeated elements. And with the two vectors you must do a half_merge fusion , and all is done. With this method you need only the vector for to sort the elements to insert. If you want I can write a small program doing this, using the code of the library.

2 2

[sort][container] Challenge for sorting experts, an improved stable sort
by Ion Gaztañaga 23 Sep '15

23 Sep '15

Hi, I'm trying to improve insertion times for flat associative containers. In range insertions one optimization is to insert the whole range in the end of the container and sort the whole vector instead of trying a loop. An additional optimization proposed in the mailing list is to have an option to create externally the internal vector type of the flat map/set, fill it and then try to move it into the flat container. That requires sorting the moved vector (and removing duplicates if needed). I could try to use std::sort/std::stable_sort but there are some problems: -> Non-portable for C++03 compilers and Boost.Move, and Boost.Container fully supports those platforms. -> Additional O(N) temporary memory for stable sorting. Usually this means a temporary N element array, although there are algorithm to use only N/2 temporary elements. With big containers, this is a lot of memory. So I started analyzing several papers and implementations to see if a custom implementation was possible, but I felt Boost.Sort could be a good place to have that implementation and the Boost community a good place to discuss design alternatives. My initial requirements: 1) Stable sort. A non-stable sort is faster and useful for unique keys containers, but stable sort can be used initially in all flat containers until the non-stable version is implemented. 2) Externally supplied auxiliary memory with optionally no auxiliary memory at all. It seems that there are newer algorithms like Grailsort (https://github.com/Mrrl/GrailSort) or WikiSort (https://github.com/BonzaiThePenguin/WikiSort) that claim O(1) memory, even no auxiliary buffer, and key comparison and data exchanges with complexity O(n*log(n)). However I don't think those implementation correctly handle the basic exception guarantee or non-trivially copyable types. Reason: I want to avoid allocating short-lived temporary memory: if it's available I want to pass the extra capacity that flat containers' internal vector holds for future insertions. 3) Customization points (without ADL, which IMHO is not customizable enough). The sort algorithm should use a SortTraits template parameter for basic operations like "move", "swap", "initialized_move". E.g: template<class T> struct sort_traits { static? void move(T &from, T &to); static? void swap(T &l, T &r); static? void uninitialized_move(T &from, void *to); static? void destroy(T &from, void *to); }; I don't know if this trait should be stateful or not (static members). I could imagine the usefulness of a stateful implementation of sort_traits that could store a reference to an allocator so that some special "construct" version is used in some operations. Or just a version that counts the number of each operation to ease debugging. In any case, a stateless version would be enough for most cases. Reason: In Boost.Container, the idea is to use boost::move + boost::adl_move_swap in the initial implementation, maybe some destructive move implementation in a second iteration if Boost.Move implements it. In any case those operations should be customizable by the user, independently from the type to be sorted. This also avoids unnecessary dependencies in Boost.Sort. -> Dependencies: the implementation should only rely on Boost.Core, Boost.Config, maybe Boost.TypeTraits and no heavy STL dependencies (optionally). Currently Boost.Sort depends on Serialization for BOOST_STATIC_WARNING, but I think this is easily solvable, maybe this static assert utility should go to the core/utility library. Reason: Sort is a low-level algorithm that should avoid pulling unneeded dependencies to other boost libraries. * * * I don't know if other Boost libraries could benefit from this new stable_sort implementation. Maybe it's too special and I should try to write it myself in Boost.Container. I would love to hear comments and suggestions from sort experts, this might be a common need that could enrich the Boost.Sort library. Best, Ion

4 9

[regression] Tests for 'develop' not showing
by Edward Diener 23 Sep '15

23 Sep '15

Trying http://www.boost.org/development/tests/develop/developer/summary.html I get: "Error extracting file: The specified zipfile was not found."

4 4

Re: [boost] Error while building boost
by Roshan 22 Sep '15

22 Sep '15

Hi, This list is specific to the Boost.Compute library. This mail is probably meant for the main Boost mailing list. Forwarding you there. P.S. I'm not sure if the attachment is being forwarded properly, please check. On Tue, Sep 22, 2015 at 12:24 PM, <valnci89(a)gmail.com> wrote: > Hi, > > > I'm trying to install boost on my machine but its not building properly. > Attached is the output generated on running ./b2 install. > > > Commands used: > > ./bootstrap.sh --prefix=/usr/include/boost > > ./b2 install > > > Machine Info: > > OS: RHEL ppc64le > > Boost version: boost_1_59_0 > > > Let me know if any other info is required. > > > Please advice me on this issue. > > > Thanks, > > Valnci > -- Warm regards Roshan

1 0