- Boost - lists.boost.org

Boost.Python release testing failures
by Steve M. Robbins 06 Nov '09

06 Nov '09

Hi, I'm running Boost nightly regression tests on a 64-bit Debian linux platform for quite some time. I've recently added gcc 4.4 and Boost.Python is failing miserably; c.f. http://tinyurl.com/yl7yjkv If I click on a test result URL, such as for "andreas_beyer" [http://tinyurl.com/yft8k3o] I'm redirected ("See boost/bin.v2/libs/python/build/gcc-4.4/debug") which shows that the compile succeeded, but nothing more [http://tinyurl.com/yft8k3o] Digging into the bjam.log file, it turns out these tests are skipped because the Boost.Python library failed to build. It would be nice to improve the error reporting to make this clear. The compilation error is: "g++-4.4" -ftemplate-depth-128 -std=c++0x -O0 -fno-inline -w -g -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_PYTHON_SOURCE -I".." -I"/usr/include/python2.5" -c -o "/home/steve/Packages/boost/upstream/testing/release/results/boost/bin.v2/libs/python/build/gcc-4.4/debug/object/function_doc_signature.o" "../libs/python/src/object/function_doc_signature.cpp" ../libs/python/src/object/function_doc_signature.cpp: In static member function 'static boost::python::str boost::python::objects::function_doc_signature_generator::pretty_signature(const boost::python::objects::function*, size_t, bool)': ../libs/python/src/object/function_doc_signature.cpp:238: error: no match for 'operator%' in '"%s %s(%s%s%s%s)" % std::make_tuple(_Elements&& ...) [with _Elements = boost::python::str&, const boost::python::api::object&, boost::python::str, boost::python::str, boost::python::str, std::string](((const boost::python::api::object&)(& f->boost::python::objects::function::m_name)), ((boost::python::str&&)(& boost::python::str::join(const T&) const [with T = boost::python::api::object_slice](((const boost::python::api::object_slice&)((const boost::python::api::object_slice*)(& boost::python::api::object_operators::slice(const T&, const V&) [with T = int, V = size_t, U = boost::python::api::object](((const int&)((const int*)(&0))), ((const size_t&)((const size_t*)(&(((size_t)arity) - n_overloads))))))))))), ((boost::python::str&&)(&((n_overloads != 0u) ? ((((size_t)arity) != n_overloads) ? boost::python::str(((const char*)" [,")) : boost::python::str(((const char*)"[ "))) : boost::python::str()))), ((boost::python::str&&)(& boost::python::str::join(const T&) const [with T = boost::python::api::object_slice](((const boost::python::api::object_slice&)((const boost::python::api::object_slice*)(& boost::python::api::object_operators::slice(const T&, const V&) [with T = size_t, V = unsigned int, U = boost::python::api::object](((const size_t&)((const size_t*)(&(((size_t)arity) - n_overloads)))), ((const unsigned int&)((const unsigned int*)(& arity)))))))))), ((std::string&&)(& std::basic_string<char, std::char_traits<char>, std::allocator<char> >(n_overloads, 93, ((const std::allocator<char>&)((const std::allocator<char>*)(& std::allocator<char>())))))))' ../boost/python/object_operators.hpp:104: note: candidates are: boost::python::api::object boost::python::api::operator%(const boost::python::api::object&, const boost::python::api::object&) ../libs/python/src/object/function_doc_signature.cpp:249: error: no match for 'operator%' in '"%s(%s%s%s%s) -> %s" % std::make_tuple(_Elements&& ...) [with _Elements = const boost::python::api::object&, boost::python::str, boost::python::str, boost::python::str, std::string, boost::python::str&](((boost::python::str&&)(& boost::python::str::join(const T&) const [with T = boost::python::api::object_slice](((const boost::python::api::object_slice&)((const boost::python::api::object_slice*)(& boost::python::api::object_operators::slice(const T&, const V&) [with T = int, V = size_t, U = boost::python::api::object](((const int&)((const int*)(&0))), ((const size_t&)((const size_t*)(&(((size_t)arity) - n_overloads))))))))))), ((boost::python::str&&)(&((n_overloads != 0u) ? ((((size_t)arity) != n_overloads) ? boost::python::str(((const char*)" [,")) : boost::python::str(((const char*)"[ "))) : boost::python::str()))), ((boost::python::str&&)(& boost::python::str::join(const T&) const [with T = boost::python::api::object_slice](((const boost::python::api::object_slice&)((const boost::python::api::object_slice*)(& boost::python::api::object_operators::slice(const T&, const V&) [with T = size_t, V = unsigned int, U = boost::python::api::object](((const size_t&)((const size_t*)(&(((size_t)arity) - n_overloads)))), ((const unsigned int&)((const unsigned int*)(& arity)))))))))), ((std::string&&)(& std::basic_string<char, std::char_traits<char>, std::allocator<char> >(n_overloads, 93, ((const std::allocator<char>&)((const std::allocator<char>*)(& std::allocator<char>())))))), ((boost::python::str&)(& ret_type)))' ../boost/python/object_operators.hpp:104: note: candidates are: boost::python::api::object boost::python::api::operator%(const boost::python::api::object&, const boost::python::api::object&) ../libs/python/src/object/function_doc_signature.cpp:262: error: no match for 'operator%' in '"%s %s(%s%s%s%s) %s" % std::make_tuple(_Elements&& ...) [with _Elements = boost::python::str, const boost::python::api::object&, boost::python::str, boost::python::str, boost::python::str, std::string, boost::python::str](((const boost::python::api::object&)(& f->boost::python::objects::function::m_name)), ((boost::python::str&&)(& boost::python::str::join(const T&) const [with T = boost::python::api::object_slice](((const boost::python::api::object_slice&)((const boost::python::api::object_slice*)(& boost::python::api::object_operators::slice(const T&, const V&) [with T = int, V = size_t, U = boost::python::api::object](((const int&)((const int*)(&0))), ((const size_t&)((const size_t*)(&(((size_t)arity) - n_overloads))))))))))), ((boost::python::str&&)(&((n_overloads != 0u) ? ((((size_t)arity) != n_overloads) ? boost::python::str(((const char*)" [,")) : boost::python::str(((const char*)"[ "))) : boost::python::str()))), ((boost::python::str&&)(& boost::python::str::join(const T&) const [with T = boost::python::api::object_slice](((const boost::python::api::object_slice&)((const boost::python::api::object_slice*)(& boost::python::api::object_operators::slice(const T&, const V&) [with T = size_t, V = unsigned int, U = boost::python::api::object](((const size_t&)((const size_t*)(&(((size_t)arity) - n_overloads)))), ((const unsigned int&)((const unsigned int*)(& arity)))))))))), ((std::string&&)(& std::basic_string<char, std::char_traits<char>, std::allocator<char> >(n_overloads, 93, ((const std::allocator<char>&)((const std::allocator<char>*)(& std::allocator<char>())))))), ((boost::python::str&&)(&(cpp_types ? boost::python::str(((const char*)"")) : boost::python::str(((const boost::python::str&)((const boost::python::str*)(& ret_type))))))))' ../boost/python/object_operators.hpp:104: note: candidates are: boost::python::api::object boost::python::api::operator%(const boost::python::api::object&, const boost::python::api::object&) ...failed gcc.compile.c++ /home/steve/Packages/boost/upstream/testing/release/results/boost/bin.v2/libs/python/build/gcc-4.4/debug/object/function_doc_signature.o... I hope this helps the Boost.Python maintainers to fix it. Let me know if you need more info. Thanks, -Steve

3 3

[rdb] 0.2.00 - bind parameter and result + dynamic sql
by Jean-Louis Leroy 05 Nov '09

05 Nov '09

I have uploaded version 0.2.01 to the vault. It contains two new major features. The first is the ability to bind parameters to variables allocated outside the prepared statement, e.g.: // in the following examples the database contains: // id first_name name age // 1 Homer Simpson 37 // 2 Marge Simpson 34 BOOST_FIXTURE_TEST_CASE(prepared_select_bind_integer_param, springfield_fixture) { person p; BOOST_AUTO(st, db.prepare(select(p.first_name).from(p).where(p.id == _))); integer id_param; st.bind_parameters(id_param); id_param = 1; BOOST_RDB_CHECK_SELECT_RESULTS(st.execute(), "((Homer))"); id_param = 2; BOOST_RDB_CHECK_SELECT_RESULTS(st.execute(), "((Marge))"); } The possibility of passing parameters to execute() remains but this is more efficient, as execute(params) binds the parameters each time it is called. Likewise, it is now possible to bind results, e.g.: BOOST_FIXTURE_TEST_CASE(prepared_select_bind_results, springfield_fixture) { person p; BOOST_AUTO(st, db.prepare(select(p.id, p.first_name).from(p))); integer id; varchar<30> first_name; st.bind_results(id, first_name); BOOST_AUTO(results, st.execute()); results.fetch(); BOOST_CHECK(!id.is_null()); BOOST_CHECK_EQUAL(id.value(), 1); BOOST_CHECK(!first_name.is_null()); BOOST_CHECK_EQUAL(string(first_name), "Homer"); results.fetch(); BOOST_CHECK(!id.is_null()); BOOST_CHECK_EQUAL(id.value(), 2); BOOST_CHECK(!first_name.is_null()); BOOST_CHECK_EQUAL(string(first_name), "Marge"); } The second feature is dynamic creation of statements. A fully static system doesn't make it possible e.g. to create a search form, where you enter (optional) values and the program returns a list of matching values. Dynamic statement parts (lists of expressions, columns, tables) are created via the make_dynamic() function. It returns a "stable" type, which does not incorporate the full type information for the encapsulated sql code. This makes it possible to create dynamic collections of sql constructs and pass them to a statement. Static and dynamic parts can be miexed freely. For example: BOOST_FIXTURE_TEST_CASE(prepared_select_bind_dynamic_integer_param, springfield_fixture) { person p; dynamic_boolean predicate = make_dynamic(p.id == _); BOOST_AUTO(st, db.prepare(select(p.first_name).from(p).where(predicate))); integer id_param; dynamic_values params; params.push_back(make_dynamic(id_param)); st.bind_parameters(params); id_param = 1; BOOST_RDB_CHECK_SELECT_RESULTS(st.execute(), "((Homer))"); id_param = 2; BOOST_RDB_CHECK_SELECT_RESULTS(st.execute(), "((Marge))"); } Here a dynamic boolean expression is used in the where clause. It contains a parameter so it is necessary to pass a collection of dynamic values when executing the statement. Here is a more complex example: BOOST_FIXTURE_TEST_CASE(prepared_select_dynamic_tables, springfield_fixture) { person p("husband"); person spouse("wife"); partner::qualified link; dynamic_expressions exprs; exprs.push_back(make_dynamic(spouse.first_name)); dynamic_tables tables; tables.push_back(make_dynamic(spouse)); tables.push_back(make_dynamic(link)); dynamic_boolean predicate = make_dynamic(p.id == link.husband && link.wife == spouse.id); BOOST_AUTO(st, db.prepare(select(p.first_name, exprs).from(p, tables).where(predicate))); varchar<30> him; dynamic_values results; varchar<30> her; results.push_back(make_dynamic(her)); st.bind_results(him, results); BOOST_AUTO(cursor, st.execute()); cursor.fetch(); BOOST_CHECK(!him.is_null()); BOOST_CHECK_EQUAL(string(him), "Homer"); BOOST_CHECK(!her.is_null()); BOOST_CHECK_EQUAL(string(her), "Marge"); } Here the projection is partly dynamic, and so is the table list and the where clause. Static entities are checked at compile-time as usual, and dynamic entities at run-time - and thus may fail with an exception. However, the system is designed to (attempt to) minimize the risk of type mismatch in the dynamic parts - no casts are required in client code (nor in the implementation ftm). The test suite contains several other examples of dynamic statements (see test_odbc_dynamic.cpp). At this point I feel that all the major features in the scope of this project have been addressed. Okay a lot is still missing - e.g. more types (currently only integer and varchar are supported), constraints, count() and such functions, group/order by... - but all these should be easy to implement in the existing framework. And the thing needs cleaning up and documentation, plus testing on Unix. J-L

1 0

[filesystem][system] Usage guideline request
by Andrey Semashev 05 Nov '09

05 Nov '09

Hi, I'm updating our software from Boost 1.33 to 1.40 and one of the major issues I encountered is using exceptions from Boost.Filesystem. The exception basic_filesystem_error has changed its interface in a breaking way, as it now relies on Boost.System error codes. I'm not aware of whether this change has been announced properly and the API deprecation period has been offered. And that is actually not what bothers me mostly. The 1.33 version of Boost.Filesystem offered a number of unified error codes that our code used to react accordingly. For example, there were error codes out_of_space_error, already_exists_error, which were used on any platform supported by Boost.Filesystem. Now, with Boost.System in place, there are at least three sets of errors: system::errc, system::windows_error and system::linux_error, although, I assume, the latter is an addition to system::errc. In order to check for the older out_of_space_error I now have to write something like this: catch (basic_filesystem_error& e) { if ( e.code() == system::errc::make_error_code( system::errc::no_space_on_device) #if defined(WIN32) || e.code() == system::windows_error::make_error_code( system::windows_error::disk_full) #endif ) { // out_of_space_error } } Is this the right way to do this? Is there a portable way to do it? I tried to find a better way in the Boost.System documentation, but was highly disappointed as there is virtually no documentation at all. Also, no examples available for this library. I wonder how this library passed the review in the first place.

2 2

[1.41.0] Release branch open for low-risk merges
by Beman Dawes 05 Nov '09

05 Nov '09

branches\release is open for low-risk merges. Use your own judgment as to what "low-risk" is, but as always stability on trunk is one of the criteria. Towards the middle of next week we will take a look at where we stand as far as the freeze for final release. We can always decide to do a second beta, too. But please do any outstanding merges as soon as you are sure they are stable, rather than waiting until the last moment. Thanks, --Beman

3 3

[1.41.0] Release branch closed for all changes; beta RC tomorrow
by Beman Dawes 05 Nov '09

05 Nov '09

The release branch is closed for all changes. Unless someone objects strenuously, I'll build a release candidate for the beta tomorrow (Tuesday) morning, eastern US time. --Beman

8 14

[timer] an accumulating_timer would be nice
by Thorsten Ottosen 05 Nov '09

05 Nov '09

Hi, For some measurements, it would be nice with a timer with the following interface class accumulating_timer { public: accumulating_timer(); // don't start timing void start(); void stop(); double elapsed() const; }; The benefit here would be that we don't have to convert to seconds until that data is actually needed. Thoughts? -Thorsten

1 0

Boost Graph Library license (boost_1_40_0/libs/graph/LICENSE)
by Troels Walsted Hansen 05 Nov '09

05 Nov '09

Hi Doug and boost developers, In a message to this mailing list on 2006-03-12 ( http://lists.boost.org/Archives/boost/2006/03/101902.php) Doug mentioned that the Boost Graph Library had been entirely converted to the regular Boost Software License (http://www.boost.org/LICENSE_1_0.txt) However, even the latest boost 1.40.0 distribution contains a file called boost_1_40_0/libs/graph/LICENSE which contains the text of the old The Boost Graph Library "Artistic License". This is slightly confusing because it could be interpreted to mean that the Boost Graph Library is still covered by the Artistic License. Can you confirm that this file is dead and void? Can it be removed from the boost distribution to avoid any license ambiguity? Thanks, Troels

2 1

Reminder: ** Please don't overquote **
by David Abrahams 05 Nov '09

05 Nov '09

I'm seeing lots of messages that quote entire threads before adding a paragraph (or sometimes just a sentence) out-of-line. Please try to keep the list and its archives readable by pruning the quoted text before posting (http://www.boost.org/community/policy.html#quoting) Thanks -- Dave Abrahams Meet me at BoostCon: http://www.boostcon.com Boost Moderator http://www.boost.org

1 0

Re: [boost] [1.41.0] Beta 1 available
by Vladimir Prus 04 Nov '09

04 Nov '09

Daniel James wrote: > On Wed, Nov 4, 2009 at 1:45 PM, Ovanes Markarian <om_boost(a)keywallet.com> wrote: >> Hello *, >> the link in the docs to Property Tree points to the wrong location. >> http://beta.boost.org/doc/libs/1_40_0/libs/property_tree/index.html >> if changing to http://beta.boost.org/doc/libs/1_41_0/libs and clicking to >> Property Tree the link points to: >> http://beta.boost.org/doc/libs/1_41_0/libs/property_tree/index.html >> But this file does not exist either. > > The documentation isn't uploaded to the site until the final release. > You can see the property tree documentation in the download. The beta > site isn't really meant for general use. Speaking of documentation: 1. It appears that http://www.boost.org/boost-build2/index.html is still broken. Is there any way to figure why? 2. Looking at http://beta.boost.org/users/news/version_1_41_0 I do not see a section 'Build System' -- which is present in boost_1_41_0.qbk Is this expected? - Volodya

2 1

[1.41.0] Beta 1 CMake 1
by troy d. straszheim 04 Nov '09

04 Nov '09

The boost.cmake beta that shadows upstream releases is out. Docs: http://sodium.resophonic.com/boost-cmake/1.41.0.beta1.cmake1/doc Tarballs and zipfiles: http://sodium.resophonic.com/boost-cmake/1.41.0.beta1.cmake1 Followups on the boost-cmake list please. -t

1 0