December 2012 - Boost - lists.preview.boost.org

[release][thread] Permission to merge.
by Vicente J. Botet Escriba 19 Dec '12

19 Dec '12

Hi, I would like to merge this change [1][82094] It is related to this feature request [2](#7422 Provide a condition variable with zero-overhead performance penality), but we can consider it as a bug, as the performance were degraded since boost.1.45. After the change the performances have been improved consequently as showed in [3] trunk-ni-7422 in green respect to trunk-ni in orange. [1] https://svn.boost.org/trac/boost/changeset/82094 [2] https://svn.boost.org/trac/boost/ticket/7422 [3] https://docs.google.com/spreadsheet/ccc?key=0Ai_v0rSH1AXrdHl2RDN4UkFYNHZ2aX… Please, could I merge it after the regression test cycle? Best, Vicente

2 1

Should I use std::get or boost::get (or both) in Boost.Array
by Marshall Clow 19 Dec '12

19 Dec '12

I've got a feature request for Boost.Array to provide compile-time checked access to the members of an array. In C++11, this is done using std::get<Idx> (std::array). Fine, I can specialize this in Boost.Array - well, for C++11. I can't specialize a nonexistent template in namespace std for C++03 (well, I _can_ but the standard says I must not). But Boost.Tuple has a get<> template. I believe I can specialize that for Boost.Array, w/o stepping on Boost.Tuples code. What do people think? boost::get? std::get? Both? -- Marshall Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki

2 4

Re: [boost] Heads up - string_ref landing
by Yanchenko Maxim 19 Dec '12

19 Dec '12

Marshall. low <mclow.lists. at> gmail.com> writes: > Please let me know what you think! As probably everyone, we have our own device for this. Here are some points and experience we gathered. 1. This class is essentially just an iterator_ range<char*> (modulo template for const/wchar_t), so it should either inherit from it or have corresponding converting ctors/operators. In this sense Olaf/Gennadiy's remarks are pretty valid. OTOH size is needed very frequently and having it precomputed is a good thing, so conversion approach seems to be better (but then we lose passing by reference as iterator_range, type_traits etc). I'm not sure what's more important. 2. Given the above, the name is misleading as it's not a reference to std::string. We use name char_range. 3. It's worth having a static constructor 'literal' (templated with size) to construct char_ranges from literals - as the compiler knows their size in compile time (minus zero terminator). It can be a constexpr too. Same manner - static function 'from_array', embrasing an array of chars in whole, assuming there is no zero terminator - useful for working with structures representing messages in char-based protocols with fixed-width fields. 4. (hack) We had to add a member function 'assign' (this is just operator=) to make boost::tokenizer return char_ranges. I don't like this part at all as it contradicts the meaning of say std::vector::assign, so I'd prefer another solution, probably in form of a customization point in boost::tokenizer. Thanks, Maxim

20 115

[Git] Boost website changes?
by Beman Dawes 18 Dec '12

18 Dec '12

The www.boost.org web site content needs to be reviewed, and all the Subversion references and instructions changed to Git and modular Boost. What is the best way to handle that? Create a branch similar to beta.boost.org? Who is willing to take on the management of updating web site content and monitor progress? --Beman

3 2

[Container] 'to_pointer' problem since 1.52
by Rich E 18 Dec '12

18 Dec '12

Just wanted to point out that there's an outstanding bug report due to some changes in Boost.Container that seem to have occured somewhere in the 1.52 dev cycle, reported here <https://svn.boost.org/trac/boost/ticket/7650>. In a nutshell, there is a compile time error caused by boost::container::list::const_iterator is trying to use a method called 'to_pointer' that doesn't exist (there is a 'pointer_to' method defined). We're using a modified version of boost/container/list.hpp at the moment, but it would be nice to ditch that come 1.53. The patch is so trivial that I thought it best to leave it up to the maintainer, as I really have no idea how to work with the current svn setup. cheers, Rich

2 1

Another set of macros to deprecate (and then remove)?
by Marshall Clow 18 Dec '12

18 Dec '12

There are a set of macros in Boost.config that describe "features that are not required by the C++ standard" Some of these features have been incorporated into C++11. I propose that we retire these macros, and have people use the shiny C++11 versions. In particular: BOOST_HAS_STATIC_ASSERT should be ! BOOST_NO_CXX11_ASSERT BOOST_HAS_VARIADIC_TMPL should be ! BOOST_NO_CXX11_VARIADIC_TEMPLATES BOOST_HAS_RVALUE_REFS should be ! BOOST_NO_CXX11_RVALUE_REFERENCES BOOST_HAS_CHAR_16_T should be ! BOOST_NO_CXX11_CHAR_16_T BOOST_HAS_CHAR_32_T should be ! BOOST_NO_CXX11_CHAR_32_T I'm using "!" here generically; in code you would replace #ifdef OLD_MACRO with #ifndef NEW_MACRO etc. I don't think this will be very disruptive; very few boost libraries use these macros. Opinions? Other macros that fit into this group? -- Marshall Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki

8 12

compilation warning on HEAD
by Gaetano Mendola 18 Dec '12

18 Dec '12

The HEAD in trunk have some compilation warnings using gcc 4.7.2 the following will fix some of those. Another warning about unused result is in here: libs/serialization/src/basic_iarchive.cpp line 576, the value is used in a BOOST_ASSERT, I don't know how you manage those cases. Regards Gaetano Mendola Index: libs/serialization/src/basic_serializer_map.cpp =================================================================== --- libs/serialization/src/basic_serializer_map.cpp (revision 81900) +++ libs/serialization/src/basic_serializer_map.cpp (working copy) @@ -43,8 +43,7 @@ BOOST_ARCHIVE_DECL(bool) basic_serializer_map::insert(const basic_serializer * bs){ // attempt to insert serializer into it's map - const std::pair<map_type::iterator, bool> result = - m_map.insert(bs); + m_map.insert(bs); // the following is commented out - rather than being just // deleted as a reminder not to try this. Index: boost/archive/iterators/transform_width.hpp =================================================================== --- boost/archive/iterators/transform_width.hpp (revision 81900) +++ boost/archive/iterators/transform_width.hpp (working copy) @@ -112,6 +112,7 @@ transform_width(BOOST_PFTO_WRAPPER(T) start) : super_t(Base(BOOST_MAKE_PFTO_WRAPPER(static_cast< T >(start)))), m_buffer_out_full(false), + m_buffer_in(), m_remaining_bits(0), m_end_of_sequence(false) {} @@ -119,8 +120,8 @@ transform_width(const transform_width & rhs) : super_t(rhs.base_reference()), m_buffer_out_full(rhs.m_buffer_out_full), + m_buffer_in(rhs.m_buffer_in), m_remaining_bits(rhs.m_remaining_bits), - m_buffer_in(rhs.m_buffer_in), m_end_of_sequence(false) {} }; -- cpp-today.blogspot.it

4 4

[Git] Documentation for Git and Modular Boost conversion
by Beman Dawes 18 Dec '12

18 Dec '12

We are starting to pull together documentation for the Git and Modular Boost conversion. https://svn.boost.org/trac/boost/wiki/WikiStart#GitandModularBoost Comments and corrections welcome! I'm particularly interested in unanswered questions you have after reading these initial docs. --Beman

20 98

static_vector using aligned_storage
by Adam Wulkiewicz 18 Dec '12

18 Dec '12

Hi, I'm developing R-tree container for Boost.Geometry. To keep it short, there are containers of Values in leaf nodes. Those containers must have push_back() functionality. For static-size nodes I'm using a container based on boost::array. Unfortunately this means that default constructors of stored Values are called when the container is created. I'd like not to expect that Values have their default ctor implemented. I've implemented an alternative container using boost::aligned_storage. This is just a proof of concept. The code is available here: https://svn.boost.org/svn/boost/sandbox-branches/geometry/index/tests/stati… I've searched for this kind of container in Boost since I remember that someone proposed it some time ago but didn't find it anywhere. Is it released somewhere? Maby as a part of some library? If not, would you be so kind and see if my solution should work for any/most popular compiler/platform? I've tested it only on clang. To be specific, won't there be any problems with the memory aligmnent if I use this code for storage: boost::aligned_storage<sizeof(Value) * Capacity> m_storage; this for access: *(reinterpret_cast<Value*>(m_storage.address()) + i); and this for construction new (reinterpret_cast<Value*>(m_storage.address()) + i) Value(value); Regards, Adam

8 26

[range] Adapter to select class member
by Mark Snelling 17 Dec '12

17 Dec '12

Hi, I'm not sure if this has already been done but I have created a new Boost.Range adapter that will return a specified member variable of the class in the range, similar to the existing map_keys and map_values adapters. Would there be interest in this? For example consider the following code: #include <boost/range/adaptor/member.hpp> #include <boost/range/algorithm/copy.hpp> #include <boost/lexical_cast.hpp> #include <iostream> #include <vector> #include <string> struct A { int foo; std::string bar; }; int main(int argc, char* argv[]) { std::vector< A > input; for ( int i = 0; i < 10; ++i ) { A a; a.foo = i; a.bar = boost::lexical_cast< std::string >( i * 10 ); input.push_back( a ); } boost::copy( input | boost::adaptors::selected_member( &A::foo ), std::ostream_iterator< int >( std::cout, "," ) ); std::cout << std::endl; boost::copy( input | boost::adaptors::selected_member( &A::bar ), std::ostream_iterator< std::string >( std::cout, "," ) ); return 0; } Cheers, Mark

2 1

[crypto]not in https://github.com/boost-vault
by Jeff Flinn 16 Dec '12

16 Dec '12

It appears the crypto library that was in: http://www.boost-consulting.com/vault/index.php?action=downloadfile&filenam… Didn't get moved to https://github.com/boost-vault. Does anyone have access to the last vault incarnation? Thanks, Jeff

2 2

[release] permission to merge atomic and lockfree
by Tim Blechmann 16 Dec '12

16 Dec '12

hi all, apparently boost.atomic has been abandoned. i must admit, i'm very disappointed that the original author did hardly reacted neither on-list nor off-list. furthermore, it is blocking the release of boost.lockfree, so i'm volunteering to maintain this library. i'd rather see helge bahmann coming back and taking over responsibility for his code, but frankly, i lost all hopes that this is going to happen. iac, i'd like to get permission from the release managers to merge both atomic and lockfree to the release branch. thanks, tim

6 15

[GitHelp] Help desk support for developers moving to Git and modular Boost
by Beman Dawes 15 Dec '12

15 Dec '12

Documentation will aid developers moving to Git and modular Boost. See https://svn.boost.org/trac/boost/wiki/WikiStart#GitandModularBoost Beyond documentation, simply asking questions via a search engine works particularly well for Git. There is a vast amount of Git material available on the web, including some excellent YouTube videos. But documentation, web searches, and YouTube videos are not enough. Learning Git can be daunting - Git has more surface area than Subversion and it isn't obvious at first why some operations need to be done in a certain sequence or in a certain way or why they even need to be done at all. Two or three developers at C++Now mentioned that they became discouraged when they inadvertently got painted into a Git corner and couldn't find a way out. And even experienced git uses occasionally run into something they need human help with. This post proposes a virtual "Help Desk" to provide Boost specific answers to the inevitable questions that will come up during the transition to Git and modular Boost. The idea is that postings with at [GitHelp] subject tag will signal a request for help wrt Git or modular Boost. Anyone who can help should jump right in with a response. Comments? Suggestions? --Beman

3 2

[graph] A* search applied to knight's tour
by Dave Abrahams 15 Dec '12

15 Dec '12

Hi, I was just trying to work up an example for a class I'm teaching, to illustrate implicit graphs. The following shows how far I've gotten: https://gist.github.com/4153918 This is attempting to apply Warnsdorff's heuristic (choose the next move with the least out-degree) using A* search. I'm running into several problems having to do with the requirements of astar_search_no_init. In particular, the requirement that we can assign an index to every vertex is quite painful, since enumerating all the possible vertices in the search space is difficult. Any advice here? I suppose I could keep a real map and simply assign indices in the order vertices are encountered, but that seems pretty ugly to me. Any hints? -- Dave Abrahams BoostPro Computing Software Development Training http://www.boostpro.com Clang/LLVM/EDG Compilers C++ Boost

2 4

Deadline extension: C++ Now 2013, Call for Submissions
by Hartmut Kaiser 15 Dec '12

15 Dec '12

Please see below for the extended deadline. ---------------------------------------------------------------------------- C++ NOW CONFERENCE 2013 - Aspen CO, USA, May 13-17, 2013, www.cppnow.org ---------------------------------------------------------------------------- CALL FOR SUBMISSIONS -------------------- We invite you to submit session proposals to the 2nd annual C++ Now Conference (Aspen CO, USA, May 13-17, 2013). Building upon the resounding success of C++ Now 2012 and five years of BoostCon, C++ Now 2013 will present leading speakers from the whole C++ community. The C++ Now Conference is dedicated to discussion and education about C++, an open and free language and standard. Our Conference will focus on discussion and education about open source software usage and developments in the C++ developer and user community. To reflect the breadth of the C++ and Boost communities, the conference includes sessions aimed at three constituencies: C++ and Boost end-users, hard-core Boost library and tool developers, and researchers pushing the boundaries of computation. The program fosters interaction and engagement within and across those groups, with an emphasis on hands-on, participatory sessions. As a multi-paradigm language, C++ is a melting pot where the most compelling ideas from other programming communities are blended in powerful ways. Historically, some of the most popular sessions at C++ Now have highlighted these concepts, from DSLs to functional programming to transactional memory and more. Bring your C#, Python, Ruby or Haskell influences to bear in an environment that will broaden their exposure. At C++ Now 2013 we would like to focus on parallel and distributed computing with C++. However, by no means this is intended to restrict the topics of proposals we hope to see. Any other topic related to C++ as outlined below is perfectly fine for submission. IMPORTANT DATES --------------- New proposal submissions due: January 5th, 2013. Proposals decisions sent (tentative program available): January 30th, 2013. Fully scheduled program available: February 24th, 2013. BEST PRESENTATION AWARDS ------------------------ We know how much effort it takes to prepare talks for our conference. For this reason we will award the best presentations in the following categories: Best Presentation, Best Short Presentation, Best Tutorial, and Best Workshop. The awards will be given based on the audience's voting. Each award will include the author's name listed on the cover of the C++ Now website for that year and a plaque containing all the C++ Now conference information. SESSION TOPICS -------------- Topics of interest include, but are not restricted to, the following: * Parallelism in the new C++11 standard * Parallel, distributed and GPGPU topics relating to C++ * C++11 and how it changes life for users and library writers * General tutorial sessions on C++11, the C++11 Standards library, and one or more Boost libraries * In-depth sessions on using specific Boost libraries * Case studies on using Boost * Experts panels * Advanced sessions on implementation techniques used within Boost libraries * Development workshops to extend or enhance existing Boost libraries * Workshops on design process * Infrastructure workshops such as Build tools, Website, Testing * Concepts and Generic Programming * Hardware and infrastructure presentations focused on how libraries can make better use of the technology * Software development tools and their application to C++ and or Boost * Other topics likely to be of great interest to C++ users and developers Interactive and collaborative sessions are encouraged, as this is the style of learning and participation that has proven most successful at such events. Sessions can be tutorial based, with an emphasis on interaction and participant involvement, or workshop based, whether hands-on programming or paper-based, discussion-driven collaborative work. SESSION FORMATS --------------- Presentations Presentations focus on a practitioner's ideas and experience with anything relevant to C++11, Boost and users. Panels Panels feature three or four people presenting their ideas and experiences relating to C++11 and Boost's relevant, controversial, emerging, or unresolved issues. Panels may be conducted in several ways, such as comparative, analytic, or historic. Tutorials Tutorials are sessions at which instructors teach conference participants specific skills relevant to C++11 and Boost. Workshops Workshops provide an active arena for advancements in Boost-relevant topics. Workshops provide the opportunity for experienced practitioners to develop new ideas about a topic of common interest and experience. Author's Corner Presentations These were introduced at BoostCon 2008, and were a great success. They are short (30 minute) sessions, focusing on tips on usage and design. In addition, we're looking to uncover the hidden design gems in Boost libraries. Tool Vendors Presentations We actively encourage tool vendors and ISP's to submit proposals for a special Tool Vendors Session Track aimed at products related to Boost and C++ (compilers, libraries, tools, etc.). Other formats may also be of interest. Don't hold back a proposal just because it doesn't fit into a pigeonhole. SUBMITTING A PROPOSAL --------------------- Standard Sessions are 90 minutes. You may submit a proposal for fractions Or multiples of 90-minutes. Fractional proposals will be grouped into 90 Minute sessions covering related topics. Longer sessions, such as tutorials and classes, will be assigned three hour (i.e. half day), or six hour (i.e. full day) time slots. Please include: * The working title. * Type of session: presentation, panel, tutorial, workshop, authors corner, vendor track, other. * A paragraph or two describing the topic covered, suitable for the conference web site. * Proposed length: 10-20 minute short talks, 45 minutes, 90 minutes, half day, full day. * Alternate lengths, if you are willing to make adjustments: 10-20 minute short-talks, 45 minutes, 90 minutes, half-day, full day. * Audience: users, developers, both. * Level: basic, intermediate, advanced. * A biography, suitable for the conference web site. * Your contact information (will not be made public). SUBMISSION DETAILS ------------------ All submissions should be made through the EasyChair conference management system: http://www.easychair.org/conferences/?conf=cppnow2013. If you have not already registered at EasyChair, you will need to do so in order to submit your proposal. All submissions will go through a peer review process. Authors are invited (but are not required) to submit PDF versions of full papers of up to 10 pages in ACM conference proceedings format (see http://www.acm.org/sigs/publications/proceedings-templates) The full papers are not required unless you want them published in the proceedings. All accepted proposals will be made available in the Association for Computing Machinery (ACM) Digital Library (approval pending). Best papers, after further reviews, will be considered to be book chapters or journal articles in a renowned journal. The session materials go on the C++ Now website and will be available to attendees. For general information on the C++ Now 2013 paper submission or the scope of technical papers solicited; please refer to the conference website at www.cppnow.org. For any other questions about the submission process or paper format, please contact the Program Committee at cppnow2013(a)easychair.com. If you have any technical problems with EasyChair, please contact EasyChair for help. Note: Presenters must agree to grant a non-exclusive perpetual license to publish submitted materials, either electronically or in print, in any media related to C++ Now. Hartmut Kaiser, email: hartmut.kaiser(a)gmail.com (Program Committee Chair) Dave Abrahams, email: dave(a)boostpro.com (Conference Chair) On behalf of the conference organizers

1 0

[system] Add noexcept to conform with C++11
by Vicente J. Botet Escriba 14 Dec '12

14 Dec '12

Hi, any news on https://svn.boost.org/trac/boost/ticket/7278. I could add them if you don't have the time now. Best, Vicente

6 18

[test] Getting an execution monitor to ignore a failed child processes
by Daniel James 14 Dec '12

14 Dec '12

Hi, A couple of days ago the inspect report was failing on the release branch and not the trunk branch (not currently, because I reverted the change which caused it). It turns out that this happened because inspect uses the program execution monitor. Inspect runs subversion to get the version information, but I wasn't running it in a subversion checkout, so the child process fails, which causes a signal which the execution monitor detects, throwing an exception. I guess it's thrown from the top level, so I can't catch it. I've got a patch ready which fixes this by running subversion from inside a nested execution monitor so that the exception is thrown at a more appropriate location. But this is a bit verbose, is there a better way to handle this? Perhaps temporarily stop the program execution monitor from handling failed process signals? I don't want to disable it for the rest of the program. Secondly, this doesn't happen on trunk. It looks like the program execution monitor isn't detecting the failure. This might be a bug in the new version. thanks, Daniel

1 0

[Proposal] Adding CPUID Library in Boost
by Shakti Misra 14 Dec '12

14 Dec '12

Hi All, Any interest in a cross platform CPU ID library? For a application I wanted to get the CPUID mostly to check the SSE2 status. So I missed it in Boost. So any interest for it? I am currently evaluating the library http://libcpuid.sourceforge.net/ This has a permissive license that I think can go with the Boost license. I mailed the author also, although he does not use boost, he told he can give any fixes or support needed. ~Thanks smisra

7 19

[odeint] Regression tests fail for unknown reason
by Karsten Ahnert 14 Dec '12

14 Dec '12

On some machines all of odeints regression tests in the release branch fail for an unknown reason (http://www.boost.org/development/tests/release/developer/numeric-odeint.html) Does anyone know what happens here?

4 4

Re: [boost] [Boost-testing] [odeint] Regression tests fail for unknown reason
by Vicente J. Botet Escriba 14 Dec '12

14 Dec '12

Le 13/12/12 21:40, Vicente J. Botet Escriba a écrit : > Le 13/12/12 21:28, Daniel James a écrit : >> On 13 December 2012 20:21, Vicente J. Botet Escriba >> <vicente.botet(a)wanadoo.fr> wrote: >>> Maybe, but I don't think so. All the Boost.Thread test are failling, and >>> most of them don't use Boost.Test. >>> The problem is that here is no information. What is happening with the >>> regression test results? >> I tried it on my machine: >> >> darwin.compile.c++ >> ../../../bin.v2/libs/thread/build/darwin-4.7x/debug/link-static/threading-multi/pthread/thread.o >> ../../../libs/thread/src/pthread/thread.cpp: In member function 'bool >> boost::thread::joinable() const': >> ../../../libs/thread/src/pthread/thread.cpp:398:34: error: cannot >> convert 'boost::detail::thread_data_ptr {aka >> boost::shared_ptr<boost::detail::thread_data_base>}' to 'bool' in >> return >> ../../../libs/thread/src/pthread/thread.cpp:399:5: warning: control >> reaches end of non-void function [-Wreturn-type] >> >> So it's shared_ptr's explicit bool? >> > Yes. I need to merge from trunk. I believed that I did it already :( > 06:01 Changeset /[81788]/ by viboes > <https://svn.boost.org/trac/boost/changeset/81788> > > Thread: fix shared_ptr implicit conversion to bool introduced in > [81780] <https://svn.boost.org/trac/boost/changeset/81780> > > I will take care also of the merge of Boost.Test > > 06:43 Changeset /[81791]/ by viboes > <https://svn.boost.org/trac/boost/changeset/81791> > Test: fix shared_ptr implicit conversion to bool introduced in > [81780] <https://svn.boost.org/trac/boost/changeset/81780> > why we are not able to see the comile errors on the regression test results? Vicente

2 2

Boost.Process: Formal review request
by Boris Schaeling 14 Dec '12

14 Dec '12

I'd like to ask for a formal review of the library which is known as Boost.Process 0.5: - Docs: http://www.highscore.de/boost/process0.5/ - Code: http://www.highscore.de/boost/process0.5/process.zip Since 2006 a lot of people spent a tremendous amount of work on a process management library for Boost. Since then Boost.Process went through two GSoC projects, had a formal review in 2011 where it got rejected, was discussed at BoostCon, went through a complete overhaul afterwards, spun off boost::asio::windows::object_handle and got a sponsorship. In fact the library is around for so long and has attracted so much interest that it could be called a de facto Boost library. People call it Boost.Process, and there are some who use the library in their projects. The main reason why Boost.Process is under construction for six years: Differences between the supported platforms Windows and POSIX. There are other libraries like Boost.Asio or Boost.Interprocess which have to deal with platform differences, too. But in their case no core functionality is affected. Classes like boost::asio::posix::stream_descriptor or boost::interprocess::windows_shared_memory are nice to have, and no one is worried that they only work on one platform. Boost.Process has to deal with platform differences in core functions. For example, resource leaking is unacceptable (zombie processes on POSIX and open HANDLEs on Windows when child processes exit). Given that platforms are very different two extreme solutions are possible: Abstract away differences at all costs. Or tell the library user to call platform-specific system functions. As none is satisfactory, a balance between these extremes has to be found. But where this balance should be exactly can be discussed with no end. Someone has to make a decision at some point, and that will be another important role for the review manager. :) Looking back at what has been accomplished since the first review, I think Boost.Process 0.5 is a huge step forward: * The library is now fully customizable. While previous versions had a function called launch() which was immutable, the current version is based on things called executors and initializers. An executor is basically a struct with member variables which will be passed as arguments to a system function to spawn a child. Initializers set those member variables. Library users pick initializers provided by Boost.Process or define their own to setup executors. * Boost.Process 0.5 is cleaner and more focused as it makes better use of other Boost libraries. For example, previous versions had their own stream classes. They were removed in the current version - Boost.Iostreams is used instead. Now Boost.Process doesn't reinvent concepts or reimplement functions anymore which belong in other libraries. All of that makes me believe it's time for a new review. Boris

5 9

[Interprocess] Experimental Win32 Mutexes
by Brink, Robert (GE Aviation, US) 13 Dec '12

13 Dec '12

I'm running Boost 1.52 on Windows 7, Visual Studio 2010. I noticed in sync\interprocess_mutex.hpp there is a windows mutex implementation that is hidden behind the BOOST_INTERPROCESS_FORCE_GENERIC_EMULATION macro. The comment indicates that it is "Experimental". Could someone shed some light on what is Experimental about it and what the general plans for this feature are? I was having a problem with many processes all spin-locking when allocating shared memory that I traced down to the old mutex implementation for shared memory. I enabled the experimental feature in my local build ( by commenting out the above macro in the detail\workaround.hpp file) and it seems to fix my problems. My performance is much improved. But what are my risks for using this implementation? I'm a little nervous to depend on something marked as "Experimental". Thanks Rob Brink

3 5

[Interprocess] Managed mapped file questions
by Jorge Lodos Vigil 13 Dec '12

13 Dec '12

Hi First of all, thank you for boost interprocess :-) I have a couple of questions: 1. When you grow a managed mapped file, the current implementation fills all the new space with zeroes. This is less efficient than just resizing the file. The comments in the code implies there is a reason, so what is it? 2. When the size to map is too small, take 1 or 2 bytes for instance, the library fails in a non elegant way. This is a corner case, but I could not find this documented. Is this a bug? I'm asking this before sending any sample code or creating tickets, but of course I could do that as well if there is the need. Thanks again. Cheers Jorge

2 4

[Container][Move] #if defined(BOOST_MOVE_USE_STANDARD_LIBRARY_MOVE): boost::move_backward is undefined
by Hartmut Kaiser 13 Dec '12

13 Dec '12

Hey, If BOOST_MOVE_USE_STANDARD_LIBRARY_MOVE is defined, then compiling Boost.Container fails because its missing boost::move_backward. Patch is attached. Ok to commit? Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu

2 3

Boost.Process 0.5: And another minor update
by Boris Schaeling 13 Dec '12

13 Dec '12

I've uploaded a new version of Boost.Process 0.5 to <http://www.highscore.de/boost/process0.5/>: - First command line argument passed to set_args is used as a path to the executable to start - No escaping of command line arguments anymore with set_args (see <http://article.gmane.org/gmane.comp.lib.boost.devel/236137>) - Updated documentation Boris

4 6