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

[interprocess] Determine size of managed_shared_memory
by Kai Benndorf 12 Oct '19

12 Oct '19

Hi all, I want to create a managed_shared_memory in exactly the size I needed. Therefore I do something like this: size = sizeof( common_managed_shared_memory ); size += sizeof( MyClassInSharedMem ); managed_shared_memory segment(create_only, "name", size ); MyClassInSharedMem allocates itself some memory by segment->allocate(). I added this also to the size, but get a boost::interprocess::bad_alloc exception on allocating this additional memory. Are there some magic bytes I forgot to add? Many thanks in advance Kai

3 2

[Range, Phoenix] What am I missing...
by Robert Jones 25 Apr '17

25 Apr '17

Hi Folks Can anyone explain the output of this program... #include <iostream> #include <boost/range/algorithm/copy.hpp> #include <boost/range/counting_range.hpp> #include <boost/range/adaptor/reversed.hpp> #include <boost/range/adaptor/transformed.hpp> #include <boost/phoenix/bind/bind_function.hpp> #include <boost/phoenix/core/argument.hpp> int f( int i ) { return i * 2; } int main( ) { using boost::adaptors::reversed; using boost::adaptors::transformed; using boost::counting_range; using boost::copy; using boost::phoenix::arg_names::_1; copy( counting_range( 1, 5 ) | reversed | transformed( f ), std::ostream_iterator<int>( std::cout, " " ) ); std::cout << std::endl; copy( counting_range( 1, 5 ) | reversed | transformed( bind( f, _1 ) ), std::ostream_iterator<int>( std::cout, " " ) ); std::cout << std::endl; } Which is... 8 6 4 2 1768406272 1768406272 1768406272 1768406272 I'm using Gcc 4.6.2 & Boost 1.53 Thx All.

3 4

[statechart] Passing parameters from event to State Local Storage
by Christophe Bourez 16 Nov '16

16 Nov '16

I need to maintain a parameter into the state local storage. This parameter is initially contained in the event that causes the transition to the target state. I give hereafter a small illustrative example. typename sc = boost::statechart; class EvTest : public sc::event<EvTest> { public: EvTest(std::size_t val) : value(val) {} std::size_t getValue() const { return this->value; } private: std::size_t value; }; class MyStateMachine; class StSource; class StTarget; class StSource : public sc::simple_state<StSource, MyStateMachine> { public: typedef sc::custom_reaction<EvTest> reactions; sc::result react(const EvTest &event) { // How to pass event.getValue() to the target state ? transit<StTarget>(); } }; class StTarget : public sc::simple_state<StTarget, MyStateMachine> { public: StTarget(std::size_t val) : val(value) {} private: std::size_t value; }; Thanks, Christophe

5 6

Re: [Boost-users] Crashing Issue
by swati upadhyaya 04 Nov '15

04 Nov '15

hi I am using like this where RunningThreads_ is vector containing boost thread object pointer(handler).I am using interrupt() for the interruption of thread interruption_point() catching that interruption then joining.everytime its crashing in join() for me but for others who have the same configuration its working fine all of us has windos 8. For me also it was working last week but this week the same piece of code is crashing. :( RunningThreads_[i].handle->interrupt(); RunningThreads_[i].handle->join(); delete RunningThreads_[i].handle; On Thu, Feb 5, 2015 at 9:31 AM, swati upadhyaya <swatiupadhyaya(a)gmail.com> wrote: > RunningThreads_[i].handle->interrupt(); > LOG4CPLUS_INFO(root, "Thread Interrupted for " << > RunningThreads_[i].app_name << " successful"); > RunningThreads_[i].handle->join(); > LOG4CPLUS_INFO(root, "Waiting for thread to exit " << > RunningThreads_[i].app_name << " successful"); > delete RunningThreads_[i].handle; > LOG4CPLUS_INFO(root, "Thread handle for " << > RunningThreads_[i].app_name << " successfully deleted"); > //RunningThreads_.erase(i); > > On Wed, Feb 4, 2015 at 12:10 AM, Vicente J. Botet Escriba < > vicente.botet(a)wanadoo.fr> wrote: > >> Le 03/02/15 09:10, swati upadhyaya a écrit : >> >> In my code join() timed_joined() is crashing, I am using these API >> after interrupt(),Same piece of code is working for others but in my system >> its crashing, >> Is there some dependency problem I am using >> Boost version: 1.55.0 >> OS: Windows 8 >> IDE: Visual Studio 2010 >> >> Hi, >> >> it could help if you post the example and the backtrace. >> >> Which version/OS/compiler use others for which this works? >> >> Vicente >> >> _______________________________________________ >> Boost-users mailing list >> Boost-users(a)lists.boost.org >> http://lists.boost.org/mailman/listinfo.cgi/boost-users >> > >

3 2

the stability of breadth_first_visit in BGL
by breadbread1984 14 Jul '15

14 Jul '15

I am wondering if breadth_first_visit can always get the same sequence of vertex no matter whether the graph is serialized and deserialized again. Thx

4 3

Re: [Boost-users] [IPC Named Mutex]
by Lorenzo Trivelli 19 Jun '15

19 Jun '15

> >One thing you could try...in interprocess's win32_api.hpp, there is another implementation of get_last_bootup_time() which uses WMI instead of the event log (there were warnings in the source about WMI not supporting hibernation/clock changes correctly, so beware). If you define >BOOST_INTERPROCESS_BOOTSTAMP_IS_LASTBOOTUPTIME >it should use that other version...give that a try. (in visual studio Project Properties -> C/C++ -> Preprocessor -> Preprocessor Definitions: add a semi colon ';' then t Thanks Tom, I'll try to fallback to the "old" WMI version (which BTW worked in the 1.44 version I we used before) I'd also be glad to fix it by myself and so help boost developement, , but I do not completely understand the usage of the system boot time... If boost needs in some way a tmestamp to differentiate things, in my opinion there are plenty of them to use instead of the last boot time. Obviously it has been done for a reason, but I cannot understand why :-D Best regards Lorenzo

6 11

Some strange boost headers errors
by alfonso santimone 15 May '15

15 May '15

Hi guys, i'm a boost newbie. I've got to include boost libraries in the include path of a VisualStudio 2012 project. When i try to compile i have all these errors. Every errors is related to missing headers ( boost ones and even standard Win ones ) and to synthax errors depending on missing headers i guess. Do someone have any idea on what's wrong here? I just post here a few lines of errors, but the other ones are all of the same kind Error 1 error C2061: syntax error : identifier 'boost' C:\boost_1_57_0\boost\core\ checked_delete.hpp 24 1 csound~ Error 2 error C2059: syntax error : ';' C:\boost_1_57_0\boost\core\checked_delete.hpp 24 1 csound~ Error 3 error C2449: found '{' at file scope (missing function header?) C:\boost_1_57_0\boost\core\checked_delete.hpp 25 1 csound~ Error 4 error C2059: syntax error : '}' C:\boost_1_57_0\boost\core\checked_delete.hpp 67 1 csound~ Error 5 error C2054: expected '(' to follow 'using' C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\include\cstddef 19 1 csound~ Error 6 error C2061: syntax error : identifier 'using' C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\include\cstddef 19 1 csound~ Error 7 error C2061: syntax error : identifier 'boost' C:\boost_1_57_0\boost\smart_ptr\detail\sp_nullptr_t.hpp 23 1 csound~ Error 8 error C2059: syntax error : ';' C:\boost_1_57_0\boost\smart_ptr\detail\sp_nullptr_t.hpp 23 1 csound~ Error 9 error C2449: found '{' at file scope (missing function header?) C:\boost_1_57_0\boost\smart_ptr\detail\sp_nullptr_t.hpp 24 1 csound~ Error 10 error C2059: syntax error : '}' C:\boost_1_57_0\boost\smart_ptr\detail\sp_nullptr_t.hpp 41 1 csound~ Error 11 error C2054: expected '(' to follow 'using' C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\include\cstdlib 19 1 csound~ Error 12 error C2061: syntax error : identifier 'using' C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\include\cstdlib 19 1 csound~ Error 13 error C2061: syntax error : identifier 'abort' C:\Program Files (x86)\Microsoft Visual Studio many thanks in advance bests alfonso www.elgallorojorecords.com soundcloud.com/alfonsosantimone www.facebook.com/alfonsosantimone

5 11

Re: [Boost-users] lexical_cast between double and string slow in Visual Studio 2013
by David Roberts 07 May '15

07 May '15

> That issue is unknown. I'd really appreciate the investigation. I have done some more investigation, and there are two factors that only cause the slowness when they both occur together. > Try excluding the lexical_cast from test, I have a feeling that this is only MSVC related issue: > > #include <sstream> > #include <string> > > int main (int, char **) > { > for (double count = 0.0; count < 1000000.0; count += 1.41) > { > std::stringstream ss; > ss << count; > std::string result = std::move(ss.str()); > ss.str(std::string()); > > ss << result; > ss >> count; > } > > return 0; > } > Running your test program does not exhibit the problem. It runs in around 3 seconds on my machine when built with either Visual Studio 2010 or Visual Studio 2013. However, changing it very slightly to match more closely what lexical_cast does internally does recreate the problem: #include <sstream> #include <string> int main (int, char **) { for (double count = 0.0; count < 1000000.0; count += 1.41) { std::stringstream ss; ss.unsetf(std::ios::skipws); ss.precision(17); ss << count; std::string result = std::move(ss.str()); ss.str(std::string()); ss << result; ss >> count; } return 0; } The effect of setting the precision to 17 is that lots of 9s appear in the string representations. (The number 17 is what boost::detail::lcast_get_precision(double*) chooses.) Without the precision call the contents of the string called result start off like this: 0 1.41 2.82 4.23 5.64 7.05 8.46 9.87 11.28 12.69 With precision set to 17 they start off like this: 0 1.4099999999999999 2.8199999999999998 4.2299999999999995 5.6399999999999997 7.0499999999999998 8.4599999999999991 9.8699999999999992 11.279999999999999 12.69 This happens for both Visual Studio 2010 and Visual Studio 2013. Then the next difference is that Visual Studio 2013 spends a lot longer handling all the extra 9s. Changing the program so that the double is converted to a string using std::stringstream without a precision call and then back to double using lexical_cast takes about 3 seconds for both Visual Studio 2010 and Visual Studio 2013. It is the combination of having all the extra 9s to parse and using Visual Studio 2013 that makes the test using lexical_cast to go both ways slow. Both Visual Studio 2010 and Visual Studio 2013 do the conversion by calling std::num_get<char,std::istreambuf_iterator<char,std::char_traits<char> > >::do_get() which then calls a function called _Stodx() which is implemented in xstod.c. This function is very different for the two versions. In Visual Studio 2010 it's a relatively thin wrapper around the C function strtod(). In Visual Studio 2013 _Stodx() has got a completely new implementation that's generated by #including xxstod.h with some macros defined. The original C function strtod() is much faster than the new _Stodx() when there are lots of 9s at the end of the strings being parsed. This modification to the program: #include <sstream> #include <string> #include <stdlib.h> int main (int, char **) { for (double count = 0.0; count < 1000000.0; count += 1.41) { std::stringstream ss; ss.unsetf(std::ios::skipws); ss.precision(17); ss << count; std::string result = std::move(ss.str()); ss.str(std::string()); ss << result; char *endptr; count = strtod(ss.str().c_str(), &endptr); } return 0; } has a runtime of about 3 seconds even though it's got to cope with all the 9s. I guess only someone from Microsoft or Dinkumware could comment on why _Stodx() was reimplemented. But the other thing is that by setting precision to 17 lexical_cast is bloating the string representations of the doubles with lots of 9s in both Visual Studio 2010 and Visual Studio 2013. Setting precision to 15 instead prevents this, and makes the original test run faster even with Visual Studio 2013 (about 4 seconds rather than 10). Regards, David

5 4

[serialization] std::shared_ptr with Boost >= 1.53
by Rüdiger Berlich 04 May '15

04 May '15

Hi there, I need to support various versions of Boost, but am in the process of porting our entire code base to C++11. This involves replacing those constructs of Boost that are now in the standard with their C++11-counterparts. A prime example is std::shared_ptr. However, most of our code needs to be serializable. I know that serialization of std::shared_ptr is possible with Boost 1.58. But 1.53 (the oldest version I need to support) cannot serialize std::shared_ptr . Is there any reason not to include the 1.58-Version of #include <boost/serialization/shared_ptr.hpp> instead of the older version, if I detect a Boost-version < 1.58 ? Thanks and Best Regards, Beet

4 12

Boost.Cgi Status
by Michael Ainsworth 01 May '15

01 May '15

What is the status of Boost.Cgi by Darren Garvey? It seems that the library hasn't been accepted and it's now 2015 - at least 7 years after last Boost Users mailing list post regarding its status. Michael

2 2

[gsoc15] This year's GSoC students
by Niall Douglas 27 Apr '15

27 Apr '15

Dear Boost, It is our pleasure to announce this year's winning GSoC students and projects: 1. Damian Vicino Topic: Safe Float (boost::safe_numerics<float>) Mentor: Robert Ramey 2. Rajaditya Mukherjee Topic: Boost uBLAS EigenSolver Mentor: David Bellot 3. Anurag Ghosh Topic: Boost Document Library Mentor: Antony Polukhin 4. Nikhar Agrawal Topic: Boost.Fixed-Point Mentor: Paul A. Bristow 5. Benedek Thaler Topic: Enhanced vector and deque containers Mentor: Thorsten Ottosen 6. Louis Dionne Topic: Improved compile-time associative data structures for Hana Mentor: Joel Falcou 7. Jakub Szuppe Topic: Improving Boost.Compute Mentor: Kyle Lutz Congratulations to these students for passing an exceptionally tough contest this year, and our thanks to the above mentors for making themselves available. Finally, thank you Google for another year of funding and to those open source orgs who released duplicate students to us, we appreciate it! Niall and Boris --- Boost C++ Libraries Google Summer of Code 2015 admin https://svn.boost.org/trac/boost/wiki/SoC2015

1 0

Re: [Boost-users] boost examples
by Max 27 Apr '15

27 Apr '15

----- Original Message ----- From: mloskot <mateusz(a)loskot.net> To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] boost examples Date: 2015-04-24 18:01 mloskot wrote > On 23 April 2015 at 11:44, Trek < > trek830@ > > wrote: >> Is there a central link where all official boost examples are hosted? > > No. You may check http://theboostcpplibraries.com/ for unofficial ones. ----- -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org Member of ACCU, http://accu.org The book, Beyond the C++ Standard Library, also used to be a very good starting point of my understanding the boost libraries. Max

1 0

[Pyhton] (re)binding class instance in python object
by Tamas.Ruszkai＠leica-geosystems.com 27 Apr '15

27 Apr '15

Hi, I have a plain C++ class which I want to exposed to python. The pyhton object accesses the C++ class via smart pointer. class Sensor : public boost::enable_shared_from_this<Sensor> { public: Sensor(int port); ~Sensor() void Open(); void SendCommand(const std::string& command); void Close(); private: int _port; }; auto sensorClassTypeObject = boost::python::class_<Sensor, boost:: shared_ptr<Sensor>>("Sensor", boost::python::init<int>()) .def("Open", &Sensor::Open) .def("SendCommand", &Sensor::SendCommand) .def("Close", &Sensor::Close); The question is: if I already have one instance of the C++ class (in a dependency injection container) then how can I create in the C++ part an instance of the python wrapper so that it does not create a new instance of Sensor, but uses my existing Sensor instance? Then I would put this instance into one of the python modules (this part would be made in C++) inside the python interpreter to be able to access it via script. Something like that: shared_ptr<Sensor> sensorInstance = DIContainer.Resolve<Sensor>(); boost::object pythonInstance = sensorClassTypeObject(sensorInstance); pythonInterpreterWrapper.AddToModule("__main__", pythonInstance); Best Regards, Tamas

1 0

[msm] Event does not get processed after exiting an interrupt state
by Chrisopher Vogl 27 Apr '15

27 Apr '15

Hi all! I got a state machine with 2 regions. The second region has two states ("Run" and "Interrupt"), one is an interrupt state. The region starts in the non interrupt state, just like in the MSM example "Orthogonal regions, terminate state, event deferring". The event called Ev_Resume leads to a transition from state Interrupt back to state Run. In on_entry() of Run I fire an event which never gets processed. Is at that time the FSM still interrupted, i.e. event processing still blocked? Christopher

2 1

Re: [Boost-users] [boost] [test] boost.test owner unresponsive to persistent problems for multiple years
by Paul A. Bristow 24 Apr '15

24 Apr '15

> -----Original Message----- > From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Richard > Sent: 17 March 2015 17:20 > To: boost(a)lists.boost.org > Subject: Re: [boost] [test] boost.test owner unresponsive to persistent problems for multiple years > > Another quarter has gone by and another Boost release is prepared for beta and I see *no* changes to > Boost.Test listed in the release notes.> > So here we are, waiting another 3 months for *simple* changes to be reflected in this library while the > maintainer insists that the fixes are available, yet they continue not to be deployed into any shipping release. It is indeed really deplorable that we don't have Boost.Test updates in a release. Though in mitigation I note that we are really struggling to get out a GIT-driven release at all, (and some of the new troubles are with asynch-exceptions in Boost.Test. See this thread Re: [boost] Running b2 on develop needs asynch-exceptions=on.) However, Richard's hard work on improved docs have been refined and completed by Raffi Enficiaud. Many bug fixes are in the develop branch (including some very new and prompt bug fixes, for example https://svn.boost.org/trac/boost/ticket/11054). I also understand that the fear of Boost.Test updates causing trouble with other libraries, and worse with users test, is a cause for caution in a release version. So it would be really good if *lots more users could download and use the version in the Boost.Test develop branch* so we can get current user feedback. (My experience is good using this, and the test matrix is also good). You can download just Boost.Test either using GIT or as a zip from https://github.com/boostorg/test/tree/develop and substitute it for the contents of the current release modular-boost/libs/test folder (Don't forget to rebuild the Boost.Test library unless you only use the included version). If nothing else, you will find Raffi's shiny new Boostbook docs finally allow you to find what you want to know without frustration. I'd very much like to see this new docs version in the 1.58 documentation release (despite any new features not being in the code release). Paul --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830

5 5

[log] Possible to explicitly disable AVX2?
by Jason Roehm 24 Apr '15

24 Apr '15

I am building Boost.Log on a relatively new machine whose compiler and CPU both support the AVX2 instruction set. Boost.Log detects this at build time and configures its compiler flags accordingly to use the AVX2 instruction set. I'd like to use the resulting binaries, however, on older systems that do not have AVX2 support. Is it possible to explicitly disable this at build time? I didn't see any mention of it in the documentation, and my attempts to parse the Jamfile's intentions were not successful. Thank you. Jason

1 0

[nowide] Cannot end input using ^Z/^D on Windows
by Yuan Yao 24 Apr '15

24 Apr '15

3 2

boost examples
by Trek 24 Apr '15

24 Apr '15

Is there a central link where all official boost examples are hosted? thanks,

3 2

Boost.Thread Continuation future with executor blocking in destructor
by Konrad Zemek 23 Apr '15

23 Apr '15

Hi, When creating a continuation future with future<>::then(), and the policy is boost::launch::async, the created future's destructor blocks, like a future created by boost::async, and probably for the same reasons (as outlined by the standardization committee in n3679). The same behavior is coded into continuation futures' destructor when using an executor. Why is it needed here? The situation with executor-run continuations is a little different, as even when the future is destroyed, the lifetime of running job is still bound to the executor. My use case: I've coded a network communication stack that returns to the caller a future<NetworkResponse>. I've previously used std::async(std::launch::deferred, ...) to transform the future's content before returning it to the caller (bytes -> protobuf -> internal object), and I consider such manipulation of a future value to be a very powerful feature. I've used std::launch::deferred to reduce the number of running threads, but the downside is that the client can't wait for the future value with a timeout. On the other side of the spectrum is std::launch::async, which would run a new thread - per pending communication - that would do little more than block. boost::future<>::then is a fantastic fit for my use case, as I can use my boost::asio::io_service as an executor and let my communication stack's threads do the work without having them block on future.get() to first retrieve the result. The caller can then call future<>::wait_for() to wait for the reply with a custom timeout. This being network communication, though, a reply message may never arrive - the corresponding promise will eventually be destroyed by the stack, but I can't have users block on the future's destructor until that happens, after they have already decided that the reply is no longer worth waiting for. Please advise if there's a workaround for this behavior that doesn't involve me distributing a custom version of Boost.Thread with my binaries? :) Konrad

5 6

[asio] What are the enhancements for Asio in 1.58
by Aaron Levy 22 Apr '15

22 Apr '15

I am sorry if this has been already asked. Wanted to get a head start on Asio 1.58, having heard that it's a significantly enhanced library. -- Aaron Levy aaron.levy(a)yandex.com

3 2

[multi_index] Announcing preview of ranked indices
by Joaquin M Lopez Munoz 22 Apr '15

22 Apr '15

Hi, It's been 11 years since first proposed, but here it is at last. I'm releasing a prereview of ranked indices for Boost.MultiIndex: struct person { int age; std::string name; }; typedef multi_index_container< person, indexed_by< ranked_non_unique<member<person,int,&person::age> >, ordered_non_unique<member<person,std::string,&person::name>>>> multi_t; multi_t m={{40,"Joe"},{25,"Jill"},{30,"Kurt"},{32,"Sue"}}; auto it=m.emplace(31,"Maggie").first; std::cout<<m.rank(it)<<" persons younger than "<<it->name<<"\n"; auto n=m.size()/2; std::cout<<n<<" persons are less than "<<m.nth(n)->age<<" years old\n"; Ranked indices add a bunch of extra rank-related capabilities to the interface of ordered indices. The rank of an element is its numerical position in the index. nth(i) returns an iterator to the element with rank i, whereas rank(it) is the inverse operation. Both execute in log(n) time. Additionally, the member functions find_rank lower_bound_rank upper_bound_rank equal_range_rank range_rank behave as their "_rank"-less counterparts except they return ranks rather than iterators. One drawback of ranked indices wrt ordered indices (other than their slower perfomance and higher memory consumption) is that deletion of elements is log(n) (in ordered indices it is constant time). Download lib preview: http://tinyurl.com/kemwk8q Tutorial: http://tinyurl.com/q36c9f7 Reference: http://tinyurl.com/pvoulgr For people interested in this, I'd appreciate if you could download the source, copy it on top of Boost 1.58 (1.57 should work as well), play a bit with the new feature and report your results. Also, opinions on naming are welcome. Target version for releasing is Boost 1.59, so we have plenty of time to discuss the design before it is final. Thank you, Joaquín M López Muñoz Telefónica

1 0

Which is the effective way for data transfer for Interprocess shared memory ?
by Kalyan Chakravarthy Gudimella 22 Apr '15

22 Apr '15

Hi, I am currently evaluating boost interprocess library for using shared memory. I found two ways to transfer complex data structures. 1. Creating data structures directly in shared memory. E.g. http://www.boost.org/doc/libs/1_58_0/doc/html/interprocess/allocators_conta… class complex_data{ int id_; char_string char_string_; int_vector_vector int_vector_vector_; public: //Since void_allocator is convertible to any other allocator<T>, we can simplify //the initialization taking just one allocator for all inner containers. complex_data(int id, const char *name, const void_allocator &void_alloc) : id_(id), char_string_(name, void_alloc), int_vector_vector_(void_alloc) {} //Other members...}; 2. Serializing data into bufferstream and deserializing it. E.g.http://www.boost.org/doc/libs/1_58_0/doc/html/interprocess/streams.html My initial trial shows that streaming to bufferstream took 7 times more time than using direct shared structures. Can you please help me to choose the effective way between these two approaches? thanks, Kalyan

1 0

[MPL][Config] Can no longer pre-generate headers for MPL-containers with more than 50 elements.
by Deniz Bahadir 22 Apr '15

22 Apr '15

Hello everyone, While playing around with the current Boost release-candidate (1.58.0-RC3) I noticed that pre-generating MPL-headers for MPL-containers with more than 50 Elements seems no longer possible. Up till at least Boost 1.55.0 I was able to pre-generate these MPL-headers using the python-scripts from Boost-source ([1]) with the help of a bash-script which I already described here [2]. Internally, these python-scripts seem to use GCC to generate these MPL-headers. They also seem to partially circumvent Boost.Config by using custom user.hpp files located in subdirectories of [3] and defining BOOST_NO_CONFIG and some other macros therein. However, this does not seem to please Boost.Config so that compiler-errors ([4]) occur. Defining the macro BOOST_CONFIG_ALLOW_DEPRECATED as [4] suggests seems not to help. It just silences the warnings but does not generate proper files. (It actually erases the content of almost all header-files in subdirectories of [5].) Does anyone know how to workaround or better fix this? Or does anyone know who to talk to, to get these problems fixed? Also, I would suggest, that documentation for these python-scripts are added to the documentation of Boost.MPL. Best regards, Deniz References: [1] ${BOOST_SOURCE}/libs/mpl/preprocessed/ [2] http://stackoverflow.com/a/20660264/3115457 [3] ${BOOST_SOURCE}/libs/mpl/preprocessed/include/ [4] #error "You are using a compiler which lacks features which are now a minimum requirement in order to use Boost, define BOOST_CONFIG_ALLOW_DEPRECATED if you want to continue at your own risk!!!" [5] ${BOOST_SOURCE}/boost/mpl/aux_/preprocessed/

3 5

[SPAM] from: giridhar
by giridhar 22 Apr '15

22 Apr '15

Greetings boost http://findislamicservices.com/reduce.php?silver=aswydt7xv2r0enm3 giridhar Sent from my iPhone

1 0

sliding window containing n seconds of data
by Lane 22 Apr '15

22 Apr '15

I'm looking for a way to examine an array of object structures for an adjustable window of n seconds. My application reads objects at a high rate (which I'll have to throttle), and I'd then like to put them onto an array. My thinking is to assign a timer on each object that is initialized to n seconds and once the timer expires, the object is removed from the array, but while it's on the array, I'll iterate over the objects looking for the info I need. I put this out on the boost list as I suspect boost has the mechanisms to handle this and someone could suggest a good way of going about it. Any help much appreciated.

5 5