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

[filesystem] problem: is_regular_file and deduplified files (reparse+sparse)
by Paul Harris 24 Jul '15

24 Jul '15

Hi guys, I'm seeing a lot of failures all of a sudden, its a serious problem. I imagine some of you may start seeing the same failures too very soon. I'm seeing it with boost 1.58.0. There is a related bug already entered here: https://svn.boost.org/trac/boost/ticket/11057 I can't seem to log on and update this ticket. But the problem extends further than that ticket. Windows Server 2003 support has been dropped by Microsoft, and a lot of IT depts around the world are switching over to the latest Windows Server. With this server comes the new "dedup" feature, that can automatically deduplify files. This happens on a schedule, eg 2am saturday. So suddenly we are getting messages of failures of software from all over the place, due to fs::is_regular_file() Deduped files have the REPARSE and SPARSE flag set. On the command line, you can run FSUTIL REPARSEPOINT QUERY and the "Reparse Tag Value" is 0x80000013 Which is a relatively new flag known as IO_REPARSE_TAG_DEDUP https://msdn.microsoft.com/en-us/library/windows/desktop/aa365740%28v=vs.85… These files act as normal files, you can fopen and fread them, so I assume they should be treated almost like symlink by boost... perhaps not quite a symlink because I assume the "lstat" link properties are identical to the file's stat properties. Typically, I iterate over directories and only process files if fs::is_regular_file(filename) is true. I wrote some code to check what the properties were on these files, and its not any of the possible enums detected by file_status::type(). ideas? Best regards, Paul

2 5

Re: [Boost-users] problem of getting vertex_index_t property
by breadbread1984 24 Jul '15

24 Jul '15

Thx for your reply. But I use vecS to store vertices instead of setS. The setS is for storing edges. There should be something else going wrong. 在 2015年7月23日星期四 10:32:28，boost-users-request@lists.boost.org 写道： > Send Boost-users mailing list submissions to > boost-users(a)lists.boost.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.boost.org/mailman/listinfo.cgi/boost-users > or, via email, send a message with subject or body 'help' to > boost-users-request(a)lists.boost.org > > You can reach the person managing the list at > boost-users-owner(a)lists.boost.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Boost-users digest..." > > > Today's Topics: > > 1. Re: [interval] Errors using transc.hpp WAS: Power (Sensei) > 2. problem of getting vertex_index_t property with BGL > (breadbread1984) > 3. Re: problem of getting vertex_index_t property with BGL > (Jeremiah Willcock) > 4. Re: Boost.DateTime and leap year/leap seconds (Auer, Jens) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 23 Jul 2015 10:03:47 +0200 > From: Sensei <senseiwa(a)gmail.com> > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] [interval] Errors using transc.hpp WAS: > Power > Message-ID: <55B09FE3.20108(a)gmail.com> > Content-Type: text/plain; charset=utf-8; format=flowed > > Dear all, > > I've tried to move beyond simple exp/log functions, but this problem > > > /usr/local/include/boost/numeric/interval/transc.hpp:47:42: No member > > named 'log_down' in 'boost::numeric::interval_lib::rounded_math<double>' > > > > /usr/local/include/boost/numeric/interval/transc.hpp:34:16: No member > > named 'exp_down' in 'boost::numeric::interval_lib::rounded_math<double>' > > arises with *all* of the functions contained in transc.hpp, and I don't > know what I'm doing wrong here. > > Can anyone help me? > > > Thanks! > > > ------------------------------ > > Message: 2 > Date: Thu, 23 Jul 2015 18:25:39 +0800 > From: breadbread1984 <breadbread1984(a)163.com> > To: boost-users(a)lists.boost.org > Subject: [Boost-users] problem of getting vertex_index_t property with > BGL > Message-ID: <2807116.uu1eRmarTQ@xieyi-paf4> > Content-Type: text/plain; charset="utf-8" > > I am using boost graph library. I found there is a built in property > vertex_index_t corresponding to every vertex from the document > [here](http://www.boost.org/doc/libs/1_58_0/libs/graph/doc/adjacency_list.h > tml). But when I get the vertex_index_t property the compiler prompt the > following error: > > CooperativeGraph.h:59:36: required from here > /usr/include/boost/graph/detail/adjacency_list.hpp:2498:29: error: forming > reference to void typedef value_type& reference; > ^ > /usr/include/boost/graph/detail/adjacency_list.hpp:2499:35: error: forming > reference to void typedef const value_type& const_reference; > ^ > /usr/include/boost/graph/detail/adjacency_list.hpp:2502:47: error: forming > reference to void <Graph, value_type, reference, Tag> type; > ^ > /usr/include/boost/graph/detail/adjacency_list.hpp:2504:53: error: forming > reference to void <Graph, value_type, const_reference, Tag> const_type; > ^ > CooperativeGraph.cpp: In member function ?void > CooperativeGraph::getProperties()?: CooperativeGraph.cpp:384:35: error: no > matching function for call to ?get(boost::vertex_index_t, Graph&)? > vertex_index = get(vertex_index,g); > ^ > I defined the data structure as follows > > typedef property<vertex_BatteryLevel_t,int, > property<vertex_ObservationHistory_t,deque<Observation>, > property<vertex_name_t,uuid> > > > vertex_state; > > typedef property<edge_QFunction_t,QTable, > property<edge_Eligibility_t,Eligibility> > > > edge_qfunction; > > typedef adjacency_list< > vecS,setS,directedS, > vertex_state, > edge_qfunction > > > Graph; > > Does anyone know what I am doing wrong? Why can't I get the vertex_index_t > property. Thanks! > > > > ------------------------------ > > Message: 3 > Date: Thu, 23 Jul 2015 14:06:03 +0000 (UTC) > From: Jeremiah Willcock <jewillco(a)yahoo.com> > To: "boost-users(a)lists.boost.org" <boost-users(a)lists.boost.org> > Subject: Re: [Boost-users] problem of getting vertex_index_t property > with BGL > Message-ID: > <983493185.1183146.1437660363876.JavaMail.yahoo(a)mail.yahoo.com> > Content-Type: text/plain; charset=UTF-8 > > >________________________________ > > > > From: breadbread1984 <breadbread1984(a)163.com> > > > >To: boost-users(a)lists.boost.org > >Sent: Thursday, July 23, 2015 4:25 AM > >Subject: [Boost-users] problem of getting vertex_index_t property with BGL > > > > > >I am using boost graph library. I found there is a built in property > >vertex_index_t corresponding to every vertex from the document > >[here](http://www.boost.org/doc/libs/1_58_0/libs/graph/doc/adjacency_list. > >html). But when I get the vertex_index_t property the compiler prompt the > >following error: > > > >CooperativeGraph.h:59:36: required from here > >/usr/include/boost/graph/detail/adjacency_list.hpp:2498:29: error: forming > >reference to void> > > typedef value_type& reference; > > > > ^ > > > >/usr/include/boost/graph/detail/adjacency_list.hpp:2499:35: error: forming > >reference to void> > > typedef const value_type& const_reference; > > > > ^ > > > >/usr/include/boost/graph/detail/adjacency_list.hpp:2502:47: error: forming > >reference to void> > > <Graph, value_type, reference, Tag> type; > > > > ^ > > > >/usr/include/boost/graph/detail/adjacency_list.hpp:2504:53: error: forming > >reference to void> > > <Graph, value_type, const_reference, Tag> const_type; > > > > ^ > > > >CooperativeGraph.cpp: In member function ?void > >CooperativeGraph::getProperties()?: CooperativeGraph.cpp:384:35: error: no > >matching function for call to ?get(boost::vertex_index_t, Graph&)?> > > vertex_index = get(vertex_index,g); > > > > ^ > > > >I defined the data structure as follows > > > >typedef property<vertex_BatteryLevel_t,int, > > > > property<vertex_ObservationHistory_t,deque<Observation>, > > > > property<vertex_name_t,uuid> > >> > >> vertex_state; > > > >typedef property<edge_QFunction_t,QTable, > > > > property<edge_Eligibility_t,Eligibility> > >> > >> edge_qfunction; > > > >typedef adjacency_list< > > > > vecS,setS,directedS, > > vertex_state, > > edge_qfunction > >> > >> Graph; > > > >Does anyone know what I am doing wrong? Why can't I get the vertex_index_t > >property. Thanks! > Your graph type has setS as its vertex container. Try using vecS instead to > get the vertex_index property to be present. > > -- Jeremiah Willcock > > > ------------------------------ > > Message: 4 > Date: Thu, 23 Jul 2015 14:31:51 +0000 > From: "Auer, Jens" <jens.auer(a)cgi.com> > To: "boost-users(a)lists.boost.org" <boost-users(a)lists.boost.org> > Subject: Re: [Boost-users] Boost.DateTime and leap year/leap seconds > Message-ID: > <E47848702ADBE04EA7ECF45E05F60B6DF98E840C(a)SE-EX020.groupinfra.com> > Content-Type: text/plain; charset="utf-8" > > Hi Howard, > > Thank you very much. That basically made my day! > > We have no restrictions on the compiler, currently I'm using gcc 4.9 in > C++-14 mode. I think I can also justify using a time handling library, so > the chances are very good that we will use your library. > > Many thanks and best wishes, > Jens > > -- > Dr. Jens Auer | CGI | Software Engineer > CGI Deutschland Ltd. & Co. KG > Rheinstra?e 95 | 64295 Darmstadt | Germany > T: +49 6151 36860 154 > jens.auer(a)cgi.com > Unsere Pflichtangaben gem?? ? 35a GmbHG / ?? 161, 125a HGB finden Sie unter > de.cgi.com/pflichtangaben. > > CONFIDENTIALITY NOTICE: Proprietary/Confidential information belonging to > CGI Group Inc. and its affiliates may be contained in this message. If you > are not a recipient indicated or intended in this message (or responsible > for delivery of this message to such person), or you think for any reason > that this message may have been addressed to you in error, you may not use > or copy or deliver this message to anyone else. In such case, you should > destroy this message and are asked to notify the sender by reply e-mail. > > -----Original Message----- > From: Boost-users [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Howard Hinnant Sent: 22 July 2015 21:29 > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] Boost.DateTime and leap year/leap seconds > > I?ve been following this thread with interest. > > On Jul 22, 2015, at 8:59 AM, Auer, Jens <jens.auer(a)cgi.com> wrote: > > Reading the documentation I think that will not be correct when there were > > leap seconds. > Correct. As Jeff said earlier, leap second support is not in the current > library, but might be a feature in a future boost date-time 2.0. > > If you are using a C++11 or C++14 compiler, there is a library that will > handle this problem with leap seconds taken into account for you: > > http://howardhinnant.github.io/tz.html > > I doubt you can use this library as the space industry equates up-to-date > compilers with increased risk. However I mention it, as it is open source > and perhaps you can crib some of its ideas onto the current boost date-time > library. > > In a nutshell, this C++11/14 library handles leap seconds along the lines of > what Jeff suggested. Though in this case it creates a std::chrono - > compatible clock which is leap second aware: > > class utc_clock > { > public: > using duration = > std::chrono::system_clock::duration; using rep = > duration::rep; > using period = duration::period; > using time_point = > std::chrono::time_point<utc_clock>; static constexpr bool is_steady = true; > > static time_point now() noexcept; > > template <class Duration> > static > std::chrono::time_point<utc_clock, > typename std::common_type<Duration, > std::chrono::seconds>::type> > sys_to_utc(std::chrono::time_point<std::chrono::system_clock, Duration> t); > > template <class Duration> > static > std::chrono::time_point<std::chrono::system_clock, > typename std::common_type<Duration, > std::chrono::seconds>::type> utc_to_sys(std::chrono::time_point<utc_clock, > Duration> t); }; > > and includes conversions to and from std::chrono::system_clock::time_point > (which like boost date-time is based on Unix time). These conversions are > simply lookups into an ordered list of leap second transitions, resulting > in the addition or subtraction of the proper number of leap seconds. > > This could be used like so: > > struct CCSDS > { > std::uint16_t days; > std::uint32_t ms; > std::uint16_t us; > }; > > CCSDS > to_CCSDS(date::year y, std::chrono::microseconds us) > { > using namespace date; > using namespace std::chrono; > auto utc = utc_clock::sys_to_utc(day_point(y/jan/1)) + us; > auto sys = utc_clock::utc_to_sys(utc); > auto dp = floor<days>(sys); > auto d = dp - day_point(1958_y/jan/1); > us = utc - utc_clock::sys_to_utc(dp); > auto ms = duration_cast<milliseconds>(us); > us -= ms; > return {static_cast<std::uint16_t>(d.count()), > static_cast<std::uint32_t>(ms.count()), > static_cast<std::uint16_t>(us.count())}; > } > > The variable utc holds the ?year + us? as a time point with microseconds > precision. This time point counts microseconds, including leap seconds, > since 1970-01-01 00:00:00 UTC. > > The next step is find when the day started that is associated with utc. To > do this one must convert utc back to ?Unix time?, and then truncate that > time point to a precision of days, resulting in the variable dp. dp is a > count of days since 1970-01-01. Since your epoch is 1958-01-01, this is > taken into account in creating ?d?, the first value needed in your return > type. > > Now the number of microseconds since the start of the day needs to be > computed. The start of the day, dp, is converted back into the leap-second > aware system, and subtracted from the microsecond time point: utc. The > variable us is reused to hold ?microseconds since midnight?. Now it is a > simple computation to split this into milliseconds since midnight, and > microseconds since the last millisecond. > > This has all been tested with: > > void > test_to_CCSDS() > { > using namespace std::chrono; > using namespace date; > for (auto d = days{179}; d <= days{181}; ++d) > { > auto start = d + 86399s + 999999us + 0us; > for (auto us = start; us <= start + 3s; us += 1s) > { > auto t = to_CCSDS(2015_y, us); > std::cout << t.days << ' ' << t.ms << ' ' << t.us << '\n'; > } > std::cout << '\n'; > } > } > > which yields: > > 20998 86399999 999 > 20999 999 999 > 20999 1999 999 > 20999 2999 999 > > 20999 86399999 999 > 20999 86400999 999 > 21000 999 999 > 21000 1999 999 > > 21000 86398999 999 > 21000 86399999 999 > 21001 999 999 > 21001 1999 999 > > Interpretation: On 2015-06-29 23:59:59.999999 we are 1us away from the next > day. 1s later we are well into 2015-06-30. > > 24hrs later, we see a different pattern as the leap second is inserted. The > last microsecond of the day is 1s later at 2015-06030 23:59:60.999999. > > 24hrs later we are back to days with only 86400s. > > Assuming you have some conversion data to test against, this will hopefully > match up with those test cases. > > Howard > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users > > ------------------------------ > > End of Boost-users Digest, Vol 4202, Issue 3 > ********************************************

2 1

question about vertex_index_t property of graph
by breadbread1984 24 Jul '15

24 Jul '15

I am using boost graph library. I want to know whether the value of vertex_index_t property is assigned and updated automatically? If I serialize a graph to a file and deserialize it, will the value of vertex_index_t property remain?

2 1

Boost.DateTime and leap year/leap seconds
by Auer, Jens 23 Jul '15

23 Jul '15

Hi, I am considering using Boost.DateTime in one of my projects, and there have been some concerns about handling leap seconds on the customers side. The documentation says that other libraries do not handle leap seconds correctly, but it does not state that Boost.DateTime does. I found only one mail from 2009 on the mailing list asking about leap seconds, but this does not give an answer. Does anybody have some information on this? The computations I intend to do are actually rather limited. I will be given a year and a number microseconds, and have to compute the day in the year that this describes from the start of the year, together with microseconds and milliseconds in the day. So what I want to implement is a function tuple<days, milliseconds, microsends> convertTime(year, microseconds). Best wishes, Jens -- Dr. Jens Auer | CGI | Software Engineer CGI Deutschland Ltd. & Co. KG Rheinstraße 95 | 64295 Darmstadt | Germany T: +49 6151 36860 154 jens.auer(a)cgi.com<mailto:jens.auer@cgi.com> Unsere Pflichtangaben gemäß § 35a GmbHG / §§ 161, 125a HGB finden Sie unter de.cgi.com/pflichtangaben<http://de.cgi.com/pflichtangaben>. CONFIDENTIALITY NOTICE: Proprietary/Confidential information belonging to CGI Group Inc. and its affiliates may be contained in this message. If you are not a recipient indicated or intended in this message (or responsible for delivery of this message to such person), or you think for any reason that this message may have been addressed to you in error, you may not use or copy or deliver this message to anyone else. In such case, you should destroy this message and are asked to notify the sender by reply e-mail.

3 6

problem of getting vertex_index_t property with BGL
by breadbread1984 23 Jul '15

23 Jul '15

I am using boost graph library. I found there is a built in property vertex_index_t corresponding to every vertex from the document [here](http://www.boost.org/doc/libs/1_58_0/libs/graph/doc/adjacency_list.ht…. But when I get the vertex_index_t property the compiler prompt the following error: CooperativeGraph.h:59:36: required from here /usr/include/boost/graph/detail/adjacency_list.hpp:2498:29: error: forming reference to void typedef value_type& reference; ^ /usr/include/boost/graph/detail/adjacency_list.hpp:2499:35: error: forming reference to void typedef const value_type& const_reference; ^ /usr/include/boost/graph/detail/adjacency_list.hpp:2502:47: error: forming reference to void <Graph, value_type, reference, Tag> type; ^ /usr/include/boost/graph/detail/adjacency_list.hpp:2504:53: error: forming reference to void <Graph, value_type, const_reference, Tag> const_type; ^ CooperativeGraph.cpp: In member function ‘void CooperativeGraph::getProperties()’: CooperativeGraph.cpp:384:35: error: no matching function for call to ‘get(boost::vertex_index_t, Graph&)’ vertex_index = get(vertex_index,g); ^ I defined the data structure as follows typedef property<vertex_BatteryLevel_t,int, property<vertex_ObservationHistory_t,deque<Observation>, property<vertex_name_t,uuid> > > vertex_state; typedef property<edge_QFunction_t,QTable, property<edge_Eligibility_t,Eligibility> > edge_qfunction; typedef adjacency_list< vecS,setS,directedS, vertex_state, edge_qfunction > Graph; Does anyone know what I am doing wrong? Why can't I get the vertex_index_t property. Thanks!

2 1

[interval] Power
by Sensei 23 Jul '15

23 Jul '15

Dear all, I am defining a "scalar" type for a project, and this scalar I'd like to be an interval. Among the operations, already provided by boost interval, I need pow(interval, interval). Since there is no pow() function, but log() and exp() are defined, I mistakenly defined power as the obvious: typedef boost::numeric::interval<double> scalar; scalar p(1.0, 1.0), q(4, 100); log << "^ " << boost::numeric::exp(p * boost::numeric::log(q)) << std::endl; Unfortunately, it won't work, and it gives me this error: /usr/local/include/boost/numeric/interval/transc.hpp:47:42: No member named 'log_down' in 'boost::numeric::interval_lib::rounded_math<double>' /usr/local/include/boost/numeric/interval/transc.hpp:34:16: No member named 'exp_down' in 'boost::numeric::interval_lib::rounded_math<double>' Is there any "correct" pow() function I can implement? Is something wrong with the definition of scalar? Thank you!

2 3

Re: [Boost-users] Subject:[atomic] why atomic<>::store method can not support memory_order_consum memory_order_acquire and memory_order_acq_rel these memory_orders?
by class7class＠163.com 23 Jul '15

23 Jul '15

Your explanation is very detailedand useful, I think I understood. Thank you very much! class7class(a)163.com From: boost-users-request Date: 2015-07-23 09:04 To: boost-users Subject: Boost-users Digest, Vol 4201, Issue 4 Send Boost-users mailing list submissions to boost-users(a)lists.boost.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.boost.org/mailman/listinfo.cgi/boost-users or, via email, send a message with subject or body 'help' to boost-users-request(a)lists.boost.org You can reach the person managing the list at boost-users-owner(a)lists.boost.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Boost-users digest..." Today's Topics: 1. Re: Boost release 1.59.0 beta 1 is now available from SourceForge (Ben Pope) 2. Re: Boost release 1.59.0 beta 1 is now available from SourceForge (Vicky Vergara) 3. Re: Subject:[atomic] why atomic<>::store method can not support memory_order_consum memory_order_acquire and memory_order_acq_rel these memory_orders? (Gavin Lambert) 4. [filesystem] problem: is_regular_file and deduplified files (reparse+sparse) (Paul Harris) 5. Re: Subject:[atomic] why atomic<>::store method can not support memory_order_consum memory_order_acquire and memory_order_acq_rel (Isaac To) ---------------------------------------------------------------------- Message: 1 Date: Thu, 23 Jul 2015 05:20:39 +0800 From: Ben Pope <benpope81(a)gmail.com> To: boost-users(a)lists.boost.org Cc: boost(a)lists.boost.org Subject: Re: [Boost-users] Boost release 1.59.0 beta 1 is now available from SourceForge Message-ID: <mop1f7$6dg$1(a)ger.gmane.org> Content-Type: text/plain; charset=windows-1252; format=flowed On Thursday, July 23, 2015 02:23 AM, Marshall Clow wrote: > On Thu, Jul 16, 2015 at 6:16 AM, Marshall Clow <mclow.lists(a)gmail.com > <mailto:mclow.lists@gmail.com>> wrote: > > > Boost release 1.59.0 beta 1 is now available from SourceForge > See http://sourceforge.net/projects/boost/files/boost/1.59.0.beta.1/ > For details of what's in the release, see > http://www.boost.org/users/history/version_1_59_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. > > > Has anyone tried the beta release with new compilers? > > Specifically, I'm thinking about: > * GCC 5.2 > * VS2015 > * Clang 3.7rc1 For clang 3.7 rc1, the tests for master are up on the ftp, but they won't be published because I haven't submitted a pull request for them to be published on the test site, since I don't run them regularly. The dev results should be up on the test matrix at some point soon, but the entire run of dev and release takes a couple of days (which feels slow) and is still in progress. I intend to publish the results of asan, msan, tsan runs at some point but I haven't got round to figuring out the right way to present them yet, if you want the raw xml results and don't have access to the ftp, contact me. I'll probably run for gcc 5.2 when it arrives on Ubuntu's launchpad. Ben ------------------------------ Message: 2 Date: Wed, 22 Jul 2015 17:53:17 -0500 From: Vicky Vergara <vicky_vergara(a)hotmail.com> To: "boost-users(a)lists.boost.org" <boost-users(a)lists.boost.org> Subject: Re: [Boost-users] Boost release 1.59.0 beta 1 is now available from SourceForge Message-ID: <BAY177-W30049CC41A57EE28144AA18A830(a)phx.gbl> Content-Type: text/plain; charset="iso-8859-1" We re working on the release of pgRouting. We use Boost.Graph. My Question is: Waht changes I have to do in Github travis to check that pgRouting is compatible with this beta release? Here is our travis file: https://github.com/pgRouting/pgrouting/blob/develop_2_1_0/.travis.yml Right now it runs with boost 1.46.1 https://travis-ci.org/pgRouting/pgrouting/jobs/72064827#L1834 Thanks > To: boost-users(a)lists.boost.org > From: benpope81(a)gmail.com > Date: Thu, 23 Jul 2015 05:20:39 +0800 > CC: boost(a)lists.boost.org > Subject: Re: [Boost-users] Boost release 1.59.0 beta 1 is now available from SourceForge > > On Thursday, July 23, 2015 02:23 AM, Marshall Clow wrote: > > On Thu, Jul 16, 2015 at 6:16 AM, Marshall Clow <mclow.lists(a)gmail.com > > <mailto:mclow.lists@gmail.com>> wrote: > > > > > > Boost release 1.59.0 beta 1 is now available from SourceForge > > See http://sourceforge.net/projects/boost/files/boost/1.59.0.beta.1/ > > For details of what's in the release, see > > http://www.boost.org/users/history/version_1_59_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. > > > > > > Has anyone tried the beta release with new compilers? > > > > Specifically, I'm thinking about: > > * GCC 5.2 > > * VS2015 > > * Clang 3.7rc1 > > For clang 3.7 rc1, the tests for master are up on the ftp, but they > won't be published because I haven't submitted a pull request for them > to be published on the test site, since I don't run them regularly. > > The dev results should be up on the test matrix at some point soon, but > the entire run of dev and release takes a couple of days (which feels > slow) and is still in progress. > > I intend to publish the results of asan, msan, tsan runs at some point > but I haven't got round to figuring out the right way to present them > yet, if you want the raw xml results and don't have access to the ftp, > contact me. > > I'll probably run for gcc 5.2 when it arrives on Ubuntu's launchpad. > > Ben > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users -------------- next part -------------- HTML attachment scrubbed and removed ------------------------------ Message: 3 Date: Thu, 23 Jul 2015 12:20:28 +1200 From: Gavin Lambert <gavinl(a)compacsort.com> To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] Subject:[atomic] why atomic<>::store method can not support memory_order_consum memory_order_acquire and memory_order_acq_rel these memory_orders? Message-ID: <mopc0e$6ph$1(a)ger.gmane.org> Content-Type: text/plain; charset=windows-1252; format=flowed On 22/07/2015 14:43, class7class(a)163.com wrote: > I am a SE and I program based on boost library, I have one question to > ask as below: > > When I use the atomic library included boost , I coded as following: > atomic<bool> flag; //declare the var > flag.store(true,boost::memory_order_acq_rel); // use > store method to change the value of flag > > but BOOST_ASSERT failed,and I read the code of base_atomic<> template > class,I found the the store() method can not support several > memory_orders metioned in the subject , and the other methods can not > support all memory_orders,such as: > 1.the load method can not support memory_order_release and > memory_order_acq_rel > 2. the compare_exchange_strong method can not support > memory_order_release and memory_order_acq_rel > 3. the compare_exchange_weak method can not support > memory_order_release and memory_order_acq_rel > > I really want to know the reason that why the methods of atomic can not > support all memory_orders. Because this is mandated by the standard, and because doing otherwise doesn't really make sense. Loads can't release, and stores can't acquire. Therefore those memory orders are nonsensical. memory_order_acq_rel exists for RMW operations such as compare_exchange. The "acq" applies to the load and the "rel" to the store. It's not sensible for a store alone. > If I need the methods of the atomic<> support all memory_orders,how > can i do? You can re-read the standard memory model and discover why that doesn't make sense. Memory ordering can be tricky to get your head around at first -- it's a good idea to run any atomic algorithm you implement through a sanity checker such as RRD or ThreadSanitizer to help catch subtle bugs. If in doubt, stick with seq_cst memory ordering (the default). On x86/x64 there is very little performance difference between seq_cst and the weaker orders -- cacheline sharing tends to be more problematic. ------------------------------ Message: 4 Date: Thu, 23 Jul 2015 08:56:21 +0800 From: Paul Harris <harris.pc(a)gmail.com> To: boost-users <boost-users(a)lists.boost.org> Subject: [Boost-users] [filesystem] problem: is_regular_file and deduplified files (reparse+sparse) Message-ID: <CAMSUDdZL95bnn3Ec=3pKGkKRdtMk2i7=PL6e7aK6u4J9GBVpZg(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi guys, I'm seeing a lot of failures all of a sudden, its a serious problem. I imagine some of you may start seeing the same failures too very soon. I'm seeing it with boost 1.58.0. There is a related bug already entered here: https://svn.boost.org/trac/boost/ticket/11057 I can't seem to log on and update this ticket. But the problem extends further than that ticket. Windows Server 2003 support has been dropped by Microsoft, and a lot of IT depts around the world are switching over to the latest Windows Server. With this server comes the new "dedup" feature, that can automatically deduplify files. This happens on a schedule, eg 2am saturday. So suddenly we are getting messages of failures of software from all over the place, due to fs::is_regular_file() Deduped files have the REPARSE and SPARSE flag set. On the command line, you can run FSUTIL REPARSEPOINT QUERY and the "Reparse Tag Value" is 0x80000013 Which is a relatively new flag known as IO_REPARSE_TAG_DEDUP https://msdn.microsoft.com/en-us/library/windows/desktop/aa365740%28v=vs.85… These files act as normal files, you can fopen and fread them, so I assume they should be treated almost like symlink by boost... perhaps not quite a symlink because I assume the "lstat" link properties are identical to the file's stat properties. Typically, I iterate over directories and only process files if fs::is_regular_file(filename) is true. I wrote some code to check what the properties were on these files, and its not any of the possible enums detected by file_status::type(). ideas? Best regards, Paul -------------- next part -------------- HTML attachment scrubbed and removed ------------------------------ Message: 5 Date: Thu, 23 Jul 2015 09:04:57 +0800 From: Isaac To <isaac.to(a)gmail.com> To: boost-users(a)lists.boost.org Subject: Re: [Boost-users] Subject:[atomic] why atomic<>::store method can not support memory_order_consum memory_order_acquire and memory_order_acq_rel Message-ID: <CAOArY3UmCXoCcWPntHo2GufdmAy1mSNceFGUwdoZt4_Kd5D2EA(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" On Thu, Jul 23, 2015 at 12:00 AM, "class7class(a)163.com" <class7class(a)163.com > wrote: > I found the the store() method can not support several memory_orders > metioned in the subject , and the other methods can not support all > memory_orders,such as: > 1.the load method can not support memory_order_release and > memory_order_acq_rel > 2. the compare_exchange_strong method can not support > memory_order_release and memory_order_acq_rel > 3. the compare_exchange_weak method can not support memory_order_release > and memory_order_acq_rel > > I really want to know the reason that why the methods of atomic can not > support all memory_orders. > > If I need the methods of the atomic<> support all memory_orders,how can i > do? > You are asking into the area of C++ where the fewest people in the world understand, namely relaxed atomics. Before I tell my limited understanding of the issue, I have an advice: - Use mutexes like boost::mutex to ensure all your accesses to variables shared among threads are not accessed concurrently, and you'll be fine. If your circumstance forces you to ignore the above advice (like me, e.g., when you cannot afford the scheduling overheads of mutexes), here is yet another advice which may save your life: - Make all your variables that can be accessed concurrently from multiple threads (with at least one thread writing) atomic. (This makes your program "data race free".) - Always use the default memory_order_seq_cst memory ordering for accesses to your atomics, never use anything else. If your circumstance forces you to ignore the above advices (unlike me, I just learn them because I haven't heard about the second advice before; you'll have to be writing for old ARM (i.e., ones without the LDA and STL instructions) or POWER for you to have a real reason to use relaxed atomics, I write for neither), here is what I have learnt. tl;dr The boost atomic doesn't support all memory ordering because the C++11 standard doesn't support all of them. The C++ standard doesn't support all memory ordering because not all make sense in the "memory model" supported by C++. It is not likely to change in the near future, i.e., unless some genius devises some novel memory model which changes the status quo. Here "memory model" means what "loads" from memory is allowed to return. Because of compiler and hardware optimization, writes (including atomic writes) to memory locations may be reordered, so the load doesn't always return "the last value stored". Special hardware instructions are necessary to ensure a particular ordering that the programmer needs. The easiest way to understand a program is that "All memory operations by all threads looks as if they are done one after another, interleaving among threads". But it proves to be too tricky for hardware to provide any reasonable performance for this model. The C++ memory model without relaxed atomics is essentially "All *atomic* memory operations by all threads looks as if they are done one after another, interleaving among threads. All other memory operations of each thread looks as if they are completely done between adjacent atomic memory operations. But the programmer guarantees not to write a data race. The compiler uses this assumption in all its work, and your program can break in all mysterious ways if you break this rule." This is essentially the illusion provided by sequential consistency. Everybody should want it. Except some don't, because in some architectures it is essentially impossible to provide sequential consistency efficiently. To do sequential consistency, one has to ensure that (1) the compiler doesn't reorder the statements written by the programmer, which is controllable by compiler writer; and (2) the hardware doesn't reorder the instructions generated by the compiler, which is damn hard. It usually means the compiler must insert memory fences before and after memory accesses (i.e., tell the CPU "don't return to me until everything I do up to this point are visible by all other CPUs" or "don't return to me until everything other CPUs do up to this point are visible by me"), which is very slow. It is particularly bad because for these architectures, fences must be inserted not just for atomic stores, but for the supposedly fast atomic loads as well. (Recent architectures do better because they link the requirement into the accesses of the particular memory location: the "particular memory location" here limits the scope where the "fences" have to do, and this makes a big difference in performance.) That's why relaxed atomics (i.e., memory_order_acq, etc) exists in the standard. They allow those architectures to perform better than using full sequential consistency in some common cases. Because different architectures require different sort of fences, it doesn't make sense for these to mean "insert a fence after the load". Instead, the C++ standard uses a more programmer centric view when defining relaxed memory ordering: - If a thread X stores a value with release semantics into an atomic variable, and another thread Y loads this value with acquire semantics from that same atomic variable, then everything done by thread X before this releasing store are guaranteed to be visible to thread Y after this acquiring load. There is no other semantics attached to the acquire and release. This is why acquiring stores and releasing loads are meaningless: they are not assigned any semantics. But the deeper reason for the lack is that the computer industry cannot find a way to give additional guarantee without incurring hefty performance overheads. And at the same time, sequentially consistent atomics are not so expensive in the new architectures. As for what to do if you want more than the above release-acquire guarantee: Simple, just use sequentially consistent atomic operations. Regards, Isaac -------------- next part -------------- HTML attachment scrubbed and removed ------------------------------ Subject: Digest Footer _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users ------------------------------ End of Boost-users Digest, Vol 4201, Issue 4 ********************************************

1 0

Can Boot MultiIndex help me?
by Paolo Bolzoni 23 Jul '15

23 Jul '15

Dear list, I needed a data structure such that: - a list of POD structs (with an Id and other fields) stays in contiguous memory. This is required because I need to pass this block of memory to a C function. - the order of this POD structs is irrelevant. - I need to access to each element from the Id quickly. So I implemented a class using std::map and std::vector; the vector contains the structs and the map associate between the ids and the vector position. The vector ensures C memory layout and the map gives the elements from the Id quickly. To delete an element I copy the last element in its position, update the map, and pop the vector back (of course there are some special cases, like deleting the last element... but you got the point) To add an element I push it back to the vector and update the map. It works fine, but a colleague mentioned that boost multiindex can do a similar job. I checked the documentation, but I am not sure I can build an index on a vector. Is that possible? Thanks. Your faithfully, Paolo

3 2

Re: [Boost-users] Subject:[atomic] why atomic<>::store method can not support memory_order_consum memory_order_acquire and memory_order_acq_rel
by Isaac To 23 Jul '15

23 Jul '15

On Thu, Jul 23, 2015 at 12:00 AM, "class7class(a)163.com" <class7class(a)163.com > wrote: > I found the the store() method can not support several memory_orders > metioned in the subject , and the other methods can not support all > memory_orders,such as: > 1.the load method can not support memory_order_release and > memory_order_acq_rel > 2. the compare_exchange_strong method can not support > memory_order_release and memory_order_acq_rel > 3. the compare_exchange_weak method can not support memory_order_release > and memory_order_acq_rel > > I really want to know the reason that why the methods of atomic can not > support all memory_orders. > > If I need the methods of the atomic<> support all memory_orders,how can i > do? > You are asking into the area of C++ where the fewest people in the world understand, namely relaxed atomics. Before I tell my limited understanding of the issue, I have an advice: - Use mutexes like boost::mutex to ensure all your accesses to variables shared among threads are not accessed concurrently, and you'll be fine. If your circumstance forces you to ignore the above advice (like me, e.g., when you cannot afford the scheduling overheads of mutexes), here is yet another advice which may save your life: - Make all your variables that can be accessed concurrently from multiple threads (with at least one thread writing) atomic. (This makes your program "data race free".) - Always use the default memory_order_seq_cst memory ordering for accesses to your atomics, never use anything else. If your circumstance forces you to ignore the above advices (unlike me, I just learn them because I haven't heard about the second advice before; you'll have to be writing for old ARM (i.e., ones without the LDA and STL instructions) or POWER for you to have a real reason to use relaxed atomics, I write for neither), here is what I have learnt. tl;dr The boost atomic doesn't support all memory ordering because the C++11 standard doesn't support all of them. The C++ standard doesn't support all memory ordering because not all make sense in the "memory model" supported by C++. It is not likely to change in the near future, i.e., unless some genius devises some novel memory model which changes the status quo. Here "memory model" means what "loads" from memory is allowed to return. Because of compiler and hardware optimization, writes (including atomic writes) to memory locations may be reordered, so the load doesn't always return "the last value stored". Special hardware instructions are necessary to ensure a particular ordering that the programmer needs. The easiest way to understand a program is that "All memory operations by all threads looks as if they are done one after another, interleaving among threads". But it proves to be too tricky for hardware to provide any reasonable performance for this model. The C++ memory model without relaxed atomics is essentially "All *atomic* memory operations by all threads looks as if they are done one after another, interleaving among threads. All other memory operations of each thread looks as if they are completely done between adjacent atomic memory operations. But the programmer guarantees not to write a data race. The compiler uses this assumption in all its work, and your program can break in all mysterious ways if you break this rule." This is essentially the illusion provided by sequential consistency. Everybody should want it. Except some don't, because in some architectures it is essentially impossible to provide sequential consistency efficiently. To do sequential consistency, one has to ensure that (1) the compiler doesn't reorder the statements written by the programmer, which is controllable by compiler writer; and (2) the hardware doesn't reorder the instructions generated by the compiler, which is damn hard. It usually means the compiler must insert memory fences before and after memory accesses (i.e., tell the CPU "don't return to me until everything I do up to this point are visible by all other CPUs" or "don't return to me until everything other CPUs do up to this point are visible by me"), which is very slow. It is particularly bad because for these architectures, fences must be inserted not just for atomic stores, but for the supposedly fast atomic loads as well. (Recent architectures do better because they link the requirement into the accesses of the particular memory location: the "particular memory location" here limits the scope where the "fences" have to do, and this makes a big difference in performance.) That's why relaxed atomics (i.e., memory_order_acq, etc) exists in the standard. They allow those architectures to perform better than using full sequential consistency in some common cases. Because different architectures require different sort of fences, it doesn't make sense for these to mean "insert a fence after the load". Instead, the C++ standard uses a more programmer centric view when defining relaxed memory ordering: - If a thread X stores a value with release semantics into an atomic variable, and another thread Y loads this value with acquire semantics from that same atomic variable, then everything done by thread X before this releasing store are guaranteed to be visible to thread Y after this acquiring load. There is no other semantics attached to the acquire and release. This is why acquiring stores and releasing loads are meaningless: they are not assigned any semantics. But the deeper reason for the lack is that the computer industry cannot find a way to give additional guarantee without incurring hefty performance overheads. And at the same time, sequentially consistent atomics are not so expensive in the new architectures. As for what to do if you want more than the above release-acquire guarantee: Simple, just use sequentially consistent atomic operations. Regards, Isaac

1 0

Subject:[atomic] why atomic<>::store method can not support memory_order_consum memory_order_acquire and memory_order_acq_rel these memory_orders?
by class7class＠163.com 23 Jul '15

23 Jul '15

Hello ! I am a SE and I program based on boost library, I have one question to ask as below: When I use the atomic library included boost , I coded as following: atomic<bool> flag; //declare the var flag.store(true,boost::memory_order_acq_rel); // use store method to change the value of flag but BOOST_ASSERT failed,and I read the code of base_atomic<> template class,I found the the store() method can not support several memory_orders metioned in the subject , and the other methods can not support all memory_orders,such as: 1.the load method can not support memory_order_release and memory_order_acq_rel 2. the compare_exchange_strong method can not support memory_order_release and memory_order_acq_rel 3. the compare_exchange_weak method can not support memory_order_release and memory_order_acq_rel I really want to know the reason that why the methods of atomic can not support all memory_orders. If I need the methods of the atomic<> support all memory_orders,how can i do? thank you very much! class7class(a)163.com

2 1

[Graph] Warning with boost 1.54, but not with 1.46.1 or 1.55
by Vicky Vergara 22 Jul '15

22 Jul '15

I have, with this code: 100: graph_traits<graph_t>::edge_iterator ei, eend; 101: for (tie(ei, eend) = boost::edges(graph); ei != eend; ei++) { I know this is not a major problem, as for the final release I will remove the -Wall flag from the compilation But then my question is why is the difference? Using boost 1.54 under Ubuntu 14.04 this warning shows on line 100 about variable ei /home/woodbri/work/pgrouting/src/apsp_johnson/src/apsp_johnson_boost_wrapper.cpp:100:40: warning: '*((void*)(& ei)+32).__gnu_cxx::__normal_iterator<boost::detail::stored_edge_property<long unsigned int, Edge>*, std::vector<boost::detail::stored_edge_property<long unsigned int, Edge>, std::allocator<boost::detail::stored_edge_property<long unsigned int, Edge> > > >:: _M_current' may be used uninitialized in this function [-Wmaybe-uninitialized] graph_traits<graph_t>::edge_iterator ei, eend; the complete code can be found : https://github.com/pgRouting/pgrouting/blob/develop/src/apsp_johnson/src/ap… in the cmake the compiler flags are set like this: set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fPIC -O2 -g -Wall -std=c++0x -frounding-math -Wno-deprecated") Complete setup can be found: https://github.com/pgRouting/pgrouting/blob/develop_2_1_0/CMakeLists.txt#L2… This is a test that has boost 1.46.1, no warning shows I also don't get a warning with boost 1.55 https://travis-ci.org/pgRouting/pgrouting/jobs/72064827#L1834 The complete conversation of the problem can be found here: https://github.com/pgRouting/pgrouting/issues/373#issuecomment-123749888

1 0

Help with voronoi diagram
by rehouma 22 Jul '15

22 Jul '15

<http://boost.2283326.n4.nabble.com/file/n4678233/voronoi.png> I work on a project were I needed to generate the voronoi diagram (dashed lines = voronoi diagram). I used boost successfully. Now, I need to determine the coordinates of the output point e11 from the coordinates of the input point e1 and determine the coordinates of the other input point e12. Please help me, how can I do this. Thanks. -- View this message in context: http://boost.2283326.n4.nabble.com/Help-with-voronoi-diagram-tp4678233.html Sent from the Boost - Users mailing list archive at Nabble.com.

1 0

enable_if error with Intel compiler 15.0.1
by Matthieu Brucher 21 Jul '15

21 Jul '15

Hi, I got this error on Linux with the Intel compiler: PATH/boost/boost_1_58_0/include/boost/core/enable_if.hpp(36): error: incomplete type is not allowed struct enable_if : public enable_if_c<Cond::value, T> {}; ^ detected during: instantiation of class "boost::enable_if<Cond, T> [with Cond=boost::mpl::and_<boost::fusion::traits::is_sequence<boost::fusion::cons<boost::spirit::qi::literal_char<boost::spirit::char_encoding::standard, true, false>, boost::fusion::cons<boost::spirit::qi::action<boost::spirit::qi::reference<const boost::spirit::qi::rule<__gnu_cxx::__normal_iterator<const char *, std::basic_string<char, std::char_traits<char>, std::allocator<char>>>, expr_node (), boost::spirit::ascii::space_type, boost::spirit::unused_type, boost::spirit::unused_type>>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::assign, boost::proto::argsns_::list2<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::spirit::attribute<0>>, 0L>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list4<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<binary_op_phx>, 0L>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<const char *>, 0L>, boost::spirit::_val_type, boost::spirit::_1_type>, 4L>>>, 2L>>>, boost::fusion::nil_>>>, boost::mpl::not_<boost::is_convertible<boost::fusion::cons<boost::spirit::qi::literal_char<boost::spirit::char_encoding::standard, true, false>, boost::fusion::cons<boost::spirit::qi::action<boost::spirit::qi::reference<const boost::spirit::qi::rule<__gnu_cxx::__normal_iterator<const char *, std::basic_string<char, std::char_traits<char>, std::allocator<char>>>, expr_node (), boost::spirit::ascii::space_type, boost::spirit::unused_type, boost::spirit::unused_type>>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::assign, boost::proto::argsns_::list2<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::spirit::attribute<0>>, 0L>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list4<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<binary_op_phx>, 0L>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<const char *>, 0L>, boost::spirit::_val_type, boost::spirit::_1_type>, 4L>>>, 2L>>>, boost::fusion::nil_>>, boost::spirit::qi::literal_char<boost::spirit::char_encoding::standard, true, false>>>, boost::mpl::bool_<true>, boost::mpl::bool_<true>, boost::mpl::bool_<true>>, T=void]" at line 92 of "PATH/boost/boost_1_58_0/include/boost/type_traits/is_convertible.hpp" instantiation of class "boost::detail::is_convertible_basic_impl<From, To, false> [with From=boost::fusion::cons<boost::spirit::qi::literal_char<boost::spirit::char_encoding::standard, true, false>, boost::fusion::cons<boost::spirit::qi::action<boost::spirit::qi::reference<const boost::spirit::qi::rule<__gnu_cxx::__normal_iterator<const char *, std::basic_string<char, std::char_traits<char>, std::allocator<char>>>, expr_node (), boost::spirit::ascii::space_type, boost::spirit::unused_type, boost::spirit::unused_type>>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::assign, boost::proto::argsns_::list2<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::spirit::attribute<0>>, 0L>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list4<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<binary_op_phx>, 0L>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<const char *>, 0L>, boost::spirit::_val_type, boost::spirit::_1_type>, 4L>>>, 2L>>>, boost::fusion::nil_>>, To=boost::spirit::qi::literal_char<boost::spirit::char_encoding::standard, true, false>]" at line 357 of "PATH/boost/boost_1_58_0/include/boost/type_traits/is_convertible.hpp" instantiation of class "boost::detail::is_convertible_impl<From, To> [with From=boost::fusion::cons<boost::spirit::qi::literal_char<boost::spirit::char_encoding::standard, true, false>, boost::fusion::cons<boost::spirit::qi::action<boost::spirit::qi::reference<const boost::spirit::qi::rule<__gnu_cxx::__normal_iterator<const char *, std::basic_string<char, std::char_traits<char>, std::allocator<char>>>, expr_node (), boost::spirit::ascii::space_type, boost::spirit::unused_type, boost::spirit::unused_type>>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::assign, boost::proto::argsns_::list2<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::spirit::attribute<0>>, 0L>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list4<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<binary_op_phx>, 0L>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<const char *>, 0L>, boost::spirit::_val_type, boost::spirit::_1_type>, 4L>>>, 2L>>>, boost::fusion::nil_>>, To=boost::spirit::qi::literal_char<boost::spirit::char_encoding::standard, true, false>]" at line 437 of "PATH/boost/boost_1_58_0/include/boost/type_traits/is_convertible.hpp" instantiation of class "boost::detail::is_convertible_impl_dispatch<From, To> [with From=boost::fusion::cons<boost::spirit::qi::literal_char<boost::spirit::char_encoding::standard, true, false>, boost::fusion::cons<boost::spirit::qi::action<boost::spirit::qi::reference<const boost::spirit::qi::rule<__gnu_cxx::__normal_iterator<const char *, std::basic_string<char, std::char_traits<char>, std::allocator<char>>>, expr_node (), boost::spirit::ascii::space_type, boost::spirit::unused_type, boost::spirit::unused_type>>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::assign, boost::proto::argsns_::list2<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::spirit::attribute<0>>, 0L>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list4<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<binary_op_phx>, 0L>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<const char *>, 0L>, boost::spirit::_val_type, boost::spirit::_1_type>, 4L>>>, 2L>>>, boost::fusion::nil_>>, To=boost::spirit::qi::literal_char<boost::spirit::char_encoding::standard, true, false>]" at line 482 of "PATH/boost/boost_1_58_0/include/boost/type_traits/is_convertible.hpp" instantiation of class "boost::is_convertible<From, To> [with From=boost::fusion::cons<boost::spirit::qi::literal_char<boost::spirit::char_encoding::standard, true, false>, boost::fusion::cons<boost::spirit::qi::action<boost::spirit::qi::reference<const boost::spirit::qi::rule<__gnu_cxx::__normal_iterator<const char *, std::basic_string<char, std::char_traits<char>, std::allocator<char>>>, expr_node (), boost::spirit::ascii::space_type, boost::spirit::unused_type, boost::spirit::unused_type>>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::assign, boost::proto::argsns_::list2<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::spirit::attribute<0>>, 0L>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list4<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<binary_op_phx>, 0L>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<const char *>, 0L>, boost::spirit::_val_type, boost::spirit::_1_type>, 4L>>>, 2L>>>, boost::fusion::nil_>>, To=boost::spirit::qi::literal_char<boost::spirit::char_encoding::standard, true, false>]" at line 27 of "PATH/boost/boost_1_58_0/include/boost/mpl/aux_/nested_type_wknd.hpp" [ 26 instantiation contexts not shown ] instantiation of class "boost::proto::transform<PrimitiveTransform, X>::result<Sig> [with PrimitiveTransform=boost::proto::switch_<boost::spirit::meta_compiler<boost::spirit::qi::domain>::cases, boost::proto::tag_of<boost::proto::_> ()>, X=void, Sig=boost::spirit::meta_compiler<boost::spirit::qi::domain>::meta_grammar (boost::proto::exprns_::expr<boost::proto::tagns_::tag::shift_right, boost::proto::argsns_::list2<const boost::proto::exprns_::expr<boost::proto::tagns_::tag::subscript, boost::proto::argsns_::list2<boost::spirit::qi::rule<__gnu_cxx::__normal_iterator<const char *, std::basic_string<char, std::char_traits<char>, std::allocator<char>>>, expr_node (), boost::spirit::ascii::space_type, boost::spirit::unused_type, boost::spirit::unused_type> &, const boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::assign, boost::proto::argsns_::list2<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::spirit::attribute<0>>, 0L>, boost::spirit::_1_type>, 2L>> &>, 2L> &, const boost::proto::exprns_::expr<boost::proto::tagns_::tag::dereference, boost::proto::argsns_::list1<const boost::proto::exprns_::expr<boost::proto::tagns_::tag::shift_right, boost::proto::argsns_::list2<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<const char &>, 0L>, const boost::proto::exprns_::expr<boost::proto::tagns_::tag::subscript, boost::proto::argsns_::list2<boost::spirit::qi::rule<__gnu_cxx::__normal_iterator<const char *, std::basic_string<char, std::char_traits<char>, std::allocator<char>>>, expr_node (), boost::spirit::ascii::space_type, boost::spirit::unused_type, boost::spirit::unused_type> &, const boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::assign, boost::proto::argsns_::list2<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::spirit::attribute<0>>, 0L>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list4<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<binary_op_phx>, 0L>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<const char *>, 0L>, boost::spirit::_val_type, boost::spirit::_1_type>, 4L>>>, 2L>> &>, 2L> &>, 2L> &>, 1L> &>, 2L>, boost::mpl::void_, boost::spirit::unused_type)]" at line 206 of "PATH/boost/boost_1_58_0/include/boost/spirit/home/support/meta_compiler.hpp" instantiation of class "boost::spirit::result_of::compile<Domain, Expr, Modifiers, Enable> [with Domain=boost::spirit::qi::domain, Expr=boost::proto::exprns_::expr<boost::proto::tagns_::tag::shift_right, boost::proto::argsns_::list2<const boost::proto::exprns_::expr<boost::proto::tagns_::tag::subscript, boost::proto::argsns_::list2<boost::spirit::qi::rule<__gnu_cxx::__normal_iterator<const char *, std::basic_string<char, std::char_traits<char>, std::allocator<char>>>, expr_node (), boost::spirit::ascii::space_type, boost::spirit::unused_type, boost::spirit::unused_type> &, const boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::assign, boost::proto::argsns_::list2<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::spirit::attribute<0>>, 0L>, boost::spirit::_1_type>, 2L>> &>, 2L> &, const boost::proto::exprns_::expr<boost::proto::tagns_::tag::dereference, boost::proto::argsns_::list1<const boost::proto::exprns_::expr<boost::proto::tagns_::tag::shift_right, boost::proto::argsns_::list2<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<const char &>, 0L>, const boost::proto::exprns_::expr<boost::proto::tagns_::tag::subscript, boost::proto::argsns_::list2<boost::spirit::qi::rule<__gnu_cxx::__normal_iterator<const char *, std::basic_string<char, std::char_traits<char>, std::allocator<char>>>, expr_node (), boost::spirit::ascii::space_type, boost::spirit::unused_type, boost::spirit::unused_type> &, const boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::assign, boost::proto::argsns_::list2<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::spirit::attribute<0>>, 0L>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list4<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<binary_op_phx>, 0L>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<const char *>, 0L>, boost::spirit::_val_type, boost::spirit::_1_type>, 4L>>>, 2L>> &>, 2L> &>, 2L> &>, 1L> &>, 2L>, Modifiers=boost::spirit::unused_type, Enable=void]" at line 184 of "PATH/boost/boost_1_58_0/include/boost/spirit/home/qi/nonterminal/rule.hpp" instantiation of "void boost::spirit::qi::rule<Iterator, T1, T2, T3, T4>::define<Auto,Expr>(boost::spirit::qi::rule<Iterator, T1, T2, T3, T4> &, const Expr &, boost::mpl::true_) [with Iterator=__gnu_cxx::__normal_iterator<const char *, std::basic_string<char, std::char_traits<char>, std::allocator<char>>>, T1=expr_node (), T2=boost::spirit::ascii::space_type, T3=boost::spirit::unused_type, T4=boost::spirit::unused_type, Auto=boost::mpl::false_, Expr=boost::proto::exprns_::expr<boost::proto::tagns_::tag::shift_right, boost::proto::argsns_::list2<const boost::proto::exprns_::expr<boost::proto::tagns_::tag::subscript, boost::proto::argsns_::list2<boost::spirit::qi::rule<__gnu_cxx::__normal_iterator<const char *, std::basic_string<char, std::char_traits<char>, std::allocator<char>>>, expr_node (), boost::spirit::ascii::space_type, boost::spirit::unused_type, boost::spirit::unused_type> &, const boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::assign, boost::proto::argsns_::list2<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::spirit::attribute<0>>, 0L>, boost::spirit::_1_type>, 2L>> &>, 2L> &, const boost::proto::exprns_::expr<boost::proto::tagns_::tag::dereference, boost::proto::argsns_::list1<const boost::proto::exprns_::expr<boost::proto::tagns_::tag::shift_right, boost::proto::argsns_::list2<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<const char &>, 0L>, const boost::proto::exprns_::expr<boost::proto::tagns_::tag::subscript, boost::proto::argsns_::list2<boost::spirit::qi::rule<__gnu_cxx::__normal_iterator<const char *, std::basic_string<char, std::char_traits<char>, std::allocator<char>>>, expr_node (), boost::spirit::ascii::space_type, boost::spirit::unused_type, boost::spirit::unused_type> &, const boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::assign, boost::proto::argsns_::list2<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::spirit::attribute<0>>, 0L>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list4<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<binary_op_phx>, 0L>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<const char *>, 0L>, boost::spirit::_val_type, boost::spirit::_1_type>, 4L>>>, 2L>> &>, 2L> &>, 2L> &>, 1L> &>, 2L>]" at line 221 of "PATH/boost/boost_1_58_0/include/boost/spirit/home/qi/nonterminal/rule.hpp" instantiation of "boost::spirit::qi::rule<Iterator, T1, T2, T3, T4> &boost::spirit::qi::rule<Iterator, T1, T2, T3, T4>::operator=(const Expr &) [with Iterator=__gnu_cxx::__normal_iterator<const char *, std::basic_string<char, std::char_traits<char>, std::allocator<char>>>, T1=expr_node (), T2=boost::spirit::ascii::space_type, T3=boost::spirit::unused_type, T4=boost::spirit::unused_type, Expr=boost::proto::exprns_::expr<boost::proto::tagns_::tag::shift_right, boost::proto::argsns_::list2<const boost::proto::exprns_::expr<boost::proto::tagns_::tag::subscript, boost::proto::argsns_::list2<boost::spirit::qi::rule<__gnu_cxx::__normal_iterator<const char *, std::basic_string<char, std::char_traits<char>, std::allocator<char>>>, expr_node (), boost::spirit::ascii::space_type, boost::spirit::unused_type, boost::spirit::unused_type> &, const boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::assign, boost::proto::argsns_::list2<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::spirit::attribute<0>>, 0L>, boost::spirit::_1_type>, 2L>> &>, 2L> &, const boost::proto::exprns_::expr<boost::proto::tagns_::tag::dereference, boost::proto::argsns_::list1<const boost::proto::exprns_::expr<boost::proto::tagns_::tag::shift_right, boost::proto::argsns_::list2<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<const char &>, 0L>, const boost::proto::exprns_::expr<boost::proto::tagns_::tag::subscript, boost::proto::argsns_::list2<boost::spirit::qi::rule<__gnu_cxx::__normal_iterator<const char *, std::basic_string<char, std::char_traits<char>, std::allocator<char>>>, expr_node (), boost::spirit::ascii::space_type, boost::spirit::unused_type, boost::spirit::unused_type> &, const boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::assign, boost::proto::argsns_::list2<boost::proto::exprns_::expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::spirit::attribute<0>>, 0L>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list4<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<binary_op_phx>, 0L>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<const char *>, 0L>, boost::spirit::_val_type, boost::spirit::_1_type>, 4L>>>, 2L>> &>, 2L> &>, 2L> &>, 1L> &>, 2L>]" at line 82 of "test.cpp" instantiation of "Grammar<Iterator>::Grammar() [with Iterator=__gnu_cxx::__normal_iterator<const char *, std::basic_string<char, std::char_traits<char>, std::allocator<char>>>]" at line 92 of "test.cpp" I can't make sense of this, as it works fine with gcc or Visual Studio. The original file is far bigger, but this is the smallest grammar I could make that displays this error... If someone knows... Matthieu -- Information System Engineer, Ph.D. Blog: http://matt.eifelle.com LinkedIn: http://www.linkedin.com/in/matthieubrucher Music band: http://liliejay.com/

1 0

Re: [Boost-users] [IPC Named Mutex]
by Lorenzo Trivelli 21 Jul '15

21 Jul '15

Good evening, I've further investigated innto the possible solution I found out to get system boot time under win machines (even if my last post did not have so much success :-D ) After some tries, it seems that the boot time is not always the same, but they are different ALWAYS by 1 ms,Usually in my experience a machine does not boot every 1 ms (:-D) so a possible workaround would be: 1) compute boot time 2) try to open the shared folders with the given boot time 3) if fails, try to add or subtract one ms and repet step 2, if all of them failes then you are sure that id does not exist may it work or is it too cumbersome ? regards L. Trivelli

1 0

asio: async_write handler not called in Linux but called in Windows
by Lloyd 21 Jul '15

21 Jul '15

Hi, I have an application that need to work on both Windows and Linux. We are using asio for network communication (boost 1.57). In this, once the connection is established with the server, the connection handler in client executes the following async calls... boost::asio::async_read_until(Socket, stream, string("\r\n"), boost::bind(&MyConnection::HandleRead, shared_from_this(), boost::asio::placeholders::error)); ... ... ... boost::asio::async_write(Socket,boost::asio::buffer(buff,len), boost::bind(&MyConnection::HandleWrite,shared_from_this(), boost::asio::placeholders::error,boost::asio::placeholders::bytes_transferred)); On Windows, the "HandleWrite" function is called as soon as the data is written. But on Linux this function never gets called!. In Linux and Windows HandleRead is getting called as expected. In bot the the case, the server receives the data properly. Is there any reason for this? Thanks, Lloyd

1 2

Log: Filter expression in file stream init
by Florian Lindner 20 Jul '15

20 Jul '15

Hello, I have this piece of code: http://pastebin.com/iMyyaB6a It adds a file and a console log and reads in a file config: [Core] # Filter="%Severity% > 1" [Sinks.MyConsoleSink1] Destination=Console and prints some messages: using namespace boost::log::trivial; boost::log::sources::severity_logger<severity_level> lg; BOOST_LOG_SEV(lg, trace) << "A trace severity message"; BOOST_LOG_SEV(lg, debug) << "A debug severity message"; BOOST_LOG_SEV(lg, info) << "An informational severity message"; BOOST_LOG_SEV(lg, warning) << "A warning severity message"; BOOST_LOG_SEV(lg, error) << "An error severity message"; BOOST_LOG_SEV(lg, fatal) << "A fatal severity message"; It does exactly what I want, prints each message twice to the console. But when I uncomment the Filter expression it prints nothing. Why not? Severity > 1 means everything info and above, doesn't it? Thanks, Florian

1 2

Test: Aborting at global fixture
by Florian Lindner 17 Jul '15

17 Jul '15

Hello, what is the canonical way of reporting an error that accours at the global fixture: #include <boost/test/unit_test.hpp> struct GlobalFixture { GlobalFixture() { std::cout << master.argc << std::endl; BOOST_FAIL("CRASH BOOM"); } ~GlobalFixture() { std::cout << "Global teardown\n"; } }; BOOST_GLOBAL_FIXTURE(GlobalFixture) Crashes with segfault. Thanks, Florian

2 1

Boost.DLL formal review is ending soon - submit your reviews
by Vladimir Prus 17 Jul '15

17 Jul '15

Boosters, I wanted to remind that the formal review of Boost.DLL library by Antony Polukhin is nearing the end - the last day to submit reviews is Sunday. Of course, not much discussion is likely to happen on Sunday, so if you have any thoughts, sending them on Thursday or Friday will be much appreciated. Thanks in advance! The summary of the library features and review checklists are reproduced below. Boost.DLL is a C++98 library for comfortable work with DLL and DSO. Library provides a portable across platforms way to: - load libraries at runtime - import and export any native functions and variables - make alias names for C++ mangled functions and symbols - query libraries/objects and executables for sections and exported symbols - self loading and self querying - getting program and module location by exported symbol The documentation can be found at: http://apolukhin.github.io/Boost.DLL/index.html and the source can be obtained at: https://github.com/apolukhin/Boost.DLL Please post your reviews on the mailing list and if possible, answer the following questions: - Should the library be accepted? - How useful is it? - What's your evaluation of - Design - Implementation - Documentations - Tests - How much effort did you put into your evaluation? - Did you attempt to use the library? On what systems and compilers? Thanks, Volodya _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

9 10

Problem with boost.log in a multithread application
by Rajalakshmi Iyer 17 Jul '15

17 Jul '15

Hello, I am using Boost.Log to produce 2 logs for a multi-thread application. There are 2 singleton channel_mt loggers corresponding to 2 files. Several threads continuously write different messages to the two loggers. Log file rotation is enabled on both loggers and in the event of rotation, the logs are collected into a different folder. All of this works as expected for a while, except randomly (but surely at some point) - I start seeing a stream of messages like - [2015-Jul-17 01:11:26.532653] (info): *** Exception: boost::filesystem::last_write_time: No such file or directory: "/var/infinity/rtb/auction_log" [2015-Jul-17 01:11:26.532896] (info): Boost Exception - libs/log/src/text_file_backend.cpp(1160): Throw in function void boost::log::v2_mt_posix::sinks::text_file_backend::consume(const boost::log::v2_mt_posix::record_view&, const string_type&) This goes on for a while and then my application hangs. It is not entirely clear whether this incidence happens only during size based rotation or even otherwise. Any pointers on how to approach this issue would be greatly appreciated. Thanks Raj -- This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of BlisMedia Ltd, a company registered in England and Wales with registered number 06455773. Its registered office is 3rd Floor, 101 New Cavendish St, London, W1W 6XH, United Kingdom. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error.

1 0

Is this a known bug in lexical_cast<double> ?
by TILLMAN, MICHAEL D9 16 Jul '15

16 Jul '15

We're using boost 1.51. Management is reluctant to upgrade because the software is for manned space flight and our current boost version has been stable. Wanted to see if there was a known bug with boost::lexical_cast<double>. We're seeing failures on what appear to be valid float strings. When we catch the exception, and simply do a second cast on the same string, the cast succeeds. The Code fragment: try { dVal = boost::lexical_cast<double>(theValue); } catch(boost::bad_lexical_cast &eX) { ... more code ... firstAttemptFailed = true; } // If the first cast succeeded, don't bother to attempt it again. if(firstAttemptFailed == true) { // Let the API throw the actual exception if the second attempt also fails. dVal = boost::lexical_cast<double>(theValue); } The string sequence this fails on is: ... ... "7104", "0.416666699999999999983", "0.22222224", "4.08233160000000000001", "1.81436960000000000002", ... ... It fails on the last string, "1.81.....", in the actual program, but when compiled into a simple test program, it succeeds. If there is a known bug, we may be able to get a Boost upgrade installed. Thanks, Mike

9 12

Re: [Boost-users] Query regarding interest in my submitting plf::colony to Boost
by Colin Humphries 16 Jul '15

16 Jul '15

> I don't think anything related to multithreading should be done by such kind of container. Disturbed by that comment I just wanted to add for the benefit of anyone just starting out with multi-threading that in my experience containers are entirely safe for multi-threading PROVIDED that you're only reading from them (i.e. they are passed by const &). This is by far the most efficient way to pass common information into parallel threads (all threads read the same data). For containers required to return a result, the approach that works for me is to create a vector of containers and dedicate one to each thread. The result containers must be guaranteed to remain in scope until all threads have completed so I usually make them global. The only challenge is how to efficiently coalesce the partial results. Get this wrong (or use too many threads) and the performance gain from multi-threading quickly evaporates. Colin Humphries

2 1

[Graph] pgRouting and boost.graph
by Vicky Vergara 16 Jul '15

16 Jul '15

Hello, We work on the pgRouting project and we are updating our code to use Boost.Graph. For the moment our intention is to have a V2.1 of pgRouting modifying 3 of our routing functions, and I am working on the documentation. I am making references to Boost.Graph, I would like some one from Boost.Graph team to check if the references I am making are according to your requirements and /or give us some suggestions. The following link takes you to the tentative documentation that mentions Boost.Graph. https://github.com/pgRouting/pgrouting/blob/develop_2_1_0/src/dijkstra/doc/… Thanks in advance. Vicky

2 2

Boost graph parallel issue
by Mayank Bakshi 16 Jul '15

16 Jul '15

2 3

How do I build boost with a specific compiler flag?
by Gagnon, Joseph - 0553 - MITLL 15 Jul '15

15 Jul '15

Hello, I am developing a C++ application on a Linux (CentOS 6.6) platform with gcc 4.8.2. I need to build the Boost libraries I'm using (Regex and others) such that the code is compiled with the "-fPIC" (position-independent code) option. I looked around on the Boost web site and found information about a configure script and something called Boost.Config. I quickly got overwhelmed. What do I need to do to have the Boost build system use this flag to build its libraries? Is it something fairly simple, or do I need to invoke a complicated set of steps? Thanks, Joe Gagnon Engineer II Group 53 - Secure Resilient Systems and Technology MIT Lincoln Laboratory Lexington, MA

2 1

[Test] Did This Pass, Or Didn't it?
by Merrill Cornish 15 Jul '15

15 Jul '15

Here is the Boost Test assertion: BOOST_CHECK_EXCEPTION(dummyOpr->setOperand(emptyValue), DiGSE::fail, fail_msg); Here is the test execution log message: info: check 'incorrect exception DiGSE::fail is caught' has passed I have only one exception: *DiGSE::fail* (derived from *std::exception*). It is the /only /exception that appears in the *BOOST_CHECK_EXCEPTION()* assertions. So, what does "incorrect exception *DiGSE::fail*" mean? If *DiGSE::fail* was caught, then that part is correct. If the message means that some /other/ exception was caught, then this is a Really Poor way of phrasing that information. Or, did the predicate return *false* (which, in my case, means the exception message is wrong)? But if the wrong exception was caught /or/ the predicate returned *false*, then why was the assertion declared "has passed"? Merrill Cornish

2 1

Test: Different versions of doc (raffienficiaud)
by Florian Lindner 15 Jul '15

15 Jul '15

Hello, additionally to the official documentation of boost test at [1], I have found a different version at [2]. This looks like the official documentation but describes much more features and more comprehensive. However, although not the development version at [3]. What does the version from raffienficiaud describes? Is this some own extensions of him? Thanks, Florian [1] http://www.boost.org/doc/libs/1_58_0/libs/test/doc/html/index.html [2] http://raffienficiaud.github.io/test/index.html [3] http://svn.boost.org/svn/boost/trunk/libs/test/doc/html/index.html

3 2

Boost.DLL formal review is ongoing
by Vladimir Prus 15 Jul '15

15 Jul '15

The formal review of Boost.DLL library by Antony Polukhin is nearing the end of the first week. As of today, over 100 people read through the library's tutorial, suggesting quite some interest. However, no reviews were submitted yet. Please take the time to post your thoughts - even if you don't have time to do a full review, or try the library, comments on design and interfaces are still very valuable. The summary of the library features and review checklists are reproduced below. Boost.DLL is a C++98 library for comfortable work with DLL and DSO. Library provides a portable across platforms way to: - load libraries at runtime - import and export any native functions and variables - make alias names for C++ mangled functions and symbols - query libraries/objects and executables for sections and exported symbols - self loading and self querying - getting program and module location by exported symbol The documentation can be found at: http://apolukhin.github.io/Boost.DLL/index.html and the source can be obtained at: https://github.com/apolukhin/Boost.DLL Please post your reviews on the mailing list and if possible, answer the following questions: - Should the library be accepted? - How useful is it? - What's your evaluation of - Design - Implementation - Documentations - Tests - How much effort did you put into your evaluation? - Did you attempt to use the library? On what systems and compilers? Thanks, Volodya _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

5 8

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

Subgraph at distance n
by Rossano Schifanella 14 Jul '15

14 Jul '15

Hi all, which is the easiest way to extract from a graph G and a generic node source a subgraph with all the vertices/edges at distance at most n from source? Thanks a lot for your help. Best, Rossano

2 1

Boost.DLL Review is finished
by Vladimir Prus 14 Jul '15

14 Jul '15

Boosters, the formal review of the Boost.DLL library by Antony Polukhin is now finished. The preliminary results are as follows: The following people have provided reviews: - Ralf Globisch - Yes - Klaim - Joël Lamotte - Yes (*) - Niall Douglas - Yes, conditionally - John P Fletcher - Yes - Bjorn Reese - Yes - Edward Diener - Yes Klaim - Joël has asked that his vote is not counted until he's done trying the library for real, and there was no confirmation it's done yet. The following people have contributed, but did not provide a review - Rodrigo Madera - Thomas Trummer - Rob Stewart - Ion Gaztañaga If anybody would like to amend or clarify anything, or plans to provide additional comments during this week, please contact me off-list. I will post final review result after that. Thanks, Volodya

4 5

Platform checks fail on Centos 6 after bootstrap ?
by gabriel nützi 12 Jul '15

12 Jul '15

Hello all :-) Is somebody able to help with the following problem: http://stackoverflow.com/questions/31347026/boost-build-on-centos-6-5-faile… <http://stackoverflow.com/questions/31347026/boost-build-on-centos-6-5-faile…> boost 1.58 used I dont know why platform checks are not done correctly? Thanks a lot!

2 1

[Boost-announce] [boost] [review] Metaparse Review Result
by Christophe Henry 11 Jul '15

11 Jul '15

Hi all, First of all, the final result. Metaparse is formally unconditionally accepted into Boost. We had 11 reviews, all "Yes" votes. 2 "No" reviews based on formality were later reversed to a "Yes". The review was lively, with a general agreement that the library is very useful, the design of high quality and the documentation great. Here are some noticeable quotes which helped me take my decision: - "thank you Abel for submitting such an amazing library. The quality of the documentation and code is wonderful and it has been a pleasure to review Metaparse." (Michael Caisse) - (Design) "Of high quality. Based on the MPL paradigm, but I don't view this as a problem." (Peter Dimov) - "Part of the role of boost is to push compilers to the limit (and sometimes beyond). This library certainly has the capabilities to do so." (Roland Bock) Worth noticing is the review of Gordon Woodhull. I myself wrote a new front-end for MSM using Metaparse, and other use cases were very welcome and Gordon managed to produce one for his compile-time graph library by the end of the review, which I found impressive (for both the reviewer and the library). Thank you for investing time in this review. Another important factor for me for acceptance is how well the author is going to maintain his library. We have too many abandoned libraries. Abel went out of his way to oblige remarks and demands made by reviewers. Long before the reviews he also had obliged my many critics and demands. He also showed himself open for experiments. All this while keeping a very calm and professional tone. This is for me a very good sign of a library which will be well-maintained. Finally, there were some repeated important comments which I see as adressed to the rest of Boost that the library is targeted towards library writers. >From Peter Dimov: > - Are you knowledgeable about the problem domain? "I'm not sure if anybody is. :-)" It all depends on us, library and potential library writers to become knowledgeable about this domain and make this library move from potentially useful to very useful. We need to use it to write more cool libraries. I notice a recurring theme where Boost would be dead or on the way to doom etc etc. Some very popular Boost libraries are now part of the Standard, and so what? We need to make new ones. Metaparse is one of them. Let's build more, using it! Yes Reviews(11): Andrzej Krzemienski Bjorn Reese Gordon Woodhull Lee Clagett Louis Dionne Michael Caisse Paul A. Bristow Peter Dimov Roland Bock Edward Diener Niall Douglas I want to thank all the reviewers who invested their time in this review and those who provided some usefuls comments. I also want to thank Abel for presenting this great library. Christophe Henry Metaparse Review Manager

1 0

Slow decoding in thread
by Gonzalo Garramuno 10 Jul '15

10 Jul '15

I am writing a movie player using boost. I use a condition_variable to control a mutex in one thread that waits for packets of video to be ready for decoding, while another thread feeds those packets. My problem is that the decode thread may end up doing a lot of work when playing backwards and it is not ready to wait on the condition variable when the message comes from the other thread and so it hangs (or so I think). This is my wait loop. I apologize for the use of macros. #define SCOPED_LOCK(mutex) Mutex::scoped_lock lk_##mutex(mutex) #define CONDITION_WAIT( cond, mutex ) cond.wait( lk_##mutex ); void aviImage::wait_image() { mrv::PacketQueue::Mutex& vpm = _video_packets.mutex(); SCOPED_LOCK( vpm ); for(;;) { if ( stopped() || ! _video_packets.empty() ) break; CONDITION_WAIT( _video_packets.cond(), vpm ); } return; } When it returns it tries to decode one or more frames of video taken from _video_packets. The condition variable is notified whenever the program calls push_back() to add a packet. That is: class PacketQueue { .... inline void push_back( AVPacket& pkt ) { Mutex::scoped_lock lk( _mutex ); // assert( pkt.dts != MRV_NOPTS_VALUE ); if ( av_dup_packet(&pkt) < 0 ) { std::cerr << "Could not duplicate packet - not added" << std::endl; return; } _packets.push_back( pkt ); _bytes += pkt.size; _cond.notify_one(); } }; Can somebody suggest an alternative to this scheme? -- Gonzalo Garramuño

1 1

Query: metis_input_exception
by Mayank Bakshi 10 Jul '15

10 Jul '15

1 0

crc updating how?
by U.Mutlu 09 Jul '15

09 Jul '15

Hi, I need to calc the crc chunkwise (ie. calc crc of a block, then continue with the next block etc.). Is this (not) possible with the boost crc? In other words: how can the type "crc_32_type" be initialized with a user supplied uint32_t value? boost::crc_32_type crc; crc = 0x1234; // <-- this brings compile error crc.process_bytes(buf, len); error: no match for ‘operator=’ (operand types are ‘boost::crc_32_type {aka boost::crc_optimal<32ul, 79764919u, 4294967295u, 4294967295u, true, true>}’ and ‘const uint32_t {aka const unsigned int}’) Thx

2 3

[crc] bug in boost::crc
by U.Mutlu 09 Jul '15

09 Jul '15

/* boost-crc-bug-demo.cpp Written by U.Mutlu on 2015-07-09-Th Compile: g++ -O2 -Wall -std=gnu++11 boost-crc-bug-demo.cpp Run: ./a.out Output: crc("The quick brown fox jumps over the lazy dog")=414fa339 crc("The quick brown fox ")=88b075e2 crc("The quick brown fox jumps over the lazy dog")=4ac56d0f ERROR See also: http://www.boost.org/doc/libs/1_58_0/libs/crc/crc.html#usage Conclusion: It doesn't do what it should and also advertises; ie. there's a bug */ #include <boost/crc.hpp> #include <boost/cstdint.hpp> #include <iostream> int main() { uint32_t expected; { const std::string sTxt = "The quick brown fox jumps over the lazy dog"; boost::crc_optimal<32, 0x04C11DB7, 0xFFFFFFFF, 0xFFFFFFFF, true, true> crc; crc.process_bytes(sTxt.data(), sTxt.size()); std::cout << "crc(\"" << sTxt << "\")=" << std::hex << crc.checksum() << std::endl; // save the result for the following test expected = crc.checksum(); } // test: doing the same as above, but now in 2 steps, ie. chunk- or blockwise: std::string sTxt; uint32_t result = 0xFFFFFFFF; for (size_t i = 0; i <= 1; ++i) { sTxt += !i ? "The quick brown fox " : "jumps over the lazy dog"; // using the special ctor for initial remainder stored in "result" boost::crc_optimal<32, 0x04C11DB7, 0xFFFFFFFF, 0xFFFFFFFF, true, true> crc(result); crc.process_bytes(sTxt.data(), sTxt.size()); std::cout << "crc(\"" << sTxt << "\")=" << std::hex << crc.checksum() << std::endl; result = crc.checksum(); } // eval: const std::string sRes = result == expected ? "SUCCESS" : "ERROR"; std::cout << sRes << std::endl; return 0; }

3 4

[Interprocess] posix robust mutex and EOWNERDEAD
by Malko 07 Jul '15

07 Jul '15

Hi, I lurked a bit and found this: http://boost.2283326.n4.nabble.com/boost-interprocess-gt-1-45-robust-mutexe… I didn't feel like necroposting, and it's /dev anyway, so allow me to ask here about updates on the matter. Is there anything, even if only "experimental" or "beta", that you have that would allow me to handle the EWOENERDEAD result? I'd rather use your code before putting my hands on your library, since it would be easier to let my manager (and his manager) deal with a "boost beta" rather than my personal modification to boost. If there is none, I would really need to modify your files for my project to work, and I would appreciate if you could confirm a couple of things for me. In http://stackoverflow.com/a/1179766/4598277 it is mentioned to modify two files: 1. posix/thread_helpers.hpp to set the attribute (first time ever I was happy to get an exception :D) 2. posix/mutex.hpp to handle the EOWNERDEAD return value Can you please confirm if this would be enough? It would seem so to me, but I have only studied parts of your code. Thank you for the assistance. -- View this message in context: http://boost.2283326.n4.nabble.com/Interprocess-posix-robust-mutex-and-EOWN… Sent from the Boost - Users mailing list archive at Nabble.com.

2 3

iterator over boost::tuple
by Uthpal Urubail 06 Jul '15

06 Jul '15

Experts, What is the best way to iterator over boost::tuple and return value? Example: For(int i=0;i<boost::tuples::length<T>::value;i++) { Boost_tuple_example.get<i>(); } Regards, UJ

5 4

Boost python and python sets
by Will Hall 06 Jul '15

06 Jul '15

Hi, I'm struggling to find a way to support python sets with boost. The Python API is well defined, so am unable to switch to Python list type. The API needs to support Python sets for both input and output values. I have output values (from C++ to Python) working as follows with to_python namespace bp = boost::python; template<class T> struct to_python; template<class T> struct to_python<std::set<T> > { to_python() { bp::to_python_converter< std::set<T>, to_python< std::set<T> > >(); } static PyObject* convert(const std::set<T>& set) { bp::list values; for(typename std::set<T>::const_iterator iter=set.begin(); iter!=set.end(); ++iter) { values.append(bp::object(*iter)); } PyObject* result = PySet_New(values.ptr()); return result; } static const PyTypeObject* get_pytype() { return &PySet_Type; } }; BOOST_PYTHON_MODULE(helpers) { to_python< std::set<int> >(); bp:class_<MyClass>() // Define constructor with const std::set& arg // Define method that returns const std::set& arg } But I have no idea how to write an equivalent "from_python" to convert Python set to std::set. Any help would be very appreciated!

1 0

{Serialization] Deserialization of const references
by Mccall, Kurt E. (JSC-EG411) 06 Jul '15

06 Jul '15

As near as I can tell from the documentation http://www.boost.org/doc/libs/1_57_0/libs/serialization/doc/serialization.h… , the following is the way to handle const reference members, which are initialized in the constructor. Serialization seems to be working, from an inspection of the resulting XML file, but after deserialization, the values in the object given by the const reference are wrong and are all zero. Here is my question: Is load_construct_data() below correct? It looks like it is initializing the constant reference from a temporary, but I'm doing the same thing as the example in the documentation. class MyClass1 { friend boost::serialization::access; … }; class MyClass2 { friend boost::serialization::access; const MyClass1 & mc1_; MyClass2 ( const MyClass1 &mc1) : mc1_(mc1) { } ; }; namespace boost { namespace serialization { template<class Archive> inline void save_construct_data( Archive &ar, const MyClass2 *t, const unsigned int file_version) { // mc1_ is a reference and requires special handling -- save it // as a pointer const MyClass1 *mc1 = &t->mc1_ ; ar << boost::serialization::make_nvp("mc1_", mc1); } template<class Archive> inline void load_construct_data( Archive &ar, MyClass2* t, const unsigned int file_version) { MyClass1 *mc1; ar >> boost::serialization::make_nvp("mc1_", mc1); // NOTE: IS THIS INITIALIZING THE REFERENCE FROM A TEMPORARY? ::new(t) MyClass2(*mc1); } Thanks, Kurt

1 0

Problems to use Boost Graph
by Oodini 04 Jul '15

04 Jul '15

Hello, I am trying to understand the boost::dijkstra_shortest_paths() function. I don't understand the second and third arguments. The documentation says they're supposed to be properties map : OUT: predecessor_map(PredecessorMap p_map) The predecessor map records the edges in the shortest path tree, the tree computed by the traversal of the graph. Upon completion of the algorithm, the edges (p[u],u) for all u in V are in the tree. The shortest path from vertex s to each vertex v in the graph consists of the vertices v, p[v], p[p[v]], and so on until s is reached, in reverse order. The tree is not guaranteed to be a minimum spanning tree. If p[u] = u then u is either the source vertex or a vertex that is not reachable from the source. The PredecessorMap type must be a Read/Write Property Map whose key and value types are the same as the vertex descriptor type of the graph. but that doesn't work. I have to use an iterator on the properties map, by using : boost::make_iterator_property_map(pred_map.begin(),vertex_index) Does the documentation need reviewers ?

3 4

Re: [Boost-users] [boost] Boost.DLL formal review is ongoing
by Ralf Globisch 03 Jul '15

03 Jul '15

Hi, Firstly, thanks Anthony for submitting this useful library to boost, and to Vladimir for managing the review. - Should the library be accepted? Yes. I had been meaning to test the library for some time, and with the review reminder finally made some time to do so. My vote of yes is based on my (limited) positive experience with the library, as well as having followed past related discussions on the mailing list, in which many questions are addressed. (http://lists.boost.org/Archives/boost/2014/09/216650.php) I think boost.DLL should be accepted unless someone has a serious/valid reservation as to why this library should not to be accepted. - How useful is it? Very useful. It enabled me to add a test-plugin mechanism to an existing application (Windows and Linux) in a matter of minutes. - What's your evaluation of - Design Looks good to me. Simple to use, with good integration into rest of boost (e.g. file_system). I like the fact that the library is header only and minimal effort was required to integrate plug-in like functionality into an existing application. - Implementation I'm not knowledgeable enough to comment on this. - Documentations Good, the tutorials made it fairly easy to get going and covered my common usage scenarios Code is well commented. - How much effort did you put into your evaluation? About three hours worth of effort, reading through documentation and source code, and using library to create a very simple plug-in mechanism in an existing application. Tested basic plug-in functionality on Windows and Linux. - Did you attempt to use the library? On what systems and compilers? Yes -Linux Ubuntu 14.10 with gcc 4.9.1 with boost 1.57 -Window 7 64-bit with VS 2013 community edition with boost 1.58. Initially made the mistake of not checking the boost version (which had been 1.53 and caused lots of compilation errors.) Minor typo in documentation: Just above the "Full Sources" for tutorial 4 "If we want o make a traditional" should be "If we want to make a traditional" Regards, Ralf >>> Vladimir Prus <vladimir.prus(a)gmail.com> 07/03/15 3:52 PM >>> The formal review of Boost.DLL library by Antony Polukhin is nearing the end of the first week. As of today, over 100 people read through the library's tutorial, suggesting quite some interest. However, no reviews were submitted yet. Please take the time to post your thoughts - even if you don't have time to do a full review, or try the library, comments on design and interfaces are still very valuable. The summary of the library features and review checklists are reproduced below. Boost.DLL is a C++98 library for comfortable work with DLL and DSO. Library provides a portable across platforms way to: - load libraries at runtime - import and export any native functions and variables - make alias names for C++ mangled functions and symbols - query libraries/objects and executables for sections and exported symbols - self loading and self querying - getting program and module location by exported symbol The documentation can be found at: http://apolukhin.github.io/Boost.DLL/index.html and the source can be obtained at: https://github.com/apolukhin/Boost.DLL Please post your reviews on the mailing list and if possible, answer the following questions: - Should the library be accepted? - How useful is it? - What's your evaluation of - Design - Implementation - Documentations - Tests - How much effort did you put into your evaluation? - Did you attempt to use the library? On what systems and compilers? Thanks, Volodya _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost -- This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. Please consider the environment before printing this email. -- This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. Please consider the environment before printing this email.

1 0

[asio] async udp socket latency
by Andrew Hundt 03 Jul '15

03 Jul '15

I'm having difficulty with latency when running an async asio udp socket. I don't have the same problems with an identical application that uses synchronous udp. I'm communicating with a physical device which permits a maximum 5ms latency for each UDP packet, and I'm currently getting a latency of 8ms with a std dev of 0.065ms which is surprisingly precise. I'm on Mac OS X 10.10.4 with Xcode 6.3.2 (6D2105). Here are some of the key details about this problem: - Sync UDP test program - works, staying under 5ms latency 100% of the time for over an hour - Code - main file KukaFRIClientDataTest.cpp <https://github.com/ahundt/grl/blob/master/test/KukaFRIClientDataTest.cpp> - UDP socket communication class KukaFriClientData.hpp <https://github.com/ahundt/grl/blob/master/include/grl/KukaFriClientData.hpp> - Key lines - calls socket.receive_from() then socket.send() at the lowest level. - receive_from call <https://github.com/ahundt/grl/blob/master/include/grl/KukaFriClientData.hpp…> - send call <https://github.com/ahundt/grl/blob/master/include/grl/KukaFriClientData.hpp…> - Async UDP test program - buggy, 8ms w/ 0.065 ms std dev, continuously high latency - Code - main file KukaFRITest.cpp <https://github.com/ahundt/grl/blob/master/test/KukaFRITest.cpp> - High level wrapper class KukaFRIThreadSeparator.hpp <https://github.com/ahundt/grl/blob/master/include/grl/KukaFRIThreadSeparato…> - Low level wrapper class KukaFRI.hpp <https://github.com/ahundt/grl/blob/master/include/grl/KukaFRI.hpp> . - Key lines - calls socket_.async_receive_from() then that handler calls socket_.async_send_to(), which calls the final callback with the results. - async_receive_from call <https://github.com/ahundt/grl/blob/master/include/grl/KukaFRI.hpp#L374> - async_send_to_call <https://github.com/ahundt/grl/blob/master/include/grl/KukaFRI.hpp#L432> Does anyone have insight into why this latency issue may be occurring in the Async UDP version? Thanks. Cheers! Andrew Hundt

5 7

Re: [Boost-users] Boost-users Digest, Vol 4182, Issue 1
by Carl Wallace 02 Jul '15

02 Jul '15

>Date: Wed, 1 Jul 2015 15:04:34 +0900 >From: Kohei Takahashi <flast(a)flast.jp> >To: boost-users(a)lists.boost.org >Subject: Re: [Boost-users] Boost-users Digest, Vol 4181, Issue 1 > >>> Can I get (minimal) reproducible code or more detailed error log? >>> >>> Best, >>> Kihei >> This stripped down code snip is enough to trigger the error when the >>1.58 >> code is in place and compiles fine when the code from 1.54 is >>substituted >> in the place I indicating initially. This code is not intended to do >> anything and I have not run it. I can send the original error message if >> you like too. Will send that privately if you want it. >It should be fixed by https://github.com/boostorg/fusion/pull/87. It worked. Thanks.

1 0

Boost 1.58 and Intel Compiler 15
by Matthieu Brucher 02 Jul '15

02 Jul '15

Hi, Has any one worked with the latest Intel compiler on Linux? I'm hit with some Spirit/Fusion issues that don't arise with gcc 4.8.2 or clang 3.6.0. Quite difficult to diminish the number of lines in my example case, as the errors are different between in project and out of project... Cheers, Matthieu -- Information System Engineer, Ph.D. Blog: http://matt.eifelle.com LinkedIn: http://www.linkedin.com/in/matthieubrucher Music band: http://liliejay.com/

1 1

Re: [Boost-users] Boost-users Digest, Vol 4181, Issue 1
by Carl Wallace 01 Jul '15

01 Jul '15

> >Message: 7 >Date: Tue, 30 Jun 2015 11:08:50 +0900 >From: Kohei Takahashi <flast(a)flast.jp> >To: boost-users(a)lists.boost.org >Subject: Re: [Boost-users] fusion error when compiling graphviz code > using VC2010 >Message-ID: <5591FA32.6070802(a)flast.jp> >Content-Type: text/plain; charset="utf-8" > >Hi Carl, > >On 2015/06/29 20:36, Carl Wallace wrote: >> We have been using Boost's graphviz support for several years and have >> upgraded through a few versions of Boost with no issues in some long >> stable code. However, when we moved to 1.58 our Windows build broke. We >> are still using VC2010, with plans to move to 2015 in the >>not-too-distant >> future. We have not yet tried 1.58 in VC2015. The error message is very >> large but emanates from here: >Can I get (minimal) reproducible code or more detailed error log? > >Best, >Kihei This stripped down code snip is enough to trigger the error when the 1.58 code is in place and compiles fine when the code from 1.54 is substituted in the place I indicating initially. This code is not intended to do anything and I have not run it. I can send the original error message if you like too. Will send that privately if you want it. #include <boost/graph/breadth_first_search.hpp> #include <boost/graph/visitors.hpp> #include <boost/graph/graphviz.hpp> using namespace boost; template <class Name, class ColorMap> class label_writer2 { public: label_writer2(Name _name, ColorMap _color) : name(_name), color(_color) {} template <class VertexOrEdge> void operator()(std::ostream& out, const VertexOrEdge& v) const { } private: Name name; ColorMap color; }; struct VertexProps { }; typedef adjacency_list < vecS, vecS, bidirectionalS, VertexProps> graph_t; typedef property_map<graph_t, std::string VertexProps::*>::type name_map_t; int _tmain(int argc, char* argv[]) { std::ostringstream oss; graph_t m_graph; name_map_t m_nameMap; two_bit_color_map<property_map<graph_t, vertex_index_t>::const_type>color_map(num_vertices(m_graph), get(vertex_index, m_graph)); boost::write_graphviz(oss, m_graph, label_writer2<name_map_t, two_bit_color_map<property_map<graph_t, vertex_index_t>::const_type> >(m_nameMap, color_map)); return 0; }

2 1

boost log linking
by Lane 01 Jul '15

01 Jul '15

I'm working with boost log examples (v1.55) of trivial logging and having issues linking against these libraries. I'm receiving these errors. undefined reference to `boost::log::v2s_mt_posix::core::get()' undefined reference to `boost::log::v2s_mt_posix::core::set_filter(boost::log::v2s_mt_posix::filter const&)' In function `main': undefined reference to `boost::log::v2s_mt_posix::trivial::logger::get()' undefined reference to `boost::log::v2s_mt_posix::trivial::logger::get()' undefined reference to `boost::log::v2s_mt_posix::trivial::logger::get()' undefined reference to `boost::log::v2s_mt_posix::trivial::logger::get()' undefined reference to `boost::log::v2s_mt_posix::trivial::logger::get()' more undefined references to `boost::log::v2s_mt_posix::trivial::logger::get()' follow What I don't understand is that I have the correct paths to where the shared libs are located in my make file (-L/usr/lib64) and also included the libs (-lboost_log -lboost_setup). I have these boost libs on my system. /usr/lib64/libboost_log_setup-mt.so /usr/lib64/libboost_log-mt.so /usr/lib64/libboost_log_setup.so /usr/lib64/libboost_log.so /usr/lib64/libboost_log_setup.so.1.55.0 /usr/lib64/libboost_log.so.1.55.0 /usr/lib32/libboost_log_setup-mt.so /usr/lib32/libboost_log-mt.so /usr/lib32/libboost_log_setup.so /usr/lib32/libboost_log.so /usr/lib32/libboost_log_setup.so.1.55.0 /usr/lib32/libboost_log.so.1.55.0 Anyone see what I'm doing wrong?

1 0

Thinking in HDF5
by nitin chandra 30 Jun '15

30 Jun '15

Hello All, I have been on this for a long time and have done a lot of research / reading on this topic, HDF5. To use it for development of in-house software for design calculation of various alignments. A lot many time the basic alignment information is picked from a map / satellite imageries. Kilometre, ground level, geographic feature on the proposed route, etc. , in a csv file. Any where between 7-9 files are generated for each alignment. 1. How to read / write data into the HDF5 file ? What after creating root ? 2. In a regular situation, I have 2 input file with 3 column csv data, and 2 output files. How to do that within the same root ? Will be working in Python and c / c++. This is just the basic. If I can do this much, I can do the rest, hopefully :) Thanks to All Nitin PS :- Will post in scipy-user list too.

2 2

fusion error when compiling graphviz code using VC2010
by Carl Wallace 30 Jun '15

30 Jun '15

We have been using Boost's graphviz support for several years and have upgraded through a few versions of Boost with no issues in some long stable code. However, when we moved to 1.58 our Windows build broke. We are still using VC2010, with plans to move to 2015 in the not-too-distant future. We have not yet tried 1.58 in VC2015. The error message is very large but emanates from here: boost/include/boost-1_58\boost/fusion/container/list/cons.hpp(86): error C2664: 'boost::xpressive::detail::alternates_list<Head,Tail>::alternates_list(cons t Head &,const boost::fusion::nil &)' : cannot convert parameter 1 from 'const boost::fusion::cons_iterator<Cons>' to 'const boost::xpressive::detail::static_xpression<Matcher,Next> &’ I am not familiar with the fusion or xpressive libraries, but after picking through the error messages and review of diff of changes since 1.54 (the version we are moving from), this looks like a template specialization problem. The problem is rooted in a regex that uses xpressive in the escape_dot_string function in the graphviz library. In 1.58 the function at the line identified in the error snip above is defined as follows: template <typename Sequence> BOOST_CONSTEXPR BOOST_FUSION_GPU_ENABLED cons( Sequence const& seq, typename boost::enable_if< mpl::and_< traits::is_sequence<Sequence>, mpl::not_<is_convertible<Sequence, Car> > > // use copy to car instead >::type* /*dummy*/ = 0 ) : car(*fusion::begin(seq)), cdr(fusion::next(fusion::begin(seq)), mpl::true_()) {} When we replace this with the following implementation from 1.54 the build works and it appears the desired functionality is working (though more testing is required). template <typename Sequence> BOOST_CONSTEXPR BOOST_FUSION_GPU_ENABLED cons( Sequence const& seq, typename boost::disable_if< mpl::or_< is_convertible<Sequence, cons>, // use copy ctor instead is_convertible<Sequence, Car> // use copy to car instead > >::type* /*dummy*/ = 0 ) : car(*fusion::begin(seq)), cdr(fusion::next(fusion::begin(seq)), mpl::true_()) {} Any thoughts? The new code in 1.58 builds and runs fine with no mods on OS X. We have not tried Linux yet.

2 1

[msm] is that correct behavior?
by Sam Fisher 29 Jun '15

29 Jun '15

Hi Christophe, For an fsm with orthogonal regions if any region rejects an event (guard returns false), the library blocks all anonymous transitions. for example, an fsm has two regions. Region 0 returns HANDLED_TRUE, region 1 returns HANDLED_GUARD_REJECT for the same event. region_processing_helper combines it into a single "HANDLED_TRUE | HANDLED_GUARD_REJECT" value. However function process_event_internal<> (state_machine.hpp) creates handle_eventless_transitions_helper that takes (handled == HANDLED_TRUE) as a condition for allowing transitions. should it be (handled & HANDLED_TRUE)? as a result, fsm is stuck in event that has an anonymous transition to another event. PS. I've seen the same condition (handled == HANDLED_TRUE) in do_post_handle_deferred function, but I do not use deferred events so I did not check that part.

2 1