- Boost - lists.boost.org

[config] including typeinfo in dinkumware.hpp when RTTI is disabled
by Edward Diener 01 Nov '13

01 Nov '13

Evidently the only way to currently compile clang on Windows using the VC++ RTL is to compile without RTTI and exception handling in its VC++ emulation ( options -D_HAS_EXCEPTIONS=0 /GR- ). This may be totally unrealistic for Boost. Nonetheless with these compiler options, when the dinkumware.hpp is being used by Boost config, it is including typeinfo and this is causing a problem: c:\Program Files\Microsoft Visual Studio 10.0\VC\INCLUDE\typeinfo(156,10) : error: unknown class name 'exception'; did you mean '_exception'? : public exception Is it realistic in dinkumware.hpp to not include typeinfo if RTTI is not enabled ? Or is it just more realistic to say that compiling Boost libraries with RTTI disabled is not going to work ?

4 9

[git help] Cloning the boost git repository recursively seems to have issues.
by Cox, Michael 01 Nov '13

01 Nov '13

On Wed, Oct 30, 2013 at 11:16 PM, <boost-request(a)lists.boost.org> wrote: > Date: Wed, 30 Oct 2013 23:31:25 +0100 > From: Daniel Pfeifer <daniel(a)pfeifer-mail.de> > To: Boost Developers List <boost(a)lists.boost.org> > Cc: Mike <mhcox(a)bluezoosoftware.com> > Subject: [boost] [git help] Cloning the boost git repository > recursively seems to have issues. > Message-ID: > <CANZMcXrkLdL7-ax9CUnaySwJB4-=fSt3n627n3bdj_LF0Yp-KA(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Hi Mike, > > Thanks for reporting that issue. > Migration if Boost to modularized Git has been decoupled from Ryppl. > I forward your message to the Boost Developers List. > > -- Daniel > > ---------- Forwarded message ---------- > From: Mike <mhcox(a)bluezoosoftware.com> > Date: 2013/10/29 > Subject: [ryppl-dev] Cloning the boost git repository recursively > seems to have issues. > To: ryppl-dev(a)googlegroups.com > > > I ran the following git command to retrieve the latest modularized > boost code in github.com/boostorg: > > $ git clone --recursive https://github.com/boostorg/boost > > The boost repository and all its submodules were recursively cloned as > expected, but bootstrap.bat in the boost repository and some library > submodules were marked as modified. Not what I expected. I ran the > following command to get a list of the modified files in the > submodules: > $ git submodule foreach --recursive 'git status --short' > > I got the following output: > Entering 'libs/accumulators' > Entering 'libs/algorithm' > Entering 'libs/any' > ... > Entering 'libs/geometry' > M example/ml02_distance_strategy.cpp > Entering 'libs/gil' > ... > Entering 'libs/interprocess' > M proj/vc7ide/doc_managed_grow.vcproj > M proj/vc7ide/managed_shared_memory.vcproj > M proj/vc7ide/offset_ptr_test.vcproj > Entering 'libs/intrusive' > M proj/vc7ide/avl_multiset/avl_multiset.vcproj > M proj/vc7ide/avl_set/avl_set.vcproj > M proj/vc7ide/sg_multiset/sg_multiset.vcproj > M proj/vc7ide/sg_set/sg_set.vcproj > M proj/vc7ide/splay_multiset/splay_multiset.vcproj > M proj/vc7ide/splay_set/splay_set.vcproj > Entering 'libs/io' > ... > Entering 'libs/math' > M doc/equations/gamm1.svg > M doc/equations/gamm2.svg > M doc/equations/gamm3.svg > M doc/equations/gamm4.svg > M doc/equations/gamm5.svg > M doc/equations/gamma_dist_ref1.svg > M doc/equations/gamma_dist_ref2.svg > M doc/equations/gamma_ratio0.svg > M doc/equations/gamma_ratio1.svg > M doc/equations/hankel1.svg > M doc/equations/hankel2.svg > M doc/equations/hankel3.svg > M doc/equations/hankel4.svg > M doc/equations/hankel5.svg > M doc/equations/hazard.svg > M doc/equations/hermite_0.svg > M doc/equations/hermite_1.svg > M doc/equations/hypergeometric1.svg > M doc/equations/hypergeometric2.svg > M doc/equations/hypergeometric3.svg > M doc/equations/hypergeometric4.svg > M doc/equations/hypergeometric5.svg > M doc/equations/hypergeometric6.svg > M doc/equations/hypot.svg > M doc/equations/hypot2.svg > M doc/equations/ibeta1.svg > M doc/equations/ibeta10.svg > M doc/equations/ibeta11.svg > M doc/equations/ibeta12.svg > M doc/equations/ibeta2.svg > M doc/equations/ibeta3.svg > M doc/equations/ibeta4.svg > M doc/equations/ibeta5.svg > M doc/equations/ibeta6.svg > M doc/equations/ibeta7.svg > M doc/equations/ibeta8.svg > M doc/equations/ibeta9.svg > M doc/equations/ibeta_inv1.svg > M doc/equations/ibeta_inv2.svg > M doc/equations/ibeta_inv3.svg > M doc/equations/ibeta_inv4.svg > M doc/equations/ibeta_inv5.svg > M doc/equations/ibeta_inv6.svg > M doc/equations/ibeta_inv7.svg > M doc/equations/ibeta_inv8.svg > M doc/equations/igamma1.svg > M doc/equations/igamma10.svg > M doc/equations/igamma11.svg > M doc/equations/igamma11b.svg > M doc/equations/igamma12.svg > M doc/equations/igamma13.svg > M doc/equations/igamma16.svg > M doc/equations/igamma17.svg > M doc/equations/igamma18.svg > M doc/equations/igamma19.svg > M doc/equations/igamma1f.svg > M doc/equations/igamma2.svg > M doc/equations/igamma2f.svg > M doc/equations/igamma3.svg > M doc/equations/igamma4.svg > M doc/equations/igamma5.svg > M doc/equations/igamma6.svg > M doc/equations/igamma7.svg > M doc/equations/igamma8.svg > M doc/equations/igamma9.svg > M doc/equations/jacobi1.svg > M doc/equations/jacobi2.svg > M doc/equations/jacobi3.svg > M doc/equations/jacobi4.svg > M doc/equations/laguerre_0.svg > M doc/equations/laguerre_1.svg > M doc/equations/laguerre_2.svg > M doc/equations/laguerre_3.svg > M doc/equations/lanczos0.svg > M doc/equations/lanczos0a.svg > M doc/equations/lanczos0b.svg > M doc/equations/lanczos1.svg > M doc/equations/lanczos2.svg > M doc/equations/lanczos3.svg > M doc/equations/lanczos4.svg > M doc/equations/lanczos5.svg > M doc/equations/lanczos6.svg > M doc/equations/lanczos7.svg > M doc/equations/laplace_pdf.svg > M doc/equations/legendre_0.svg > M doc/equations/legendre_1.svg > M doc/equations/legendre_1b.svg > M doc/equations/legendre_2.svg > M doc/equations/legendre_3.svg > M doc/equations/legendre_4.svg > M doc/equations/legendre_5.svg > M doc/equations/lgamm1.svg > M doc/equations/lgamm2.svg > M doc/equations/lgamm3.svg > M doc/equations/lgamm4.svg > M doc/equations/lgamm5.svg > M doc/equations/lgamm6.svg > M doc/equations/log1pseries.svg > M doc/equations/lognormal_ref.svg > M doc/equations/mbessel1.svg > M doc/equations/mbessel10.svg > M doc/equations/mbessel11.svg > M doc/equations/mbessel12.svg > M doc/equations/mbessel13.svg > M doc/equations/mbessel14.svg > M doc/equations/mbessel15.svg > M doc/equations/mbessel16.svg > M doc/equations/mbessel17.svg > M doc/equations/mbessel2.svg > M doc/equations/mbessel3.svg > M doc/equations/mbessel4.svg > M doc/equations/mbessel5.svg > M doc/equations/mbessel6.svg > M doc/equations/mbessel7.svg > M doc/equations/mbessel8.svg > M doc/equations/mbessel9.svg > M doc/equations/nc_beta_ref1.svg > M doc/equations/nc_beta_ref2.svg > M doc/equations/nc_beta_ref3.svg > M doc/equations/nc_beta_ref4.svg > M doc/equations/nc_chi_squ_ref1.svg > M doc/equations/nc_chi_squ_ref2.svg > M doc/equations/nc_chi_squ_ref3.svg > M doc/equations/nc_chi_squ_ref4.svg > M doc/equations/nc_chi_squ_ref5.svg > M doc/equations/nc_chi_squ_ref6.svg > M doc/equations/nc_chi_squ_ref7.svg > M doc/equations/nc_f_ref1.svg > M doc/equations/nc_f_ref2.svg > M doc/equations/nc_t_ref1.svg > M doc/equations/nc_t_ref2.svg > M doc/equations/nc_t_ref3.svg > M doc/equations/nc_t_ref4.svg > M doc/equations/nc_t_ref5.svg > M doc/equations/neg_binomial_ref.svg > M doc/equations/normal_ref1.svg > M doc/equations/poisson_ref1.svg > M doc/equations/roots1.svg > M doc/equations/roots2.svg > M doc/equations/roots3.svg > M doc/equations/roots4.svg > M doc/equations/sbessel1.svg > M doc/equations/sbessel2.svg > M doc/equations/sbessel3.svg > M doc/equations/sbessel4.svg > M doc/equations/sbessel5.svg > M doc/equations/special_functions_blurb1.svg > M doc/equations/special_functions_blurb15.svg > M doc/equations/special_functions_blurb17.svg > M doc/equations/special_functions_blurb18.svg > M doc/equations/special_functions_blurb20.svg > M doc/equations/special_functions_blurb22.svg > M doc/equations/special_functions_blurb5.svg > M doc/equations/special_functions_blurb6.svg > M doc/equations/special_functions_blurb7.svg > M doc/equations/spherical_0.svg > M doc/equations/spherical_1.svg > M doc/equations/spherical_2.svg > M doc/equations/spherical_3.svg > M doc/equations/students_t_dist.svg > M doc/equations/students_t_ref1.svg > M doc/equations/zeta1.svg > M doc/equations/zeta2.svg > M doc/equations/zeta3.svg > M doc/equations/zeta4.svg > M doc/equations/zeta5.svg > M doc/equations/zeta6.svg > M doc/graphs/acosh.svg > M doc/graphs/airy_ai.svg > M doc/graphs/airy_aip.svg > M doc/graphs/airy_bi.svg > M doc/graphs/airy_bip.svg > M doc/graphs/asinh.svg > M doc/graphs/atanh.svg > M doc/graphs/bernoulli_cdf.svg > M doc/graphs/bernoulli_pdf.svg > M doc/graphs/beta.svg > M doc/graphs/beta_pdf.svg > M doc/graphs/binomial_pdf_1.svg > M doc/graphs/binomial_pdf_2.svg > M doc/graphs/cauchy_pdf1.svg > M doc/graphs/cauchy_pdf2.svg > M doc/graphs/cbrt.svg > M doc/graphs/chi_squared_pdf.svg > M doc/graphs/cyl_bessel_i.svg > M doc/graphs/cyl_bessel_j.svg > M doc/graphs/cyl_bessel_k.svg > M doc/graphs/cyl_neumann.svg > M doc/graphs/digamma.svg > M doc/graphs/ellint_1.svg > M doc/graphs/ellint_2.svg > M doc/graphs/ellint_3.svg > M doc/graphs/ellint_carlson.svg > M doc/graphs/erf.svg > M doc/graphs/erf_inv.svg > M doc/graphs/erfc.svg > M doc/graphs/erfc_inv.svg > M doc/graphs/expint2.svg > M doc/graphs/expint_i.svg > M doc/graphs/expm1.svg > M doc/graphs/exponential_pdf.svg > M doc/graphs/extreme_value_pdf1.svg > M doc/graphs/extreme_value_pdf2.svg > M doc/graphs/fisher_f_pdf.svg > M doc/graphs/gamma1_pdf.svg > M doc/graphs/gamma2_pdf.svg > M doc/graphs/gamma_p.svg > M doc/graphs/gamma_q.svg > M doc/graphs/hermite.svg > M doc/graphs/hypergeometric_pdf_1.svg > M doc/graphs/hypergeometric_pdf_2.svg > M doc/graphs/ibeta.svg > M doc/graphs/jacobi_cd.svg > M doc/graphs/jacobi_cn.svg > M doc/graphs/jacobi_cs.svg > M doc/graphs/jacobi_dc.svg > M doc/graphs/jacobi_dn.svg > M doc/graphs/jacobi_ds.svg > M doc/graphs/jacobi_nc.svg > M doc/graphs/jacobi_nd.svg > M doc/graphs/jacobi_ns.svg > M doc/graphs/jacobi_sc.svg > M doc/graphs/jacobi_sd.svg > M doc/graphs/jacobi_sn.svg > M doc/graphs/laguerre.svg > M doc/graphs/laplace_pdf.svg > M doc/graphs/legendre_p.svg > M doc/graphs/legendre_q.svg > M doc/graphs/lgamma.svg > M doc/graphs/log1p.svg > M doc/graphs/logistic_pdf.svg > M doc/graphs/lognormal_pdf1.svg > M doc/graphs/lognormal_pdf2.svg > M doc/graphs/nc_beta_pdf.svg > M doc/graphs/nc_f_pdf.svg > M doc/graphs/nc_t_pdf.svg > M doc/graphs/nccs_pdf.svg > M doc/graphs/negative_binomial_pdf_1.svg > M doc/graphs/negative_binomial_pdf_2.svg > M doc/graphs/normal_pdf.svg > M doc/graphs/pareto_pdf1.svg > M doc/graphs/pareto_pdf2.svg > M doc/graphs/poisson_pdf_1.svg > M doc/graphs/powm1.svg > M doc/graphs/rayleigh_cdf.svg > M doc/graphs/rayleigh_pdf.svg > M doc/graphs/sinc_pi.svg > M doc/graphs/sinhc_pi.svg > M doc/graphs/sph_bessel.svg > M doc/graphs/sph_neumann.svg > M doc/graphs/sqrt1pm1.svg > M doc/graphs/students_t_pdf.svg > M doc/graphs/tgamma.svg > M doc/graphs/tgamma_delta_ratio.svg > M doc/graphs/triangular_cdf.svg > M doc/graphs/triangular_pdf.svg > M doc/graphs/uniform_cdf.svg > M doc/graphs/uniform_pdf.svg > M doc/graphs/weibull_pdf1.svg > M doc/graphs/weibull_pdf2.svg > M doc/graphs/zeta1.svg > M doc/graphs/zeta2.svg > Entering 'libs/move' > ... > Entering 'libs/multiprecision' > M doc/floating_point_eg1.svg > M doc/floating_point_eg2.svg > M doc/floating_point_eg3.svg > Entering 'libs/numeric/conversion' > ... > Entering 'libs/pool' > M doc/images/mb1.svg > M doc/images/mb2.svg > M doc/images/mb3.svg > M doc/images/mb4.svg > M doc/images/pc1.svg > M doc/images/pc2.svg > M doc/images/pc3.svg > M doc/images/pc4.svg > M doc/images/pc5.svg > Entering 'libs/predef' > ... > Entering 'tools/inspect' > Entering 'tools/litre' > Entering 'tools/quickbook' > > All the "modified" files appear to be .bat, .vcproj, and .svg files > (although there was one file, example/ml02_distance_strategy.cpp in > libs/geometry). I thought it might be a problem with .gitattributes > files. When I looked at them, I noticed an unfamiliar attribute, > svneol=native. I expected to find eol=crlf for the .bat and .vcproj > files. I don't have autocrlf or safecrlf set in my ~.gitconfig file > (should I?). What is the svneol attribute? What am I missing? > > -- Some more info that I should have included: - Fedora 20 - git version 1.8.3.1 Mike

3 5

[1.55.0] Release candidates available
by Marshall Clow 01 Nov '13

01 Nov '13

Release candidate files for 1.55.0 are available at http://boost.cowic.de/rc/ As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. This helps ensure the candidates build OK before we push them out to SourceForge. The files (and associated md5s) are: ba1ae723b8b4d1edeca684bb14b3213b *boost_1_55_0_rc1.tar.gz 66e01be2f328c556835c42be7b6d17d5 *boost_1_55_0_rc1.tar.bz2 925bb6c96082033687e5742b4e77af7b *boost_1_55_0_rc1.zip 830d61075ecf7d5ebf7c0843033393bf *boost_1_55_0_rc1.7z Thanks! -- The release managers

8 9

[Serialization] - [1.55] vs2013 compiler error - tickets #9279/#8750
by Jeff Flinn 01 Nov '13

01 Nov '13

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

1 0

Re: [boost] [git help] GitHub boostorg library authentication
by Cox, Michael 31 Oct '13

31 Oct '13

On Wed, Oct 30, 2013 at 12:00 AM, <boost-request(a)lists.boost.org> wrote: > > Date: Tue, 29 Oct 2013 21:03:01 -0700 > From: Dave Abrahams <dave(a)boostpro.com> > To: boost(a)lists.boost.org > Subject: Re: [boost] [git help] GitHub boostorg library authentication > Message-ID: <m27gcv76dm.fsf(a)papi.luannocracy.com> > Content-Type: text/plain > > Daniel Pfeifer <daniel(a)pfeifer-mail.de> writes: > > > 2013/10/29 Daniel James <daniel(a)calamity.org.uk>: > >> On 29 October 2013 04:36, Dave Abrahams <dave(a)boostpro.com> wrote: > >>> > >>>> The super-project can't use github's git urls as they don't > >>>> allow anonymous access. I believe the super-project should be using > >>>> https for submodules, rather than http. > >>> > >>> Why is that? Because it's possible to commit through https? > >> > >> Yes. > >> > >>> But won't someone complain that they can't access https behind their > >>> corporate firewall? It always seems like there's no right answer in > >>> this territory. > >> > >> Oh right, I hadn't thought of that. Making it easy to check out > >> probably should be the priority. > > > > I am behind a corporate firewall and I cannot access git repositories > > through ssh. > > https works in both directions (pull and push). > > Yes, different corporate firewalls block different protocols. But I'm > happy to change to https if everyone believes that will work better > overall. In the .gitmodules file you can use relative urls, e.g. [submodule "smart_ptr"] path = libs/smart_ptr url = ../smart_ptr # url = http://github.com/boostorg/smart_ptr.git fetchRecurseSubmodules = on-demand The protocol used to access the super-project boost is what will be used to retrieve the submodule projects. This might help with issues accessing the repositories, although the super-project will have to accessed via http/https (or whatever ports are open through the firewall). This also makes the whole repository structure relocatable, e.g. a development team using boost can clone all the repositories to their local development server without having to modify the .gitmodules file in the boost super-project. Unfortunately, there's no good way I'm aware of to clone all the repositories as bare repositories. Maybe the latest changes in how git submodules are stored (i.e. under .git/modules) will help. Michael

2 1

Fwd: [Boost-users] [test] floating point comparison
by Matthijs Möhlmann 31 Oct '13

31 Oct '13

Hello all, I already posted this to the boost users list, because I thought it was a problem in my code, but I think its a bug in boost test (unit tests) Versions: Boost: 1.54 GCC: 4.8.1 Does someone have an answer to this? -------- Original Message -------- Subject: [Boost-users] [test] floating point comparison Date: Wed, 30 Oct 2013 14:40:07 +0100 From: Matthijs Möhlmann <matthijs(a)cacholong.nl> Reply-To: boost-users(a)lists.boost.org To: boost-users(a)lists.boost.org Hello all, I've the following test program: #define BOOST_TEST_DYN_LINK #define BOOST_TEST_MAIN #define BOOST_TEST_MODULE Master test suite #include <boost/test/unit_test.hpp> BOOST_AUTO_TEST_CASE(TestCase) { BOOST_REQUIRE_CLOSE_FRACTION(45.00f, 45.17f, 0.004f); } When I compile it with the following line: g++ -o main.o -c -Werror -Wall -std=c++11 -fvisibility=hidden -fvisibility-inlines-hidden -DBOOST_SPIRIT_USE_PHOENIX_V3 -DUTEST -g main.cpp g++ -o main main.o -lboost_unit_test_framework I get the following output: Running 1 test case... *** No errors detected If I lower the tolerance to 0.0004f then I'll get the following: Running 1 test case... main.cpp(8): fatal error in "TestCase": difference{0.00376352} between 45.00f{45} and 45.17f{45.1699982} exceeds 0.00039999999 *** 1 failure detected in test suite "Master test suite" Why does it say that the difference is 0.00376352 and not 0.17....... ? Regards, Matthijs Möhlmann _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

3 2

[MPL] RFC: An MPL macro to define a has_member_xxx<T> predicate
by Erik Erlandson 31 Oct '13

31 Oct '13

If there's already a boost solution for this, then I have egg on my face, but I can't find one: I'd like an MPL macro that defines a predicate template which inherits from boost::true_type iff the given type defines *any* member with a particular name (false_type otherwise), and which does not assume the member name exists, like this: struct my_class { // foo might be member data, member function, a typedef, etc: int foo; }; CREATE_MEMBER_CHECK(foo); CREATE_MEMBER_CHECK(bar); has_member_foo<my_class> t1; // this inherits from true_type has_member_bar<my_class> t2; // this inherits from false_type I wrote an implementation of the above, and example, here: https://gist.github.com/erikerlandson/7251015 The macro BOOST_MPL_HAS_XXX_TRAIT_DEF produces a predicate class that detects if a nested type exists, but only works for types, not other kinds of defined members. The class is_member_pointer<T>, but appears to require that you already know a symbol exists. I suppose such a macro might be called BOOST_MPL_HAS_XXX_MEMBER_DEF.

2 2

Re: [boost] [asio] Bug: Handlers execute on the wrong strand (Gavin Lambert).
by Marat Abrarov 31 Oct '13

31 Oct '13

> I actually ended up abandoning Asio and rolling my own threadqueue (I > didn't want any of the socket-related stuff so this wasn't as big a job > as it sounds). Mine isn't fully-baked yet (and it's Windows-only for > the moment) and I'm not sure I'd want to show it off either, but on the > upside most of the guts are entirely lock-free (though not wait-free, > since it's based on Boost.LockFree's queue). Asio at Windows uses IOCP (default settings, using asio::io_service for task scheduling) and that is the (theoretical) reason of better thread scheduling for the Asio-based thread pool. Sometimes it's really visible. Regards, Marat Abrarov.

3 6

Reimplementation of the MPL for C++11
by Louis Dionne 31 Oct '13

31 Oct '13

Hi, I am currently working on a reimplementation of the MPL for C++11. Although the library is not complete yet, I would like to gauge interest for the project from the Boost community. I wanted to wait until I have resolved some core issues before posting here, but reading the [modularization] thread made it unbearable to wait any longer :-). The library is available on GitHub: github.com/ldionne/mpl11. If some people happen to be interested by the project and would like to get involved, please get in touch with me. Regards, Louis Dionne N.B.: Some design decisions will be influenced by the community (if there's interest) and I'm experimenting a lot. Don't be put off if you see something that you don't like: it might change.

12 23

[range] RFC: span(iterator, size)
by TONGARI J 31 Oct '13

31 Oct '13

Hi there, I want to query if there's any interest in such a utility: span(iterator, size) : iterator_range which simply returns iterator_range(it, it + size) for RandomAccessIterator; for others modeling ForwardIterator, a special iterator adaptor, say, counted_iterator is used, so we don't have to advance it just for getting the end iterator. Thoughts?

3 15