- Boost - lists.preview.boost.org

[utility][enable_if] Documentation issue
by Agustín K-ballo Bergé 25 Oct '13

25 Oct '13

The documentation for `enable_if` has a duplicated anchor for sections 3.1 and 3.2, making it impossible to link to section 3.2 directly. See http://www.boost.org/libs/utility/enable_if.html#htoc7 This issue is still present in trunk. Could this be fixed? I could provide a patch but I do not see a .qbk file for it, should the html be modified directly? Regards, -- Agustín K-ballo Bergé.- http://talesofcpp.fusionfenix.com

2 2

[Type_Traits] [remove_bounds]: Wrong workaround for IBM C++ compiler is applied in remove_bounds.hpp
by Kilian Kilger 24 Oct '13

24 Oct '13

Hi, in remove_bounds.hpp, a wrong workaround for the IBM C++ compiler is applied. This workaround is only valid for IBM C++ on AIX, but wrong for IBM C++ on z/OS. The z/OS compiler has no bug and thus no workaround must be applied (else we get wrong results). So instead of testing against __IBMCPP__ one should also test against __MVS__. This last macro is only defined for IBM C++ on z/OS. I wanted to open a ticket on trac, but this system did always identify my posting as spam. Best regards, Kilian.

4 11

[1.55 beta][serialization] VS2013 boost/archive/iterators/transform_width.hpp(151) : error C2039: 'min'
by Jeff Flinn 24 Oct '13

24 Oct '13

This is ticket #9279/#8750. Just checking that this gets into the release. Is that the case? Thanks, Jeff

1 0

[functors] proposal
by Piotr Wygocki 24 Oct '13

24 Oct '13

Hi, I've developed a small set of functors and functor adaptors. Although this code is very simple it might be very useful for some subset of the community. Do you think it might become a part of the boost library? If not I'm still very interested in any feedback. I think it's not big enough to be a separate library. To my knowledge of boost it fits in the utility lib. The code can be found here: https://github.com/wygos/functors List of utilities: SkipFunctor takes any number of arguments; does completely nothing ReturnSomethingFunctor<T,t> takes any number of arguments; returns t; IdentityFunctor takes one parameter and returns it. ReturnFalseFunctor takes any number of arguments; returns false; ReturnTrueFunctor takes any number of arguments; returns true; ReturnZeroFunctor takes any number of arguments; returns 0; AssertFunctor takes any number of arguments; asserts; ArrayToFunctor<Array> Stores an object which provides operator[]. Provides operator()(). A set of non-template comparison functors (only operator() is templated): * Greater * Less * GreaterEqual * LessEqual * EqualTo * NotEqualTo FunctorToComparator<Functor, Compare> This comparator takes a functor "f" and a comparator "c". For elements (x,y) it returns c(f(x), f(y)) c is Less by default FunctorToOutputIterator<Functor> The output iterator stores a functor and each time the operator= is called the given functor is called Logical operators as functors: * Not * Or * And * Xor LiftBinaryOperatorFunctor<Operator, FunctorLeft, FunctorRight> Functor stores a binary operator "o" and two functors "f" and "g". For given arguments args returns o(f(args), g(args)). Boolean functor adapters. Each of them stores a boolean functor and performs an appropriate logical operation in the operator(). * NotFunctor<Functor> * OrFunctor<FunctorLeft, FunctorRight> * AndFunctor<FunctorLeft, FunctorRight> * XorFunctor<FunctorLeft, FunctorRight> Regards, Piotr

5 12

[boost-testing] something broke my tester(lazypiranha)
by Michael Mathews 24 Oct '13

24 Oct '13

Hi Folks, starting with last nights run my tester has been failing with : File "/home/michael/boost_testing/tools_regression_src/regression.py", line 329, in command_test self.command_test_boost_build() File "/home/michael/boost_testing/tools_regression_src/regression.py", line 369, in command_test_boost_build "boost/bin.v2/libs/any/test/any_test.test")); OSError: [Errno 2] No such file or directory: '/home/michael/boost_testing/results/boost/bin.v2/libs/any/test/any_test.test' Is there an easy an easy way for me to determine the missing test? thanks michael

1 0

NT2 and Boost.SIMD beta 2 available
by Joel Falcou 23 Oct '13

23 Oct '13

This following releases updates NT2 and Boost.SIMD libraries.10 months had past and 176 Issues have been closed since last beta release and more than 2000 commits have been issued. Boost.SIMD is heading toward API stability. We want to tackle ons ome more compile time issues before going for an actual Boost Review. Special thanks to Tim Blenchmann and Domagoj Saric for their help and suggestions throughout this development. The release Changelog is here : https://github.com/MetaScale/nt2/releases The files can be download from : http://nt2.metascale.org/downloads/ The Documentation (in progress) is here : http://nt2.metascale.org/doc/html/index.html

4 4

[1.55][Math] Are we still open to patches?
by John Maddock 23 Oct '13

23 Oct '13

Are we still open for patches for 1.55? If so I'd like to merge the patch for the issue raised here: http://boost.2283326.n4.nabble.com/Boost-1-54-0-boost-math-sph-bessel-n-x-c… now that the tests on Trunk have cycled. Thanks, John.

2 1

[website] Redirection to latest documentation
by Laurent Dupuy 23 Oct '13

23 Oct '13

Hello all, Would it be possible for the webmaster(s) to add a redirection (a symbolic link or whatever) to the latest documentation? Until recently, the URL http://www.boost.org/doc/libs/ did the job, but it does not anymore. Thanks! -- Laurent Dupuy.

2 1

Boost.Build commit heads up
by Beman Dawes 23 Oct '13

23 Oct '13

Here is the commit message for revision 86392: Add Boost.Build support for the Git modular layout, using links to to new header locations, thus preventing breakage to vast amounts of user code and build setups. Being added to SVN so that changes will automatically propagate to Git and modular Boost. Thanks to Steven Watanabe, Jürgen Hunold, Vladimir Prus, and Bjørn Roald for developing this patch. Steven in particular conceived the approach and did the initial implementation, which was further refined by the other contributors. In theory this commit won't break any existing boost builds. To verify that, on Win 7 and Ubunto I've done a fresh SVN checkout of trunk and verified bootstrap.bat, bootstrap.sh, and a b2 build work both before and after the patch is applied. On Windows, I verified that after the patch is applied a b2 build using an unpatched prior compilation of b2 still works. These tests increase confidence that committing the patch to trunk now isn't likely to cause breakage, but please post to this list right away if you spot any build breakage or other odd behavior. The files modified are listed below. Thanks, --Beman Modified: D:\boost\trunk\Jamroot Modified: D:\boost\trunk\libs\geometry\index\example\Jamfile.v2 Modified: D:\boost\trunk\libs\numeric\odeint\examples\vexcl\Jamfile.v2 Modified: D:\boost\trunk\libs\parameter\doc\html\index.html Modified: D:\boost\trunk\libs\parameter\doc\index.rst Modified: D:\boost\trunk\libs\python\example\Jamroot Modified: D:\boost\trunk\libs\python\example\quickstart\Jamroot Modified: D:\boost\trunk\libs\python\example\tutorial\Jamroot Modified: D:\boost\trunk\libs\signals2\example\Jamfile.v2 Modified: D:\boost\trunk\libs\spirit\example\qi\json\build\Jamfile Modified: D:\boost\trunk\libs\units\test\Jamfile.v2 Modified: D:\boost\trunk\tools\Jamfile.v2 Modified: D:\boost\trunk\tools\regression\build\Jamroot.jam

5 6

Re: [boost] [git help] Documenting common modular boost workflows
by Daryle Walker 23 Oct '13

23 Oct '13

Since a project that’s made of a bunch of sub-repositories that’s later merged is (AFAIK) unusual, I don’t think the writer of gitflow had it in mind. I’m guessing that each sub-repository independently uses gitflow. When it’s shipping time, the release-merge script grabs from the “master” branch of each sub-repository. Of course, this doesn’t cover multiple libraries that have to work together or what happens when fixing is necessary (probably due to cross-library problems). And do the test runners work off “develop,” “master,” “release,” or does it shift depending where we are in the release cycle? Sent from Windows Mail From: Peter Dimov Sent: ‎Monday‎, ‎October‎ ‎21‎, ‎2013 ‎10‎:‎16‎ ‎AM To: Boost Dev-List Dave Abrahams wrote: > IIUC we already agreed long ago to use gitflow: It's not entirely clear to me what using gitflow would mean in the context of a Boost superproject with per-library submodules. Who is "we" who would be using gitflow, the Boost release managers or the library maintainers? When Boost release 1.64.0 is started, who is going to create the gitflow release branch, and from what? _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

4 4