- Boost - lists.boost.org

[wave] preprocess fails using b2
by Fletcher, John P 28 Jul '14

28 Jul '14

I have been using b2 to build the preprocessed files for boost phoenix. When I try to do this it now fails with a failure to build thread.cpp "g++-4.6" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pedantic -pthread -Wextra -Wno-long-long -Wno-variadic-macros -Wunused-function -pedantic -DBOOST_ALL_NO_LIB=1 -DBOOST_SYSTEM_STATIC_LINK=1 -DBOOST_THREAD_BUILD_LIB=1 -DBOOST_THREAD_DONT_USE_CHRONO -DBOOST_THREAD_POSIX -DBOOST_WAVE_SUPPORT_THREADING=0 -DNDEBUG -I"../../.." -c -o "../../../bin.v2/libs/thread/build/gcc-4.6/release/link-static/threading-multi/wavetool-on/pthread/thread.o" "../../../libs/thread/src/pthread/thread.cpp" ../../../boost/ref.hpp:32:25: error: redefinition of â€˜class boost::reference_wrapper<T>â€™ ../../../boost/core/ref.hpp:59:25: error: previous definition of â€˜class boost::reference_wrapper<T>â€™ ../../../boost/ref.hpp:56:75: error: redefinition of â€˜template<class T> const boost::reference_wrapper<T> boost::ref(T&)â€™ ../../../boost/core/ref.hpp:131:74: error: â€˜template<class T> const boost::reference_wrapper<T> boost::ref(T&)â€™ previously declared here . It looks as though it is picking up two copies of the header file ref.hpp. This is the case with both gcc 4.6 and also gcc 4.9.0 It is not clear to me where the source file is coming from. At the moment all the libraries in my modular boost are checked out as develop. This is meaning that I cannot update my preprocessed files. Please advise me what to do. Thanks John

5 6

[1.56.0] Beta 1 Available
by Marshall Clow 28 Jul '14

28 Jul '14

Boost release 1.56.0 beta 1 is now available from SourceForge See http://sourceforge.net/projects/boost/files/boost/1.56.0.beta.1/ This release contains 2 new libraries: * Align: Memory alignment functions, allocators, and adaptors, from Glen Fernandes. * Type_Index: Runtime/Compile time copyable type info, from Antony Polukhin. Modularization Boost version control has migrated to a system using git submodules. This shouldn't make too much of a difference to users, although the directory structure is now a bit different. Parts of some libraries have been moved into different modules, and several new modules have been extracted from existing code. All header paths should remain the same. The new modules are: * Assert: Customizable assert macros. Maintained by Peter Dimov. * Core: Core utilities used by other libraries, with minimal dependencies. Maintained by Peter Dimov, Glen Fernandes and Andrey Semashev. * Lexical_Cast: General literal text conversions, such as an int represented a string, or vice-versa, from Kevlin Henney. * Throw_Exception: A common infrastructure for throwing exceptions from Boost libraries, from Emil Dotchevski. * Winapi: Windows API declarations without <windows.h>, for internal Boost use. For details of what's in the release, see http://www.boost.org/users/history/version_1_56_0.html. Note that the links to files on this web page are for the final release - use the SourceForge link above to get the beta files. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

8 17

Boost.Any and RTTI
by Chris Glover 27 Jul '14

27 Jul '14

Hi, I need a Boost.Any like facility that doesn't depend on RTTI, so I patched Boost.Any to utilize Boost.TypeIndex if BOOST_NO_RTTI is defined. The diff is available here; https://github.com/cdglove/any/commit/7188b13909a061495ef31f979b55f9779a9e9… Is there any interest in merging this into mainline? Or is someone working on a more correct patch than this? Thanks, -- chris

2 3

[GSoC] Scheduled Executors beta 1 release
by Ian Forbes 27 Jul '14

27 Jul '14

Hello, I am working on implementing scheduled executors as part of GSoC 2014 and am ready to announce my beta 1 release. For more information on my project please see my original proposal at www.cs.mcgill.ca/~iforbe All my work is currently on this branch of boost.thread. https://github.com/BoostGSoC14/boost.thread.executors . I have written a fairly extensive README about design and implementation on this page. Basically a scheduled executor is an executor which guarantees that a certain task won't be run before a certain time point. Its main use cases would be things such as periodically reloading a file, pushing updates, flushing data, and polling. It has a thread safe priority queue that store tasks (currently std::function) along with a chrono::time_point. The priority queue is ordered so that the task with the least time point (closest to time 0) is at the front. There is an abstract class scheduled_executor that deals with all the enqueue methods to the executor. The ctor is protected. There are no virtual members. There are 2 subclasses. scheduled_thread_pool and scheduling_adaptor. These add dequeuing logic to the scheduled_executor by means of a worker thread(s). I'm mostly interested in people reading this part of the README: https://github.com/BoostGSoC14/boost.thread.executors#possible-changes--rfcs This details possible changes that could be made and I would like some feedback on them as these items have both pros and cons. Please provide your feedback and I will to my best to address your questions and concerns. Thanks, Ian

4 13

Portable robust mutex an another try...
by Ladislav Sopko 27 Jul '14

27 Jul '14

Hello, I did try to continue with */Ion Gaztanaga's /*idea of portable robust mutex. I post my code and considerations in codereview. http://codereview.stackexchange.com/questions/57083/portable-c-boostiterpro… I hope to find some one to discuss about. thx -- Sopko Ladislav 3D Informatica, Via Speranza 35, 40068, S.Lazzaro di Savena - Bologna, Italy Tel: +39051450844 | Fax: +39051451942 WWW: http://www.3di.it Documentation: https://intra.3di.it/manuali/ - http://wiki.3di.it FTP: ftp://ftp@ftp.3di.it, Download:/3di, Upload:/incoming **** Informativa Privacy - Ai sensi del D. Lgs n. 196/2003 (Codice Privacy) si precisa che le informazioni contenuti in questo messaggio sono riservate e ad uno esclusivo del destinatario. Qualora il messaggio in parola Le fosse pervenuto per errore, La preghiamo di eliminarlo senza copiarlo e di non inoltrarlo a terzi, dandocene gentilmente comunicazione. Grazie. Privacy Information - This message, for the D. Lgs m. 196/2003 (Privacy Code), may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addessee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thanks you for your cooperation. --

4 4

Donation
by Avihay Eyal 27 Jul '14

27 Jul '14

Hi, my company uses boost, and we would like to donate money. Is it possible? If so, then how? Thanks.

2 1

Permission to merge to master during release
by Glen Fernandes 26 Jul '14

26 Jul '14

The small change: https://github.com/boostorg/smart_ptr/commit/88f0a98d71 Renaming identifier of a member function from "free" to anything that is not "free" to compensate for _CRTDBG_MAP_ALLOC users in MSVC. (A colleague at Microsoft reported this to me today; he tried the 1.56.0 beta with MSVC and with _CRTDBG_MAP_ALLOC defined. It doesn't like a member function named "free"). Glen

4 4

Help about boost library x64 used in the LibLas tools
by Luca Nardelli 26 Jul '14

26 Jul '14

Helo to all, thanks a LOT for your great work! I'm trying to use the x64 library for VS 2013 (12), but I have a lot of "unresolved errors" when I try to compile the *LibLas *library that uses boost. For example I get this error: *error LNK2001: unresolved external symbol "class boost::system::error_category const & __cdecl boost::system::system_category(void)" (?system_category@system@boost@@YAAEBVerror_category@12@XZ)* Could you maybe help me or give some hint? Thanks!!! -- "Il miglior modo per cambiare e iniziare"

2 1

C++ committee meeting report
by Beman Dawes 25 Jul '14

25 Jul '14

The C++ committee met last week in Rapperswil, Switzerland. Actions that might be of interest to Boosters include: * Shipped the File System TS for ISO DTS (i.e. final) ballot. Since it would be very unusual for at DTS ballot to fail, the File System TS is essentially done. The committee is now actively looking for File System TS 2 proposals. My work now shifts to bringing the Boost implementation into compliance. * Shipped the Library Fundamentals TS for ISO PDTS (i.e. preliminary) ballot. This TS includes Boost.Any and Boost.Optional. * Voted to start work Library Fundamentals TS 2. The plan is to issue a continuing stream of Library Fundamentals TSes, with work starting on the next TS as soon as content for the current TS freezes. Hopefully Boost developers will submit proposals for this TS too. It will be a good home for small libraries that don't need a whole TS of their own. * Shipped the C++ Extensions for Parallelism TS for ISO PDTS (i.e. preliminary) ballot. * The Library Evolution Working Group (LEWG) voted to base the Networking TS on Boost.ASIO. That was a major surprise, as a Networking Study Group had been trying to build up a Networking TS from many small proposals. But in LEWG polls, support for ASIO was overwhelming, with no one at all voting against. This was a major vote of confidence for Boost.ASIO and Chris Kohlhoff. And several ASIO supporters were not even in the room at the time because Filesystem issues were being worked on elsewhere. The next C++ committee meeting is November 3rd to 8th in Urbana-Champaign, IL, USA. As always, Boosters welcome. --Beman

27 78

[rational] Inadvertent construction from double
by Andrzej Krzemienski 25 Jul '14

25 Jul '14

Hi, I have encountered something I consider a bug in boost::rational's interface. Its documentation discusses in detail why conversion from double is not supported, but the following code works fine: #include <iostream> #include <boost/rational.hpp> int main() { double d = 31.82; boost::rational<int> r = d; std::cout << r << std::endl; } With the following result: 31/1 It just discards the fractional part. Such conversion is really confusing an I claim should be explicitly deleted. Regards, &rzej

3 4