- Boost-users - lists.preview.boost.org

Boost.Spirit. Karma: Kleene star with space separator
by Matwey V. Kornilov 01 Mar '16

01 Mar '16

Hello There is an example of usage Keele star with Karma generator: http://www.boost.org/doc/libs/1_60_0/libs/spirit/doc/html/spirit/karma/refe… std::vector<double> v; v.push_back(1.0); v.push_back(2.0); v.push_back(3.0); test_generator_attr_delim("1.0 2.0 3.0 ", *double_, space, v); How could the remaining space be omitted? Is (double_ % space) supposed to be used instead for such cases?

2 3

Re: [Boost-users] [boost] [Fit] upcoming formal review for Boost.Fit
by Paul Fultz II 29 Feb '16

29 Feb '16

On Sunday, February 28, 2016 at 5:28:39 PM UTC-6, Edward Diener wrote: > > On 2/28/2016 4:23 PM, paul Fultz wrote: > > > > > > > > > > On Sunday, February 28, 2016 12:23 PM, Edward Diener < > eldi...(a)tropicsoft.com <javascript:>> wrote: > > > > > >> > >> > >> On 2/27/2016 11:16 AM, Vicente J. Botet Escriba wrote: > >>> Dear Boost community, > >>> > >>> The formal review of Paul Fultz II's Fit library starts on Wednesday, > 2nd March and ends on 13th March. > >> > >> How do I generate the docs or run the tests for my local copy of Fit ? > > > >> > > > > You can build and run the tests by building the check target. For those > > unfamiliar with cmake, first configure the build directory with cmake: > > > > mkdir build > > cd build > > cmake .. > > cd .. > > > > Next build the check target using the native build system(such as make > or > > msbuild). CMake can call the native build system to build the target > 'check', > > like so: > > > > cmake --build build --config Release --target check > > > > Also, the library can be installed by invoking the 'install' target. > > Why is the CMakeLists.txt not in the 'test' subdirectory, since it > appears from your explanation that the file is used for the tests ? > Its used to install the library as well. > > > > > The documentation needs to be built using mkdocs. You can install mkdocs > and > > the boost theme with pip like this: > > > > pip install mkdocs mkdocs-boost > > > > Then to build the documentation, first `setup.py` must be run to extract > the > > documentation and examples from the source code, then `mkdocs` can be > invoked, > > like this: > > > > python setup.py > > mkdocs build -t boost > > > > And the documentation will be in the 'doc/html' directory. > > Please add these explanations to Fit as you are not using Boost build to > build the doc or run the tests. > I will add them. Also, I tried to add an initial Jamfile to build and run the tests as well. I just modified the Jamfile from other boost libraries. However, I haven't figured out how to run the tests yet using bjam to test my Jamfile. I get "error: Did not find Jamfile.jam or Jamroot.jam in any parent directory". I am not sure how I am supposed to run the tests. > > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost >

2 4

[gsoc16] Boost rejected as GSoC 2016 org
by Niall Douglas 29 Feb '16

29 Feb '16

Dear Boost, It is with a heavy heart I write to say that Boost was rejected as an org for Google Summer of Code 2016 by Google. We had our application submitted in time, it was reviewed by three members of the Boost leadership, our ideas list had six solid ideas with an especially solid seventh on the way, we were in very good standing with Google and there was no reason to expect rejection. We have asked for clarification as to why we were rejected, and we shall try to improve our application next year to improve our chances. We recognise that many students and mentors will be extremely disappointed by this news. We share in that disappointment, and all we can say is please try again next year. For those students and mentors who are continuing a previous GSoC on an existing Boost library, there may be a possibility that Boost may be able to fund those continuations this year. Each case will be approached by the steering committee on a case by case basis, and be aware that the standard required for funding by Boost is considerably above that of Google's with an accompanying high and detailed standard of funding application to the steering committee. Contact us privately if you want to know more. On other news we had been expecting to announce today that Bryce Adelstein Lelbach has generously agreed to take over as secondary GSoC admin from Boris Schäling who has served Boost GSoC for something like four years now, so he has definitely earned himself a rest! Our thanks to Boris for his service, and welcome Bryce to the team! Finally, I'd like to thank Jon Kalb who moved heaven and earth as he always does to get the GSoC application submitted in time. Yours, Niall Douglas -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

1 0

C++Now Student/Volunteers Call for Applications
by Jon Kalb 29 Feb '16

29 Feb '16

The Call for Applications for Student/Volunteers for C++Now 2016 (AKA BoostCon X) has been released: http://cppnow.org/2016-conference/announcements/2016/02/23/student-volunteer -program-accepting-applications.html The application submission deadline is March 16th. We are looking for students with a strong interest in C++. The opportunity is open to student of any level or any field of study. Jon Kalb Chair, C++Now 2016

1 0

Re: [Boost-users] Boost.Context stack growing inwards
by Thomas Ziegenhagen 29 Feb '16

29 Feb '16

Hi again, just noticed that the make_fcontext() documentation says that it expects the stack pointer to be at the end or at the beginning, depending on the architecture. So please re-read my last mail as a feature request: If Boost.Context is a platform-independent context switching library, please make its stack pointer parameter also platform-independent. Rationale: Booost.Context knows best on which platform it runs. If the API is supposed to work the same on all supported systems, its parameter should do so, too. Other than that: Sorry for wasting your time. Bye, Thomas

3 2

Boost.Context stack growing inwards
by Thomas Ziegenhagen 29 Feb '16

29 Feb '16

Hi there, I get regular crashes when using Boost.Context after just a few calls to make_fcontext(). I built a minimal example as follows: ---- #include <iostream> #include <vector> #include <boost/context/all.hpp> struct Context { boost::context::fcontext_t c_outside, c_inside; }; Context gContext = { nullptr, nullptr }; void DoIt( intptr_t /*pt*/) { uint8_t test[64]; memset( test, 0xaf, sizeof( test)); std::cout << "DoIt(), Point 1" << std::endl; boost::context::jump_fcontext( &gContext.c_inside, gContext.c_outside, 0, true); std::cout << "DoIt(), Point 2" << std::endl; boost::context::jump_fcontext( &gContext.c_inside, gContext.c_outside, 0, true); std::cout << "DoIt(), Point 3" << std::endl; boost::context::jump_fcontext( &gContext.c_inside, gContext.c_outside, 0, true); } int main() { const size_t StackSize = 16384; std::vector<uint8_t> stack( StackSize, 0xf1); gContext.c_inside = boost::context::make_fcontext( stack.data() + 256, stack.size() - 512, DoIt); std::cout << "main(), Point 1" << std::endl; boost::context::jump_fcontext( &gContext.c_outside, gContext.c_inside, 0, true); std::cout << "main(), Point 2" << std::endl; boost::context::jump_fcontext( &gContext.c_outside, gContext.c_inside, 0, true); std::cout << "main(), Point 3" << std::endl; boost::context::jump_fcontext( &gContext.c_outside, gContext.c_inside, 0, true); std::cout << "main(), Point 4" << std::endl; return 0; } ------ This notable thing is that I provide a stack with additional 256 bytes of safety borders. And it turns out: the provided memory is overwritten way beyond the beginning. The actual designated area is not touched at all, but instead the area before the beginning is overwritten. The only thing I found in the documentation is this: "sp Member: Pointer to the beginning of the stack (depending of the architecture the stack grows downwards or upwards)." which hints that on some system the stack might grow to negative addresses. But up to now I thought that boost.context knows which direction is correct, and adjusts the given pointer accordingly. But apparently it doesn't. Or the environment underwent a drastic change. Here it is Windows 10 64bit, Visual Studio 2015. For readers remembering my last mails: I have verified this also with an "classic" boost build using this command line: b2.exe -a --reconfigure variant=debug,release link=static runtime-link=static --with-context So I'm pretty sure it's not a build issue. Question: is this a bug? Probably not, I'm surely not the first to use Boost.Context, so I wonder what the correct way is to handle this issue. So what do I do about this? Thanks in advance Bye, Thomas

1 0

Boost.Spirit Karma: how to store generator?
by Matwey V. Kornilov 28 Feb '16

28 Feb '16

Hello, After reading Karma tutorial, I still don't understand whether there a way to store generator except auto my_generator = ... I would like to generate text representation for many similar objects and I think that it is worth to use single generate object and pass it to generate_delimited() by const reference. Are there such things like qi::rule<> and qi::grammar for Karma?

2 1

[ sorting_view ] -do not sort arrays, sort iterators instead
by Boris Kats 27 Feb '16

27 Feb '16

The sorting procedure is one of the most usable routine in programming.And all sorting template functions have the same signature:template< class RandomIt, class Compare >void sort( RandomIt first, RandomIt last, Compare comp );with conditions: the type of dereferenced RandomIt must meet the requirements of MoveAssignable and MoveConstructible.It is clear that in the sorting process a lot of records are moving in the memory andwhen these records have a big size, these movements, together with calling constructors, can be very expensive.Solution.The proposed template function sorting_view is free of that problem - the sorting procedureis working (and moving) on tiny objects - iterators. As result of that procedure,the initial array of records is remaining intact; however provided std::vector<int> viewallows indirect access to the sorted array. On many occasions user does not need the sortedarray at all and he/she has a luxury to iterate through sorted and unsorted arrays simultaneously.In case of real needs of sorted array, it can be obtained via other template function apply_view with exactly 2*N movements of the records, where N is the size of initial array.For getting sorted view of arrays of user's defined records the appropriate Compare template function should be supplied.Happy sorting, Boris Kats.

1 0

Help: Errors compiling SESHAT project
by C. Ichongiri 26 Feb '16

26 Feb '16

Hey there, I've been at this for days now and can't seem to find anything to help with this: I got the project at https://github.com/falvaro/seshat and followed the instructions exactly as-is: - Got the *Boost* headers - Have got *g++ *compiler ( versions 5.2, 4.9, 4.7, 4.5, 4.3) and my default *clang++* *- Makefile *is present *P.S.* I'm on *OS X Mavericks*; Used *MacPorts* to install all above gcc versions *except *5.2, which was manually done following this tutorial: https://solarianprogrammer.com/2015/05/01/compiling-gcc-5-mac-os-x/#comment… However, when I attempt to compile it, I get the following errors (attached in the Textfile below). A screenshot image also attached shows the filesystem and path I am working with, from where the error file was created. Honestly, I'm at my wits end now, especially with my being new to C++. ANY helpful insight into this would be MOST APPRECIATED. Much thanks in advance, chiich.

1 0

Build Boost.Context with Visual Studio
by Thomas Ziegenhagen 26 Feb '16

26 Feb '16

Hi there, I'm building the required portions of Boost myself, along with all my other projects. It turned out that even the smallest compiler setting changes lead to strange crashes, some of which only occured on 5% of the client's systems, so I will not use externally built boost libraries anymore. So now I'm building the parts of boost which I require, which works fine so far. The trouble starts when I tried to use Boost.Context. It also contains ASM code, which I now need to build in Visual Studio 2015. VS2015 does not have builtin Asm support, for x64 it never had. So I'm invoking the Microsoft assembler as a custom build step. Command line is as follows: ml64 /Fo path/to/obj/file.obj /c path/to/source/jump_x86_64_ms_pe_masm.asm Documentation is as scarce as usual, but I figured from the filename that jump_x86_64_ms_pe_masm.asm is the correct file for Microsoft Visual Studio, x64. But assembling failed, and to add insult to injury, the error messages are lost somewhere in the output piping process. The complete output reads like this: ------ 1>------ Erstellen gestartet: Projekt: boost, Konfiguration: Debug x64 ------ 1> Microsoft (R) Macro Assembler (x64) Version 14.00.23506.0 1> Copyright (C) Microsoft Corporation. All rights reserved. 1> 1> Assembling: C:\Projekte\DeadPlanet\SourceExt\boost\context\asm\jump_x86_64_ms_pe_masm.asm 1> C:\Projekte\DeadPlanet\SourceExt\boost\context\asm\jump_x86_64_ms_pe_masm.asm(80)ied size 1>: error A2008 : syntax error : FRAME 1> C:\Projekte\DeadPlanet\SourceExt\boost\context\asm\jump_x86_64_ms_pe_masm.asm(81)ied size 1>CUSTOMBUILD : warning A4020: directive ignored outside a procedure 1> C:\Projekte\DeadPlanet\SourceExt\boost\context\asm\jump_x86_64_ms_pe_masm.asm(215 1>CUSTOMBUILD : fatal error A1010: unmatched block nesting : jump_fcontext ------ Please note that the actual error messages are overwritten by the filename - I can only guess at what buffer magic happens there, but I'm pretty sure it's not intended. But that's just a funny anecdote. My actual question is: how do I build Boost.Context in Visual Studio? Is there maybe some way to see the effective command line when building using Boost.Jam? Is this even the right ASM file for x86_64, Visual Studio? Thanks in advance! Bye, Thomas

4 5