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

[signals2] Test failure in C++11 (trivial fix for incorrect usage of boost::optional)
by Ben Pope 06 Mar '14

06 Mar '14

I have the following errors: "clang++-3.4" -c -x c++ -std=c++11 -stdlib=libc++ -O0 -g -fno-inline -Wall -g -DBOOST_ALL_NO_LIB=1 -DBOOST_TEST_NO_AUTO_LINK=1 -I".." -o "/home/ben/development/boost/test/build/results/boost/bin.v2/libs/signals2/test/signal_test.test/clang-linux-3.4~c11_libc++/debug/link-static/signal_test.o" "../libs/signals2/test/signal_test.cpp" ../libs/signals2/test/signal_test.cpp:32:16: error: invalid operands to binary expression ('boost::optional<int>' and 'int') if(max == false) max = *first; ~~~ ^ ~~~~~ "clang++-3.4" -c -x c++ -std=c++11 -stdlib=libc++ -O0 -g -fno-inline -Wall -g -DBOOST_ALL_NO_LIB=1 -DBOOST_TEST_NO_AUTO_LINK=1 -I".." -o "/home/ben/development/boost/test/build/results/boost/bin.v2/libs/signals2/test/track_test.test/clang-linux-3.4~c11_libc++/debug/link-static/track_test.o" "../libs/signals2/test/track_test.cpp" ../libs/signals2/test/track_test.cpp:36:14: error: invalid operands to binary expression ('boost::optional<int>' and 'int') if(max == false) Richard smith explains the problem here: http://llvm.org/bugs/show_bug.cgi?id=18180#4 "OK, I see what's happening -- in Clang 3.3 and GCC 4.8, 'false' is being treated as a null pointer constant. boost::optional implicitly converts to an "unspecified-bool-type" that happens to be a pointer-to-member type, and thus can be compared against a null pointer constant via the built-in operator!=(pointer-to-member, pointer-to-member) overload. In C++11 onwards, 'false' isn't a null pointer constant any more, so this comparison is no longer valid. Clang 3.3 and GCC 4.8 don't implement that rule; Clang 3.4 does." The trivial fix is to change the if statements at: ../libs/signals2/test/signal_test.cpp:32:16: ../libs/signals2/test/track_test.cpp:36:14: to if(!max) rather than if(max == false). Ben

7 19

DRYing BOOST_FUSION_ADAPT_STRUCT with decltype/Boost.TypeOf ?
by Damien Buhl 05 Mar '14

05 Mar '14

Hi dear Boost Fusion developers, I was asking myself if there were already plan to improve BOOST_FUSION_ADAPT_STRUCT to benefit from C++11 features like decltype ? This would be interesting to avoid the risk encountered that the types definitions can get out-of-sync. And would avoid typing type declarations twice. Currently there is BOOST_FUSION_DEFINE_STRUCT to avoid repeating the type information for each field. However this is something that makes most developer I know unhappy, as it obliges to modify the readable C++ aggregate types definition (i.e. Could be public headers) with this macro. Then there is the nice choice of BOOST_FUSION_ADAPT_STRUCT which obliges retyping the type and adds the risk that some field type information could get out-of-sync between the struct definition and the BOOST_FUSION_ADAPT_STRUCT listing. I think it would be valuable to add macros that would enable to select the fields that we want to adapt to a Random Access Sequence without requiring to repeat the type information. I would find more comfortable to write the example provided here http://www.boost.org/doc/libs/1_55_0/libs/fusion/doc/html/fusion/adapted/ad… as follow : namespace demo { struct employee { std::string name; int age; }; } // demo::employee is now a Fusion sequence BOOST_FUSION_ADAPT_STRUCT_EXT( demo::employee, (name) (age)) And a naïve implementation of BOOST_FUSION_ADAPT_STRUCT_EXT could be: #include <boost/typeof/typeof.hpp> #include <boost/fusion/include/adapt_struct.hpp> #include <boost/preprocessor/seq/for_each.hpp> #define ATTRIBUTE_DEFINITION(r, data, elem) \ (BOOST_TYPEOF(data::elem), elem) \ #define BOOST_FUSION_ADAPT_STRUCT_EXT(NAME, ATTRIBUTES) \ BOOST_FUSION_ADAPT_STRUCT(NAME, \ BOOST_PP_SEQ_FOR_EACH(ATTRIBUTE_DEFINITION, NAME, ATTRIBUTES)) #endif The same could certainly be achieved for BOOST_FUSION_ADAPT_TPL_STRUCT, while I didn't check. Thanks for the really great job done in Boost.Fusion. Cheers, -- Damien Buhl alias daminetreg

3 7

[Boost.Test] Assertion changes in trunk? [WAS: Call for Review: Boost.Test documentation rewrite]
by Dominique Devienne 19 Feb '14

19 Feb '14

On Wed, Jan 22, 2014 at 11:25 AM, Alexander Lamaison <awl03(a)doc.ic.ac.uk>wrote: > [...] As for as I'm aware, the only change is > to the assertion macros, which move to a more natural syntax: > > BOOST_CHECK_EQUAL(a, b) becomes BOOST_TEST(a == b) > BOOST_CHECK_LT(a, b) becomes BOOST_TEST(a < b) > ... etc. > BOOST_REQUIRE_EQUAL(a, b) becomes BOOST_TEST_REQUIRE(a == b) > ... etc. > BOOST_WARN_EQUAL(a, b) becomes BOOST_TEST_WARN(a == b) > But don't we then miss better messages which actually show the values themselves when the assert fails? I do BOOST_CHECK(a == b) only when a and b lack the op<<, but otherwise greatly prefer BOOST_CHECK_EQUAL(a, b). And what's the point of going from BOOST_REQUIRE(expr) to BOOST_TEST_REQUIRE(expr), i.e. make it longer / more typing? What am I missing? --DD

11 17

Refactoring tools/regression and tools/release into separate sub-modules
by Beman Dawes 14 Feb '14

14 Feb '14

The tools used by regression testers and regression reporting, and the tools used by release managers are currently part of the boost-super project. As we gain experience with Git and submodules, it is becoming clear these need to be decomposed into two separate submodules. Among other advantages, that would speed work on these tools as we could better utilize volunteers without having to hand out excessive super-project write permissions. We would like one or two volunteers to do the refactoring. You don't need to be a library maintainer or release manager, although that's fine if you are. You do need git skills, as we do want to preserve history. Comments? --The release managers

5 22

[git] automated update of superproject master branch
by Peter A. Bigot 14 Feb '14

14 Feb '14

I realize there are several email threads about how the super-project branch should be managed, but most pre-date live experience with boost on git and go deep into other aspects of the issue, so I still want to call this out specially: https://svn.boost.org/trac/boost/wiki/ModBigPicture specifies that the master branch on each module should be stable at all times, which is the right policy. Currently, the master branch on the super-project is automatically updated twice(?) per hour selecting all updates to the master branches of modules. Consequently, super-project master is the exact opposite of stable. This divergence is confusing. I'm unconvinced that waiting a few days will demonstrate a significant decrease in churn on the super-project master branch. Some is due to multiple updates to specific modules, which might decrease as maintainers become more familiar with git and only push once, but interoperability issues will still arise and there will be no way to tell which master branch commits produce a working Boost installation. There is value in having a branch with automated-update semantics, but IMO regardless of what the final policy will be, "master" is not the right choice for this, and automated updates of it should stop ASAP. Perhaps the update script can simply be moved to occur on latest/master and latest/develop. Leave master untouched until whatever gets committed to it has undergone cross-toolchain integration validation, and make develop available for changes to superproject content that are not just submodule updates. Peter

4 4

[Fibers] Performance
by Hartmut Kaiser 10 Feb '14

10 Feb '14

Oliver, Do you have some performance data for your fiber implementation? What is the (amortized) overhead introduced for one fiber (i.e. the average time required to create, schedule, execute, and delete one fiber which runs an empty function, when executing a larger number of those, perhaps 500.000 fibers)? It would be interesting to see this number when giving 1..N cores to the scheduler. Thanks! Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu

14 92

sqlpp11: SQL for C++
by Roland Bock 06 Feb '14

06 Feb '14

Hi, over the last four or five years I developed several SQL libraries for C++. With C++11 I was finally able to create an SQL library that meets my own expectations and requirements. It is being used in production, I recently put it on github, and I would really like to hear from you guys whether this is something that could be interesting for you personally or for boost? https://github.com/rbock/sqlpp11 https://github.com/rbock/sqlpp11/wiki sqlpp11 is a template library representing an embedded domain specific language (EDSL) that allows you to * define types representing tables and columns, * construct type safe queries checked at compile time for syntax errors, type errors, name errors and even some semantic errors, * interpret results by iterating over query-specific structs with appropriately named and typed members. This results in several benefits, e.g. * the library user operates comfortably on structs and functions, * the compiler reports many kinds of errors long before the code enters unit testing or production, * the library hides the gory details of string construction for queries and interpreting string based results returned by select calls. I.e. you don't need to use strings in query construction where you wouldn't use them in SQL and there is no need to use positional arguments or to parse strings when obtaining fields from a result row (the latter being true unless you do not know which columns to select at compile time). The library supports both static and dynamic queries. The former offers greater benefit in terms of type and consistency checking. The latter makes it easier to construct queries on the flight. Specific traits of databases (e.g. unsupported or non-standard features) are known at compile time as well. This way, the compiler can tell the developer at compile time if a query is not accepted by the database (e.g. if a feature is missing). And the library can form the query in the correct manner, for instance if the engine uses concat instead of operator|| to concatenate strings. Two Examples: ============= Static Select: -------------- // selecting zero or more results, iterating over the results for (const auto& row : db.run( select(foo.name, foo.hasFun) .from(foo) .where(foo.id > 17 and foo.name.like("%bar%")))) { if (row.name.is_null()) std::cerr << "name will convert to empty string" << std::endl; std::string name = row.name; // text fields are implicitly convertible to string bool hasFun = hasFun; // bool fields are implicitly convertible to bool } Dynamic Select: ---------------- auto s = dynamic_select(db, tab.foo).dynamic_columns().from(tab); if (userWantsBar) s.add_column(tab.bar); for(const auto& row : run(s)) { std::cerr << "row.foo: " << row.foo; if (userWantsBar) std::cerr << "row.bar" << row.at("bar"); std::cerr << std::endl; }; Please let me know your questions/thoughts/suggestions/rants. Contributions welcome, of course :-) Regards, Roland

22 88

Trying modular Boost
by Paul A. Bristow 04 Feb '14

04 Feb '14

FWIW here are some things I didn't understand or did wrong. (And, of course, playing Devil's Decidedly Dumb Advocate ;-) 1 How do I know if I have the right version of Git? Open GitHub icon and check Tools/About? 2 Windows hint: If you install TortoiseGIT, avoid incompatibilities by using the command line version of Git that TortoiseGIT installs. I.E. place C:\Program Files (x86)\Git\cmd in your path ahead of any other git binaries, such as cygwin. Huh? Am I Shelling, Bashing, Batting or Powershelling? How do I do that? How do I check that I have done this right? Open a Windows command window? Many Windowers will not know how to find/edit their path (and should not need to know?). A link would help. If you have dozens of items in the path, this is pretty awkward to edit? But (after a frustrating failure to get SSH access to work - in a separate post) I got to the main course using https: https://github.com/boostorg/boost.git Submodule 'io' (https://github.com/boostorg/io.git) registered for path 'libs/io' Submodule 'iostreams' (https://github.com/boostorg/iostreams.git) registered for path 'libs/iostreams' <big snip> Cloning into 'tools/quickbook'... Submodule path 'tools/quickbook': checked out '340c65150d175ffc20a9a877247928b3ed5eba1b' Success (4040769 ms @ 31-Dec-2013 17:00:21) Just over an hour (using my nominal 10 mbps living-in-the-boondocks but line-of-sight radio link) - something that should be noted in the docs (along with a strong recommendation to send to a log file)? Other you would miss/lose this very useful info? Building the Boost C++ Libraries. Performing configuration checks - symlinks supported : no - hardlinks supported : yes - 32-bit : yes . And I could test system library OK J Phew! Paul PS I had an existing (luckily current) b2.exe at c:\program files\Boost and this is implicitly in my PATH. Do we need to be more specific about how b2 is stored and accessed? Some check that b2.exe vcvars32.bat etc are all set up correctly would be good? --- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 <mailto:pbristow@hetp.u-net.com> pbristow(a)hetp.u-net.com

7 14

Process for the Community Maintenance Team
by Marshall Clow 04 Feb '14

04 Feb '14

I’ve put up a set of procedures for the Boost Community Maintenance Team (CMT) on the wiki at: https://svn.boost.org/trac/boost/wiki/CommunityMaintenance Comments welcomed. — Marshall

4 6

named_condition_any not working.
by Marius Adrian DOBRESCU 02 Feb '14

02 Feb '14

Hello! I tried to use into my code an interprocess mechanism like producer/multiple consumers with named_sharable_mutexes. I found out that named_condition_any is not working with any kind of scoped locks. Neither with sharable_mutex or simple named_mutex. It takes the lock successful but cannot unblock another process when notify is called. I used linux, gcc 4.8, just basic build, linking with pthreads. Is this a known issue to you because I couldn't find any info related on the Internet? Maybe I can take a look next week what is in there... Adrian

2 1