- Boost - lists.boost.org

Re: [boost] enhanced vector and deque competency test
by Islam Taha 20 Mar '15

20 Mar '15

Thank you very much I have now removed all warnings and it removed the segmentation fault as well. It would be appreciated to give me another feedback on the updated code. thanks in advance

2 1

[1.58] Developchanges not yet merged to master?
by Beman Dawes 20 Mar '15

20 Mar '15

FWIW, I got a private email worrying about unmerged fixes: > This is the list of PR's that have been merged into the develop branch but > have not made it into the 1.58 release candidate: > > https://github.com/boostorg/serialization/pull/9 > https://github.com/boostorg/odeint/pull/7 > https://github.com/boostorg/odeint/pull/6 > https://github.com/boostorg/pool/pull/7 > https://github.com/uBLAS/ublas/pull/26 > https://github.com/boostorg/odeint/pull/9 > https://github.com/boostorg/odeint/pull/8 > https://github.com/boostorg/lexical_cast/pull/10 > https://github.com/boostorg/type_traits/pull/11 > https://github.com/boostorg/type_index/pull/6 I asked the sender to post this sort of message directly to the list, but with 1.58.0 so close it seemed worthwhile to send the list along. --Beman

3 2

Re: [boost] [gsoc15] Removing my proposal due to plagiarism concerns
by Islam Taha 20 Mar '15

20 Mar '15

I’m sorry to fork your README file on your rep. i was just concerned to know how to make bold and somethings you do in your file, there is nothing to do with plagiarism with this, don’t worry about your proposal. Apologizes Islam Taha

1 0

Windows Develop Tests Failing
by Tom Kent 20 Mar '15

20 Mar '15

All my windows test runners for develop (teeks99-08*) have been failing for the last few days (I just noticed). They run for a long while, then end with the following at the end of their results/bjam.log file: common.mkdir D:\local\teeks99-08\d\results\boost\bin.v2\libs\multiprecision\test\number_concept_check_cpp_dec_float_no_et.test\msvc-11.0\debug\address-model-64\architecture-x86\debug-symbols-off\link-static\runtime-link-static if not exist "D:\local\teeks99-08\d\results\boost\bin.v2\libs\multiprecision\test\number_concept_check_cpp_dec_float_no_et.test\msvc-11.0\debug\address-model-64\architecture-x86\debug-symbols-off\link-static\runtime-link-static\\" mkdir "D:\local\teeks99-08\d\results\boost\bin.v2\libs\multiprecision\test\number_concept_check_cpp_dec_float_no_et.test\msvc-11.0\debug\address-model-64\architecture-x86\debug-symbols-off\link-static\runtime-link-static" failed to write output file 'D:\local\teeks99-08\d\results\boost\bin.v2\libs\multiprecision\test\number_concept_check_cpp_dec_float_no_et.test\msvc-11.0\debug\address-model-64\architecture-x86\debug-symbols-off\link-static\runtime-link-static\number_concept_check_cpp_dec_float_no_et.obj.rsp'! At first I thought I might be running out of disk space or something, but that all seems fine. Has anyone seen this before? Tom

12 26

Testing develop fails with b2 errors
by Peter Dimov 20 Mar '15

20 Mar '15

LIke this: C:\Projects\boost-git\boost\libs\core\test>b2 toolset=clang,clang-cxx11,gcc,gcc-cxx11,msvc-8.0,msvc-10.0,msvc-11.0,msvc-12.0 [...] C:/Projects/boost-git/boost/tools/build/src/build\project.jam:262: in find-jamfile from module project error: Unable to load Jamfile. error: Could not find a Jamfile in directory '/C:/Projects/boost-git/boost/libs/context/config'. error: Attempted to find it with pattern '[Bb]uild.jam [Jj]amfile.v2 [Jj]amfile[Jj]amfile.jam'. error: Please consult the documentation at 'http://www.boost.org'. and then this: C:/Projects/boost-git/boost/tools/build/src/build\project.jam:280: in load-jamfile from module project C:/Projects/boost-git/boost/tools/build/src/build\project.jam:64: in project.load from module project C:/Projects/boost-git/boost/libs/log/build\log-architecture.jam:23: in load from module log-architecture C:/Projects/boost-git/boost/tools/build/src/kernel\modules.jam:289: in modules.import from module modules C:/Projects/boost-git/boost/tools/build/src/build\project.jam:1043: in import from module Jamfile<C:\Projects\boost-git\boost\libs\log\build> ..\..\..\libs\log\build\Jamfile.v2:15: in modules.load from module Jamfile<C:\Projects\boost-git\boost\libs\log\build> C:/Projects/boost-git/boost/tools/build/src/build\project.jam:325: in load-jamfile from module project C:/Projects/boost-git/boost/tools/build/src/build\project.jam:64: in load from module project C:/Projects/boost-git/boost/tools/build/src/build\project.jam:89: in load-used-projects from module project C:/Projects/boost-git/boost/tools/build/src/build\project.jam:75: in load from module project C:/Projects/boost-git/boost/tools/build/src/build\project.jam:113: in load-parent from module project C:/Projects/boost-git/boost/tools/build/src/build\project.jam:464: in initialize from module project C:/Projects/boost-git/boost/tools/build/src/build\project.jam:306: in load-jamfile from module project C:/Projects/boost-git/boost/tools/build/src/build\project.jam:64: in load from module project C:/Projects/boost-git/boost/tools/build/src/build\project.jam:113: in load-parent from module project C:/Projects/boost-git/boost/tools/build/src/build\project.jam:464: in initialize from module project C:/Projects/boost-git/boost/tools/build/src/build\project.jam:306: in load-jamfile from module project C:/Projects/boost-git/boost/tools/build/src/build\project.jam:64: in load from module project C:/Projects/boost-git/boost/tools/build/src/build\project.jam:145: in project.find from module project C:/Projects/boost-git/boost/tools/build/src\build-system.jam:535: in load from module build-system C:\Projects\boost-git\boost\tools\build\src/kernel\modules.jam:289: in import from module modules C:\Projects\boost-git\boost\tools\build\src/kernel/bootstrap.jam:139: in boost-build from module C:\Projects\boost-git\boost\boost-build.jam:17: in module scope from module

5 7

To split, or not to split, or something else? RE: type_traits rewrite, modularization, dependencies, etc.
by Rene Rivera 20 Mar '15

20 Mar '15

I keep reading emails about the effort to reduce dependencies, and to split libraries into core/simple + whole/big.. And I keep thinking it's making things more complex than they need to be. I can see the need to compartmentalize the parts of a library that have minimal to little dependencies. So here's a suggestions for structure of managing this. I see options: 1. In each library allow for a "core" set of headers that are still in a core subdir. But that we can tell is a subset of the library that has the minimal dependencies. For example we would have: * libs/<lib>/include/boost/<lib>/core/.. * libs/<lib>/include/boost/<lib>/<the-rest>.. This of course assumes that it's headers only that would be core. Second option is to have each library have to explicit sublibs/parts. "core" and "full". Structure would be: * libs/<lib>/core/(build, doc, include, meta, test) * libs/<lib>/full/(build, doc, include, meta, test) Note, both core and full would be in the same git repo to make life easier for library authors and users that visit a library git repo on github. As it's only one place for everything for that one library. As a user, release manager, testing manager, and library author this would be easy to understand and manage than the current "some random set of libraries have core or not and in different places". -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

6 11

[1.58.0] Request permission to merge smart_ptr:94824c8 into master
by Peter Dimov 20 Mar '15

20 Mar '15

This https://github.com/boostorg/smart_ptr/commit/94824c807f76dc4f3d41109a75808e… fixes a problem on QNX/Blackberry by adding std:: to ptrdiff_t, in a place where size_t is already similarly qualified, so it should be very low risk. Tested locally on g++ 4.8.3, clang-3.4.2, msvc-8.0, msvc-10.0, msvc-11.0, msvc-12.0.

2 1

[metaparse] Review Manager
by Christophe Henry 20 Mar '15

20 Mar '15

Dear Review Wizards, I would like to volunteer to be Review Manager for the metaparse library, in agreement with Abel. We would like to suggest May 25 to June 07 for the review. If there are no objections, please sign me up. Regards, Christophe

8 13

[afio][v1.30 "C++ Now edition" released]
by Niall Douglas 20 Mar '15

20 Mar '15

Dear Boost, I am very pleased to announce the v1.30 release of proposed Boost AFIO, a Boost library implementing asynchronous file input/output which has been in the review queue since 2013. This is the version of AFIO which will be overviewed in my talk at C++ Now 2015. It also demonstrates the validity of the clang AST driven BindLib standalone Boost library conversion technique which will also be overviewed at C++ Now. Source distro: https://github.com/BoostGSoC13/boost.afio/archive/v1.30_Boost_v1.57.zi p Docs and CI dashboard: https://boostgsoc13.github.io/boost.afio/ Major new features in the v1.30 release: * Performance was improved by removing the transactional memory support in the v1.2 engine which is now compile time enabled only. Throughput now reaches up to 85% of raw ASIO and average latencies were reduced by 48%, yielding a 15 microsecond average latency with +/- 0.15 microsecond at a 95% confidence interval. This should enable AFIO to handle the latest generation PCIe SSDs with their 80 microsecond latencies reasonably well. * AFIO is now capable of complete standalone usage no Boost dependencies whatsoever, including for its unit testing via a Boost.Test emulation. * Due to its use of libclang AST generated template aliasing to allow user swapping of STL 11 implementation, minimum compilers required are now VS2013, GCC 4.7 and clang 3.2. All the VS2010 workarounds baggage has been eradicated. * All things related to async_data_op_req are now fully metaprogrammed with automatic generation by the compiler of suitable ASIO scatter-gather buffers from input types and STL containers with correct scatter-gather buffer coalescing where safe to do so. This automatic generation is user customisable via free function specialisation. * Support for relative paths from an open file descriptor was added. This lets you specify a file descriptor as a base from which a path fragment operates with the path resolution atomically performed in the kernel, and therefore the path of the base file descriptor may rapidly change safely. * AFIO is now optimally filing system race condition safe on all supported platforms, with per-API documentation of how much race safety is guaranteed per platform. A soak unit test verifies per commit that perfect race safety under severe and rapid filing system change is maintained. * A new afio::path type which very thinly wraps filesystem::path was added. The new afio specific path type makes the management of NT kernel path to Win32 path transition and conversion explicit, and therefore much harder to accidentally get wrong. A new normalise_path() function can convert a NT kernel path to a traditional Win32 path, complete with drive letter. * New platforms supported: Apple OS X and Android 5.0. * New filing system features support: All platforms: sparse file support, storage extent enumeration, extent deallocation ("hole punching"), volume metadata fetching (statfs), open file handle path discovery, hard link support, atomic relink (rename) support. Windows only: file symlinking, NT lock file performance flags (lock file performance is now not far from POSIX), workaround semantics for all the ways Windows will surprise you on the filing system such as files and directories which won't delete. AFIO now does a fair job of replicating POSIX filing system semantics on Windows (and better than Mingw/Cygwin presently). Linux: symlinks are now opened as file descriptors on kernels supporting that feature. * Doubled the size of the tutorial, with all the new material being non-toy examples. There is a particularly nifty "File locking via only atomic appending and hole punching" algorithm implementation in there, and it holds up surprisingly well compared to traditional file locks except on ZFS. Plus, it's completely portable. * Some utility routines in preparation for AFIO v1.4: a cryptographically strong random filename generator, a hugepage TLB STL allocator useful for efficient file copy buffers, a very highly optimised C++ 14 constexpr constructing arbitrary Hamming code SECDED template class (an amazing 22 cycles per byte for the 32784,32768 code), and secure to-hex and from-hex validating converters. * No shortage of bug fixes, helped hugely by additional unit testing for correct error handling. Detailed changelog can be found at https://boostgsoc13.github.io/boost.afio/doc/html/afio/release_notes.h tml. I'll tag a Boost 1.58 release on github once Boost 1.58 is out. This release took far longer than I originally intended mainly due to the extensive debugging of weird filing system races, and for six weeks now I've been working till 5am every night after my day job. I cannot tell you how glad I am to see this release out! My enormous thanks to my family who have put up with a lot for this release, and to my employer for a fairly dopey employee recently. Bed, here I come! Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

3 6

enhanced vector and deque competency test
by Islam Taha 19 Mar '15

19 Mar '15

Hi, I am Islam Taha i’m interested in the idea of enhanced vector and deck and i’ve implemented the simple vector-like container, it would be pleasurable to review and give me your feedback on my implementation. that’s the link ( https://github.com/islam-taha/stdVector/blob/master/vector.cpp <https://github.com/islam-taha/stdVector/blob/master/vector.cpp> ). Thanks in advance.

2 1