January 2011 - Boost - lists.preview.boost.org

[smart_ptr] Patch submitted for #1113
by Nathan Crookston 25 Jan '11

25 Jan '11

All, I submitted a patch for ticket #1113 [1] which allows statements like the following: boost::shared_array<int> pNonConst; boost::shared_array<const int> pConst = pNonConst; while preventing treating arrays polymophically. It has been tested on windows with VC8, VC10, g++3.X and g++4.X. Additionally it has been tested on solaris with g++3.4. I didn't modify the tests, but running them seems to produce the correct output. I'd appreciate it if someone could take a look at it, perhaps applying it if it looks good. Thanks, Nate [1] <https://svn.boost.org/trac/boost/ticket/1113>

1 0

Re: [boost] What's happened to Ryppl?
by Dave Abrahams 25 Jan '11

25 Jan '11

[Redirecting replies to the boost developers' list; we should have been there nearly from the beginning. Anyone who wants to see the earlier parts of the thread should look to http://groups.google.com/group/boostusers/browse_thread/thread/6d0d01eb3cac…] Hi Robert, Could you please use standard quoting? I am having trouble separating the parts you wrote below from what Eric wrote. Thanks, Dave At Tue, 25 Jan 2011 09:06:19 -0800, Robert Ramey wrote: > > Eric Niebler wrote: > > A lot of work remains --- that is, if it's also our intention to > modularize boost and have a functioning cmake build system, too. > > At least, modularization seems like it would be a good thing to do at the > same time. And nobody is working on a bjam system for modularized boost. > > *** I don't believe there is any reason to couple modularization of boost to > any particular build system. > I use bjam to build and test the serialization library on my local machine. > I just set the current directory to libs/serialization/test and run bjam > with some switches. This builds/updates the prerequisites to the > serialization library, builds the serialization library, then builds and > runs the tests. (and in my case builds a table of test results since i use > library status.sh). I'm would expect that I could the same with CTest. > > The key issue is that the build system permit the building of just one > "module" (and its necessary prerequisites). Bjam (and hopefully ctest) does > this now. Building of "all" of boost is just the building of each module. > Building of some alternative "distribution" is just the building of each of > the component modules (and their prequisites). There isn't even any reason > why each module has to use the same build system. > > <idle speculation> > Is it feasible to have both git and svn development going on > simultaneously? Two-way synchronization from non-modularized svn boost > to modularized git boost? Is that pure insanity? > </idle speculation> > > *** By the same token, a "modularized" boost needn't require that all > modules use the same source control system. Ideally, the build for each > module would use checkout/update the local copy of the module according to > the "configuration file" (...v2 or ctest.?). > > Once the procedure for for building a module is moved to the module rather > than invoked "from the top", modularization can proceed incrementally. > > Robert Ramey > > -- > > > _______________________________________________ > > Boost-users mailing list > > Boost-users(a)lists.boost.org > > http://lists.boost.org/mailman/listinfo.cgi/boost-users > > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users -- Dave Abrahams BoostPro Computing http://www.boostpro.com

1 0

[context] new version with stack-allocator
by Oliver Kowalke 25 Jan '11

25 Jan '11

boost vault contains a new version (0.4.0) where the user can provide its own stack allocator (the lib comes with a protected-stack allocator). Oliver

2 3

[context] build issue with context-0.3.5
by Charlls Quarra 25 Jan '11

25 Jan '11

Hi Oliver, First of all, thanks for updating your context library. I might be wrong, but i think yours is currently the only supported coroutine library for c++ which is a candidate for boost. So kudos to you for that effort that you are doing. I'm having a build error on the 0.3.5; (this is on ubuntu linux x86 platform) $ bjam -a -toolset=gcc cxxflags=-std=c++0x architecture=x86 instruction-set=i686 --with-context nBuilding the Boost C++ Libraries.nn ...patience... ...found 230 targets... ...updating 8 targets... gcc.compile.c++ bin.v2/libs/context/build/gcc-4.4.5/release/architecture-x86/instruction-set-i686/threading-multi/context_uc_posix.o In file included from libs/context/src/context_uc_posix.cpp:9: ./boost/context/context.hpp:24: error: variable ‘boost::contexts::BOOST_SYMBOL_EXPORT boost::contexts::context’ has initializer but incomplete type ./boost/context/context.hpp:26: error: expected primary-expression before ‘private’ ./boost/context/context.hpp:26: error: expected ‘}’ before ‘private’ ./boost/context/context.hpp:26: error: expected ‘,’ or ‘;’ before ‘private’ ./boost/context/context.hpp:27: error: expected unqualified-id before ‘private’ ./boost/context/context.hpp:27: error: expected constructor, destructor, or type conversion before ‘&’ token ./boost/context/context.hpp:32: error: expected constructor, destructor, or type conversion before ‘;’ token ./boost/context/context.hpp:34: error: expected unqualified-id before ‘public’ ./boost/context/context.hpp:41: error: typedef ‘boost::contexts::unspecified_bool_type’ is initialized (use decltype instead) ./boost/context/context.hpp:41: error: expected primary-expression before ‘)’ token ./boost/context/context.hpp:45: error: variable or field ‘unspecified_bool’ declared void ./boost/context/context.hpp:45: error: expected primary-expression before ‘)’ token ./boost/context/context.hpp:47: error: ‘context’ does not name a type ./boost/context/context.hpp:49: error: ‘context’ does not name a type ./boost/context/context.hpp:52: error: ‘context’ does not name a type ./boost/context/context.hpp:55: error: expected constructor, destructor, or type conversion before ‘;’ token ./boost/context/context.hpp:57: error: expected class-name before ‘(’ token ./boost/context/context.hpp:59: error: expected constructor, destructor, or type conversion before ‘(’ token ./boost/context/context.hpp:61: error: expected constructor, destructor, or type conversion before ‘&’ token ./boost/context/context.hpp:63: error: variable or field ‘jump_to’ declared void ./boost/context/context.hpp:63: error: ‘other’ was not declared in this scope ./boost/context/context.hpp:65: error: variable or field ‘swap’ declared void ./boost/context/context.hpp:65: error: ‘other’ was not declared in this scope ./boost/context/context.hpp:67: error: non-member function ‘bool boost::contexts::operator!()’ cannot have cv-qualifier ./boost/context/context.hpp:67: error: ‘bool boost::contexts::operator!()’ must have an argument of class or enumerated type ./boost/context/context.hpp:69: error: expected type-specifier before ‘unspecified_bool_type’ ./boost/context/context.hpp:73: error: variable or field ‘swap’ declared void ./boost/context/context.hpp:73: error: ‘context’ was not declared in this scope ./boost/context/context.hpp:73: error: ‘l’ was not declared in this scope ./boost/context/context.hpp:73: error: ‘context’ was not declared in this scope ./boost/context/context.hpp:73: error: ‘r’ was not declared in this scope ./boost/context/context.hpp:78: error: ‘contexts’ has not been declared ./boost/context/context.hpp:80: error: expected declaration before ‘}’ token ./boost/context/context.hpp:43: warning: ‘boost::contexts::default_stacksize’ defined but not used "g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -march=i686 -pthread -fPIC -std=c++0x -DBOOST_ALL_NO_LIB=1 -DBOOST_CONTEXT_DYN_LINK=1 -DNDEBUG -I"." -c -o "bin.v2/libs/context/build/gcc-4.4.5/release/architecture-x86/instruction-set-i686/threading-multi/context_uc_posix.o" "libs/context/src/context_uc_posix.cpp" ...failed gcc.compile.c++ bin.v2/libs/context/build/gcc-4.4.5/release/architecture-x86/instruction-set-i686/threading-multi/context_uc_posix.o... ...skipped <pbin.v2/libs/context/build/gcc-4.4.5/release/architecture-x86/instruction-set-i686/threading-multi>libboost_context.so.1.43.0 for lack of <pbin.v2/libs/context/build/gcc-4.4.5/release/architecture-x86/instruction-set-i686/threading-multi>context_uc_posix.o... ...skipped <pstage/lib>libboost_context.so.1.43.0 for lack of <pbin.v2/libs/context/build/gcc-4.4.5/release/architecture-x86/instruction-set-i686/threading-multi>libboost_context.so.1.43.0... ...skipped <pstage/lib>libboost_context.so for lack of <pstage/lib>libboost_context.so.1.43.0... gcc.compile.c++ bin.v2/libs/context/build/gcc-4.4.5/release/architecture-x86/instruction-set-i686/link-static/threading-multi/context_uc_posix.o gcc.archive bin.v2/libs/context/build/gcc-4.4.5/release/architecture-x86/instruction-set-i686/link-static/threading-multi/libboost_context.a common.copy stage/lib/libboost_context.a ...failed updating 1 target... ...skipped 3 targets... ...updated 4 targets... - Charles Quarra

2 2

[SQL-Connectivity] Is Boost interested in CppDB?
by Artyom 25 Jan '11

25 Jan '11

Hello, I have recently released a new SQL Connectivity library: General ------- Documentation : http://art-blog.no-ip.info/sql/cppdb/ Mirror Docs. : http://cppcms.sourceforge.net/sql/cppdb/ Download : https://sourceforge.net/projects/cppcms/files/cppdb/ Features -------- - Performance is the primary goal - make fastest possible SQL connectivity as possible - Transparent connection pooling support - Transparent prepared statements caching - Dynamic DB modules loading and optional static linking - Full and high priority support of FOSS RDBMS: MySQL, PostgreSQL, Sqlite3 - Support as many RDBMSs as possible via cppdb-odbc bridge - Simplicity in use - Locale safety - Support of both explicit verbose API and brief and nice syntactic sugar What it is not: --------------- This is not ORM library and not supposed to be so. This is something similar to what JDBC gives to JDK and QtSql gives to Qt and more. Boost Interest -------------- Currently I'm think whether should I boostify it, release it under BSL (currently it is LGPLv3) and submit it for formal review in boost or shouldn't I? Why do I ask, not because I'm thinking it is not good enough but rather because I feel that the "boostification" effort would be wasted at this point. For about half a year ago I had submitted a Boost.Locale for formal review, I use it under other namespace as part of CppCMS project all the time and in fact I receive most request and bug reports for Boost.Locale via CppCMS project and not via CppCMS.Locale so basically I have to handle two projects and synchronize between them all the time, and Boost.Locale is still stuck in review queue. So does it worth the effort? So before I do any steps forward may be it is better to make sure it gets (or even passes the review) and then boostify the library (which can be done very easily). Regards, Artyom

22 53

[assert][lightweight_test] Quick review of proposed changes
by Beman Dawes 24 Jan '11

24 Jan '11

In reviewing the "[assert] static_assert envy" thread, I agreed with Steven Watanabe: > MHO, the last thing we need is lots of minor variations that > don't add any real utility. KISS was also a factor, as I wanted to add only features that I would personally use right away, or that were needed for BOOST_ASSERT compatibility. It boiled down to the following: [assert] * Added BOOST_ASSERT_MSG(expr, msg) macro. If expr is false, outputs msg, then calls std::abort(). BOOST_DISABLE_ASSERTS behaves the same as in BOOST_ASSERT. BOOST_ENABLE_ASSERT_MSG_HANDLER enables a separate error handler. BOOST_ASSERT_MSG_OSTREAM defaults to std::cerr. User may define to specify a different output stream. * Added BOOST_ASSERT_MSG test cases to libs/utility/assert_test.cpp * Added BOOST_ASSERT_MSG docs to libs/utility/assert_test.cpp <boost/detail/lightweight_test.hpp> has the same Visual Studio output interleaving problem, so it makes sense to apply a similar fix at the same time. * Messages are now sent do BOOST_LIGHTWEIGHT_TEST_OSTREAM * BOOST_LIGHTWEIGHT_TEST_OSTREAM defaults to std::cerr. User may define to specify the output stream for messages. Updated files: http://mysite.verizon.net/beman/assert.hpp http://mysite.verizon.net/beman/assert.html http://mysite.verizon.net/beman/assert_test.cpp http://mysite.verizon.net/beman/lightweight_test.hpp Let's do a quick review before these get committed to trunk. Say until Monday morning. (They won't go in 1.46.0; far too late for that.) Comments welcome! --Beman

2 6

Boost.Graph Metagraph project
by Fernando J. Iglesias García 24 Jan '11

24 Jan '11

Hi all, I am new in Boost libraries and have heard about Boost.Graph and metaprograms. I think there is an ongoing project related called Metagraph. How can I get in collaboration with the people working on it? Regards, Fernando.

7 13

[container] documentation
by Gordon Woodhull 24 Jan '11

24 Jan '11

Hi Ion, I read over the documentation for Container. Looks like a neat library. I like the idea of a next gen STL in Boost. In the documentation, I think the recursive containers section could spell out what's going on here - I didn't catch it at first. It could just say "Recursive data structures contain elements of their own type." Perhaps with a link to http://en.wikipedia.org/wiki/Recursive_data_type. Pretty cool. Didn't this grow out of Interprocess? I'm wondering if it has somehow an improved contract with the allocator to support shared memory - or is that worth talking about? Cheers, Gordon

2 4

Re: [boost] [1.45][Serialization] fails to cross-compile usingarm-linux-uclibc toolchain
by Alex Potapenko 24 Jan '11

24 Jan '11

Robert Ramey wrote: > BOOST_STATIC_ASSERT(sizeof(class_id_type) == sizeof(int_least16_t)); > BOOST_STATIC_ASSERT(sizeof(class_id_reference_type) == > sizeof(int_least16_t)); These should be investigated. before commenting out. It could be detecting something unexpected in a pre-requisite library. I'm afraid I haven't neither got the knowledge, nor the skills to investigate it myself :( In case you (or someone else) are willing to investigate it for me, here's a relatively simple way to trigger these errors: 1. Checkout the optware trunk: $ svn co http://svn.nslu2-linux.org/svnroot/optware/trunk optware 2. Build the toolchain: $ cd optware; make mbwe-bluering-target $ cd mbwe-bluering; make directories toolchain ipkg-utils 3. Replace make/boost.mk from the svn with the one attached to this letter 4. Cross-compile: $ make boost # while remaining in the mbwe-bluering directory Thanks in advance, Alex

1 0

Re: [boost] [Boost-bugs] [Boost C++ Libraries] #5111: BOOST_TR1_STD_HEADER bad on Solaris 11/stdcxx4
by Bryce Lelbach 23 Jan '11

23 Jan '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 23 Jan 2011 20:39:12 -0000 "Boost C++ Libraries" <noreply(a)lists.boost.org> wrote: > #5111: BOOST_TR1_STD_HEADER bad on Solaris 11/stdcxx4 > > this is likely because stdcxx4 resides in > /usr/include/stdcxx4/ > /usr/include/stdcxx4/ansi > there, which the config_all.hpp does not take into account and sets > BOOST_TR1_STD_HEADER inappropriately This was fixed for Pathscale - John, could you please modify the fix I made for Pathscale to apply to any toolchain using the apache/rw stdlib? - -- Bryce Lelbach aka wash boost-spirit.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAk08lxcACgkQ9cB/V3/s9EzcHwCdGCinVPCvyKbGDPs7LHa1DoIQ c3wAn1OO39wYkj1F5BmCSmjR7zW0oaGD =WQvl -----END PGP SIGNATURE-----

2 1