- Boost - lists.preview.boost.org

[threads / signals2] Win events replace by boost signals (threadsafe)
by Fu ji 26 Mar '15

26 Mar '15

Hello, I have to change win32 events with something portable so I decided to use boost.signals2. Right now I have something like: ret = WaitForMultipleObjets{ switch(ret) { case Timeout: something; break; case Event1: something; break; case Event2: something; break; }} and I think that the good idea is to replace this with something like that: for(;;){ Execute code from timeout, if event occurs interrupt and execute code which is responsible for event handling} but for test I write this: boost::signals2::signal<void()> signal; void SendSignal() { std::cout << "Send signal"; boost::this_thread::sleep_for(boost::chrono::milliseconds(200)); signal(); boost::this_thread::sleep_for(boost::chrono::milliseconds(2000)); } int main() { boost::thread t1(SendSignal); for (;;) { std::cout << "."; boost::this_thread::sleep_for(boost::chrono::milliseconds(100)); } auto c = signal.connect([]() { std::cout << "Signal receive" << std::endl; boost::this_thread::sleep_for(boost::chrono::milliseconds(1000)); }); return 0; } unfortunately this example is not working, what I've done wrong ? Best regards

6 10

Server certificate expired on svn.boost.org
by William Gallafent 26 Mar '15

26 Mar '15

“The certificate expired on 2015-03-22 02:33” … ! -- Bill Gallafent.

2 1

Removing auto_ptr/etc. from Boost
by Stephan T. Lavavej 25 Mar '15

25 Mar '15

Hi Boost devs, I need your help to get rid of auto_ptr forever. I want to implement C++17's N4190 "Removing auto_ptr, random_shuffle(), And Old <functional> Stuff", although it's going to take a while. In VC 2015, the removal will be opt-in (requested via a macro; I've already checked this in). My plan is for the removal to be opt-out in the version after that, and unconditional in the version after that. To achieve the opt-in removal, I've already eliminated the STL's internal dependencies on this stuff (nothing derives from unary_function/binary_function anymore, and shuffle() isn't directly implemented with random_shuffle() anymore). To prepare for the future of opt-out removal, I've also been removing usage from the compiler and other stuff. However, Boost is used in our tests in a number of places. What I'd like to ask is for Boost to begin removing its usage of this stuff (unconditionally or for VC 2015+, your pick). According to my understanding, only unary_function/binary_function and auto_ptr are used extensively by Boost, with the other stuff being used rarely or not at all. Thanks, Stephan T. Lavavej Senior Developer - Visual C++ Libraries

10 23

[iterator] Bug #7526
by Claas 25 Mar '15

25 Mar '15

Hi! I was wondering, how the iterator developers intend to proceed with ticket #7526 (https://svn.boost.org/trac/boost/ticket/7526) Two fixes are available and seemingly just wait to be applied. One fix has been available for two years, and a more sophisticated (probably preferable) fix has been submitted 9 month ago. Has this simply been forgotten or are there any reasons, not to apply one of the available patches ?. Since I require the requested functionality, I would like to press the issue. If more support is required to fix this, please let me know. Since two years I have had to patch each version of boost manually to deploy this fix, which is a little frustrating. So I would gladly contribute, if this is required. Any update on the issue would be appreciated. Regards Claas

1 0

[TypeSort] Automatic type sorting
by costis glynos 25 Mar '15

25 Mar '15

Hello,Is there any interest in a library which automatically sorts types from smallest to largest at compile time?The benefit would be the automatic Data Structure Alignment and potential improvement in performance.Foo<int,bool,Custom16ByteType,char,double,short> foo_1; //normal Foo<int,bool,Custom16ByteType,char,double,short> foo_2; //using the TypeSort output: size of foo_1 = 48 size of foo_2 = 32 Kind Regards, Constantinos

6 17

Messages from list marked as spam
by Matus Chochlik 25 Mar '15

25 Mar '15

On Wed, Mar 25, 2015 at 1:33 PM, Christian Hägele <haegele(a)teamviewer.com> wrote: > Am 24.03.2015, 19:27 Uhr, schrieb Marcel Raad <raad(a)teamviewer.com>: > > Email from certain people on the list is >>> marked as spam by gmail: "Why >>> is this message in Spam? It has a from >>> address in teamviewer.com but >>> has failed teamviewer.com's required >>> tests for authentication. " >>> >> >> I guess that's me. Probably because I use >> Gmane's web interface to post messages >> instead of my e-mail account. >> > > I'm using my e-mail account to write this mail from the same domain as > Marcel does. > I hope this mail is not marked as spam. > > I would appreciate if somebody would give feedback if this mail is marked > as Spam by Gmail or similar providers. > It gets into spam in my gmail account (together with some messages sent from yahoo.com)

1 0

Boost 1_58_0_rc1 is available for testing
by Marshall Clow 25 Mar '15

25 Mar '15

Release candidate files for 1.58.0 beta 1 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. IMPORTANT NOTE: There is a bug with the build scripts; you have to specify the address-mode and architecture to b2. I used: ./b2 address-model=64 architecture=x86 to test this. The files (and associated md5s) are: MD5 (boost_1_58_0_b1_rc1.7z) = 302c7dfc917227843d24beed33ccc99c MD5 (boost_1_58_0_b1_rc1.tar.bz2) = d7d030e85bf5534a328c108c62a7fb0e MD5 (boost_1_58_0_b1_rc1.tar.gz) = ec90cd23bdc99c5eaf88245ea94a28e0 MD5 (boost_1_58_0_b1_rc1.zip) = dc8379fb95c84fe2fca53a4b2c96da23 Thanks! -- The release managers

13 18

Re: [boost] [test] boost.test owner unresponsive to persistent problems for multiple years
by Raffi Enficiaud 24 Mar '15

24 Mar '15

Le 18/03/15 14:43, Edward Diener a écrit : > On 3/18/2015 5:49 AM, Paul A. Bristow wrote: > > Do I have to rebuild the Boost.Test library to get the new docs ? > Because the first thing I did was to try to view the new docs by opening > index.html only to find that there was no html documentation. Then I > tried 'b2 toolset=gcc-4.9.2' for building Boost.Test and received: > > Performing configuration checks > > - symlinks supported : yes > error: Unable to find file or target named > error: 'dyn_ut_example.cpp' > error: referred to from project at > error: '../../libs/test/example' > > It does not appear that the 'develop' branch is ready for me at all. This is the location of the new documentation: http://www.boost.org/doc/libs/develop/libs/test/doc/html/index.html I do not know about the update frequency In order to build the doc: cd $boost/libs/test/doc ../../../bjam -sDOCBOOK_XSL_DIR=/some/path/docbook-xsl-1.78.1/ -sDOCBOOK_DTD_DIR=/some/path/docbook-xml-4.2/ Doxygen should be in the $PATH. The previous command will build whatever is necessary. Best, Raffi

6 8

[build] broken documentation links
by dominic meiser 24 Mar '15

24 Mar '15

Hi, The links to the documentation (html and pdf) at http://www.boost.org/doc/libs/1_57_0/tools/build/index.html are broken. Cheers, Dominic

1 0

[Hana] Informal review request
by Louis Dionne 24 Mar '15

24 Mar '15

Dear Boost, As some may be aware of, I am currently working on a metaprogramming library called Hana, with the intention of proposing it for inclusion in Boost. The purpose of that library is to act as a toolbox for expressing computations on both types (like the MPL) and heterogeneous values (like Fusion). The library is built around C++14 idioms and implementation techniques to maximize expressiveness and performance. I am now requesting feedback from the community, with the intention of asking for a formal review in the next months. A similar review was asked for in last August. The library has undergone several modifications since then, both to address issues raised during the review and for general improvement. Here are some issues that were raised during the review and addressed: - Usage of names and terms unknown to C++ programmers: Efforts were made to make this better, and several functions were renamed (`fmap` is now `transform`). When possible, the documentation also uses terms more familiar to C++ programmers, like concept instead of "type class". - The order of the arguments to some algorithms was unfortunate for C++. It was consistent with Haskell, but it turned out to be cumbersome in C++. This is changed in most places. - Inability to easily implement individual algorithms: This is fixed, and algorithms are now standalone structures using tag-dispatching, almost exactly as in Fusion. - Lack of a good introductory tutorial: A lot of work has gone into improving both the tutorial and the reference documentation. - Lack of support for mainstream compilers: The library is now almost fully functional with Clang 3.5. A GCC 4.9 port with reduced functionality is also underway on the `redux` branch. The library is available at [1] and the documentation at [2]. Comments should be directed to this mailing list, while bugs and other similar problems should be directed to the GitHub issue tracker. Please participate, especially if you have interest and/or experience in metaprogramming; after all, you represent the target audience for Hana. Thank you, Louis Dionne [1]: https://github.com/ldionne/hana [2]: http://ldionne.github.io/hana/

13 48