http://blog.gmane.org/gmane.comp.lib.boost.devel hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.lib.boost.devel/231143 <pre>:: bump :: On Tue, May 22, 2012 at 11:13 AM, Jeffrey Lee Hellrung, Jr. &lt; jeffrey.hellrung&lt; at &gt;gmail.com&gt; wrote: I was hoping to get some direction regarding the above before continuing to; specifically, what should be done about this particular changeset, and some guidelines for similar situations in the future. (I am aware of the recently revised release schedule, so disregard the "request to merge" in that context.) Thanks, - Jeff _______________________________________________ Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost </pre> Jeffrey Lee Hellrung, Jr. 2012-05-26T19:12:04 http://comments.gmane.org/gmane.comp.lib.boost.devel/231140 <pre>Hi, where can I get the source and documentation for the proposed Boost.PImpl? The doc link points to a paper and the source link points to github. Best, Vicente _______________________________________________ Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost </pre> Vicente J. Botet Escriba 2012-05-26T17:12:01 http://comments.gmane.org/gmane.comp.lib.boost.devel/231139 <pre>Hi, the link http://svn.boost.org/svn/boost/sandbox/big_number/libs/multiprecision/doc/html/index. is broken. Best, Vicente _______________________________________________ Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost </pre> Vicente J. Botet Escriba 2012-05-26T17:07:01 http://comments.gmane.org/gmane.comp.lib.boost.devel/231137 <pre>Hi, Will Boost.Range (including the change of boost::size from signed to unsigned) be merged into release? Regards, Barend _______________________________________________ Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost </pre> Barend Gehrels 2012-05-26T10:45:53 http://comments.gmane.org/gmane.comp.lib.boost.devel/231132 <pre>When using clang with -fno-rtti, the use of `typeid` results in either compile-time errors or run-time errors. But Boost.Config did not define BOOST_NO_TYPEID for that case. So, for example, including any client header of BOOST_SP_TYPEID produced compiler errors on clang trunk with -fno-rtti. This was fixed in r78510 about a week ago: (http://svn.boost.org/trac/boost/changeset/78510) -#if !__has_feature(cxx_rtti) +#if !__has_feature(cxx_rtti) &amp;&amp; !defined(BOOST_NO_RTTI) # define BOOST_NO_RTTI #endif +#if !__has_feature(cxx_rtti) &amp;&amp; !defined(BOOST_NO_TYPEID) +# define BOOST_NO_TYPEID +#endif If Boost would like to enhance the support of -fno-rtti on clang, it would be good to merge the fix into the release branch. I ran the test runner (clang trunk with -fno-rtti) for unpatched release branch and patched release branch. There was no regression and more than 1000 test results got improved. Regards, Michel _______________________________________________ Unsubscribe &amp; othe</pre> Michel Morin 2012-05-25T22:59:26 http://comments.gmane.org/gmane.comp.lib.boost.devel/231130 <pre>Hello all, Boost.Python uses operator keywords in macro expansion. This is a bad idea because on some compilers like MSVC that implement and, or, etc using macros #define to &amp;&amp;, ||, these macros will not expand correctly when ciso646 is included before including python.hpp. #include &lt;ciso646&gt; // boost/python/operators.hpp BOOST_PYTHON_BINARY_OPERATOR(and, rand, &amp;) BOOST_PYTHON_BINARY_OPERATOR(or, ror, |) ... This will actually expand to: BOOST_PYTHON_BINARY_OPERATOR(&amp;&amp;, rand, &amp;) BOOST_PYTHON_BINARY_OPERATOR(||, ror, |) And then expand the macro causing a compiler error because the operator code will have names like op_&amp;&amp;, op_||, etc instead of the intended op_and, op_or, etc. An easy and safe fix should be to change the macro to move the _ to the macro call: BOOST_PYTHON_BINARY_OPERATOR(_and, rand, &amp;) BOOST_PYTHON_BINARY_OPERATOR(_or, ror, |) Now _and, _or, etc are no longer keywords so it's safe to use them. --Lorenzo -- View this message in context: http://boost.2283326.n4.nabble.com/boost-pyth</pre> lcaminiti 2012-05-25T15:37:45 http://comments.gmane.org/gmane.comp.lib.boost.devel/231129 <pre>Hello all, I build a Boost.Python module and install it using bjam as follow: python-extension pydef : deduced_params_pydef.cpp : &lt;library&gt;/boost/python//boost_python &lt;library&gt;/boost/regex//boost_regex &lt;link&gt;shared:&lt;define&gt;BOOST_REGEX_DYN_LINK=1 ; install pydef_install : pydef : &lt;install-dependencies&gt;on &lt;install-type&gt;SHARED_LIB &lt;install-type&gt;PYTHON_EXTENSION &lt;location&gt;. ; I the same dir I have a python script deduced_params_pydef.py which will import the module and test it. How do I run the python script automatically from bjam so to fully compile and test the module that my code generates? Something like (this doesn't work of course): # Make sure pydef target is built first, then runs python deduced_params_pydef.py run-py pydef_install : deduced_params_pydef.py ; Thanks a lot. --Lorenzo -- View this message in context: http://boost.2283326.n4.nabble.com/boost-python-run-python-script-from-bjam</pre> lcaminiti 2012-05-25T14:18:50 http://comments.gmane.org/gmane.comp.lib.boost.devel/231127 <pre>Hi, Is there something changed in Boost.Range? Background: I just noticed that there appeared many failing issues (yellow squares) in the Boost.Geometry regression matrix here: http://www.boost.org/development/tests/trunk/developer/geometry.html I checked the assemble square and it gives me an assertion: Assertion `id.ring_index &gt;= -1 &amp;&amp; id.ring_index &lt; boost::size(interior_rings(polygon))' Because this did not use to be the case, I did run the test on my local machine and it was OK. Then I updated some Boost libraries (manually, separately) and as soon as I updated Boost.Range this exception did appear. So the regression is somehow caused by a change in Boost.Range. I did not yet research it further, it might be that we do something wrong here that was previously accepted but now is not, but it still stays an unexpected regression... Is there someone who has any idea what introduced this? Thanks, Barend _______________________________________________ Unsubscribe &amp; other changes: http://li</pre> Barend Gehrels 2012-05-25T11:46:14 http://comments.gmane.org/gmane.comp.lib.boost.devel/231125 <pre>Hello Christophe, I'm using Boost.MSM version 1.49.0. I bumped on a suspicious behavior. See the attached diagram and code. When Event1 occurs in State1, Action1 is invoked. I think the event isn't consumed correctly. If the transition from State1 to State2 connect State2 directly instead of Entry1, the event seems to be consumed. What do you think? Thanks, Takatoshi _______________________________________________ Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost</pre> Takatoshi Kondo 2012-05-25T08:48:54 http://comments.gmane.org/gmane.comp.lib.boost.devel/231118 <pre>Hello all, Some of my library regression tests occasionally fail like this: http://www.boost.org/development/tests/release/developer/Sandia-darwin-intel-11-1-local_function-intel-darwin-11-1-add_except_seq-variants_.html If you follow the link, there is no actual error. Plus the tests sometimes it fails (with no actual error) and other times it passes (as it should). Is this just a problem with the regression test parsing script? Thanks a lot. --Lorenzo -- View this message in context: http://boost.2283326.n4.nabble.com/boost-regression-tests-fail-with-no-error-tp4630458.html Sent from the Boost - Dev mailing list archive at Nabble.com. _______________________________________________ Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost </pre> lcaminiti 2012-05-24T12:35:15 http://comments.gmane.org/gmane.comp.lib.boost.devel/231099 <pre>I'm trying to deal with having multiple orthogonal submachines that process one event containing data. I have a contrived example that hopefully conveys the issue. Suppose I am hoping to create a state machine "Game2D" with a set of orthogonal submachines that guard certain transitions based on each other, and I would like some events to be processed by multiple submachines. Parent Machine: Game2D Event: CharacterStatus - contains character position and velocity Submachines: IsMoving - changes state based on CharacterStatus CorrectPosition - updates position based on CharacterStatus CharacterStatusUpToDate - times out to an error state if CharacterStatus hasn't been received for a while EnemyAlive - doesn't process CharacterStatus RunSystem - guards some transitions based on the state of IsMoving Since some, but not all of these submachines needs the "CharacterStatus" event, what is the best way to make sure they all get it when I call Game2D.process_event(CharacterStatus)? I want to be able to reuse th</pre> Andrew Hundt 2012-05-23T19:40:30 http://comments.gmane.org/gmane.comp.lib.boost.devel/231091 <pre>https://svn.boost.org/trac/boost/wiki/ReleaseSchedule has been updated to reflect experience and lengthen the beta period. https://svn.boost.org/trac/boost/wiki/ReleasePractices/ManagerCheckList has been updated to reflect the importance of the calendar. The Google calendar itself has been updated for releases 1.50.0, 1.51.0, and 1.52.0. I'm looking into ways to queue postings of release milestones so they get sent automatically and don't get forgotten. Thanks, --Beman _______________________________________________ Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost </pre> Beman Dawes 2012-05-23T16:36:32 http://comments.gmane.org/gmane.comp.lib.boost.devel/231072 <pre>Hello everyone, It's time to fill in the release notes, they're at: https://svn.boost.org/svn/boost/website/public_html/live/feed/history/boost_1_50_0.qbk Note that from now on, that this is on the live site, not the beta site. If you don't know quickbook syntax, don't worry, I'll clean it up before regenerating the page. You can see the html output at: http://www.boost.org/users/history/version_1_50_0.html It isn't automatically updated, so you'll only see your changes when I update it. But if that's too much for you, you can email me and I'll sort it out. It's probably better for you if do it yourself, as there's always the chance that an email will slip through the cracks, and it will be easier for you to fix typos and link errors later on. Also, please don't link to changesets in the history, if you don't have something to link to, just create a ticket, accept it and close it with a message like: "Fixed in trunk in [1234]. fixed in release in [5678]". It's also a good idea to add a more detailed c</pre> Daniel James 2012-05-23T10:24:13 http://comments.gmane.org/gmane.comp.lib.boost.devel/231052 <pre>AMDG I'd like to request a formal review of the TypeErasure library that I've posted about several times before here. The TypeErasure library is a generalization of boost::any and boost::function. It allows easy composition of arbitrary type erased operators. As an example of basic usage, we can simulate Boost.Any: any&lt;mpl::vector&lt;copy_constructible&lt;&gt;, typeid_&lt;&gt; &gt; &gt; x(10); int i = any_cast&lt;int&gt;(x); // i == 10 The library is available in the Boost Sandbox at http://svn.boost.org/svn/boost/sandbox/type_erasure/ You can download archives with pre-built documentation from http://sourceforge.net/projects/steven-watanabe.u/files/ Online documentation can be found here: http://steven_watanabe.users.sourceforge.net/type_erasure/libs/type_erasure/ In Christ, Steven Watanabe _______________________________________________ Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost </pre> Steven Watanabe 2012-05-22T20:34:14 http://comments.gmane.org/gmane.comp.lib.boost.devel/231033 <pre>Hi list. Rumor has it that C++Now! is now over, and people are slowly returning to reality. What I wonder is if anything relevant to our lives was discussed or revealed at the conference. I know how easy it is at a conference or workshop to completely forget about the people out there that are not present when things are discussed or presented. If I recall correctly, there were to be some modularisation/VCS presentation from the Steering Committee, and I'm sure that you lads all had some lovely brainstorms and fistfights over beer and pizza. Come on, spill the beans. What did you all decide that will have an influence on the lives of us mortals going forward? </pre> Lars Viklund 2012-05-22T16:01:06 http://comments.gmane.org/gmane.comp.lib.boost.devel/231027 <pre>..\..\../boost/test/utils/runtime/config.hpp: In function 'void boost::runtime::putenv_impl(boost::runtime::cstring, boost::runtime::cstring)': ..\..\../boost/test/utils/runtime/config.hpp:95:51: error: 'putenv' was not declared in this scope This is preventing me from testing other Boost libraries that use Boost.Test:-( --Beman _______________________________________________ Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost </pre> Beman Dawes 2012-05-22T13:39:50 http://comments.gmane.org/gmane.comp.lib.boost.devel/231022 <pre>Although there has been general agreement that there should be more time between beta and final releases, we haven't nailed down the exact duration. To get discussion started, I'll propose five weeks as the target time between beta and final release. Since there needs to be a week for final regression tests to cycle and release candidates to be tested, that would allow four weeks for beta fixes to be incorporated. Comments? --Beman _______________________________________________ Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost </pre> Beman Dawes 2012-05-22T12:48:12 http://comments.gmane.org/gmane.comp.lib.boost.devel/231021 <pre>C++Now! is history, so it is high time to get the 1.50.0 beta out the door. Branches/release is now closed for all changes except by permission from a release manager. Unless there are strong objections, I suggest we close branches\release for all changes next Monday, May 28, and ship the beta release as soon after that as a RC can be built and tested. I'm about to post a separate message discussing the length of beta periods. --Beman _______________________________________________ Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost </pre> Beman Dawes 2012-05-22T12:46:39 http://comments.gmane.org/gmane.comp.lib.boost.devel/231019 <pre>Does anybody have experience pulling Boost into IBM's Rhapsody UML tool, such that Rhapsody will be able to use Boost in UML models and UML to C++ codegen? _______________________________________________ Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost </pre> David Hagood 2012-05-21T22:41:21 http://comments.gmane.org/gmane.comp.lib.boost.devel/231005 <pre> While I was in Aspen I split Spirit and Spirit Classic into separate Git repositories: https://github.com/boost-lib/spirit https://github.com/boost-lib/spirit_classic The manifest entries begin here, and as you can see, are quite long for these two libraries: https://github.com/ryppl/boost-modularize/blob/master/manifest.txt#L643 This is mostly due to the limited expressivity of the manifest language, but regardless... The question, for Spirit developers: which arrangement is better? Should both spirits go back into a single repository? </pre> Dave Abrahams 2012-05-21T16:40:22 http://comments.gmane.org/gmane.comp.lib.boost.devel/230989 <pre>There would seem to be a missing include for enable_if in /boost/range/algorithm/for_each.hpp... shows up from change 18502. _______________________________________________ Unsubscribe &amp; other changes: http://lists.boost.org/mailman/listinfo.cgi/boost</pre> Richard Crossley 2012-05-20T10:50:21 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.lib.boost.devel