July 2008 - Boost - lists.preview.boost.org

[filesystem] Resolving a path ?
by Loïc Joly 15 Jul '08

15 Jul '08

Hello, I'd like to know if there is in boost::filesystem a way to "resolve" a path. For instance, I have a path that is built from : "c:\foo1\foo2\..\bar1\bar2" And I'd like to obtain: "c:\foo1\bar1\bar2" Best regards, -- Loïc

4 5

[extension] Suggestion: Loading shared libraries from memory
by Robert Dailey 15 Jul '08

15 Jul '08

Hi, I'm not a huge expert on shared libraries, however I was wondering if there's a portable way to support loading libraries from a memory buffer instead of from the file system. If this is possible, could it be added as a feature to Boost.Extension? Thanks for reading!

3 3

[rfc] dual-mode regression testing
by joaquin＠tid.es 15 Jul '08

15 Jul '08

Hello, As it stands now, most testing force goes to the trunk of SVN, which is good. The problem is that there are few regression runners running against the release branch, and I think we have a trade off: a regression runner volunteer will choose to work on either the trunk or the release branch, but taking care of both is possibly too much of a hassle. It is assumed that the release branch is much cleaner and thus needs less attention, but it's better to be safe than sorry wrt this. My proposal is then: why not modify the regression tool code so that it operates by default in *dual mode*, i.e. it automatically downloads two tarballs (trunk & release) to different folders, test them separately and upload the results to the appropriate destinations? From the point of view of a volunteer, setting this to work is as simple as having it running only against one branch, and the only drawback is that resource consumption doubles, but this might be acceptable to a fair number of people. Comments? Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

[parameter][accumulators] test failures on release branch
by Richard Webb 15 Jul '08

15 Jul '08

(reposting this in it's own thread, to make sure it doesnt get lost). The release branch parameter/accumulator tests are showing a large number of failures due to a missing #include <boost/type_traits/is_convertible.hpp> in boost/parameter/aux_/tagged_argument.hpp e.g. http://tinyurl.com/642sgq Thanks, Richard Webb

2 1

Re: [boost] [pool] segfault (fun with static initialization ordering)
by joaquin＠tid.es 15 Jul '08

15 Jul '08

Chris Newbold escribió: >> From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] >> On Behalf Of JOAQUIN M. LOPEZ MUÑOZ >> Sent: Friday, July 11, 2008 11:35 AM >> >> BTW, have you tried the fix I was proposing? >> > > Not yet. I'm on vacation this week, but I will try it as soon as possible. My only concern is whether referencing singleton_default from the constructor for fast_pool_singleton will guarantee proper initialization ordering. > > 3.6.2 doesn't really shed any light on how ordered and unordered initialization may be coupled. There isn't, for example, any expressed guarantee that non-locals will be initialized prior to first reference. > There is no such guarantee indeed, but the fix does NOT rely on initialization rules for non-local objects, but on the initialization rules for *local* objects with static storage duration (6.7/4): the singleton is a local static object inside the function singleton_default<T>::instance(), which is explicitly invoked inside fast_pool_allocator ctors via singleton_pool<...>is_from() (if you apply the fix, that is). The non-local object involved in singleton_default<T>, namely singleton_default<T>::create_object is there to guarantee that singleton_default<T>::instance() is invoked, and thus the singleton created in dynamic initialization time *if no one has done it before*. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

a new release of Join - asynchronous concurrency library
by Yigong Liu 15 Jul '08

15 Jul '08

Hello, I just uploaded a new version of Join library to Vault under Concurrent Programming. Based on the feedback from list, the following changes are made: . add schedulers as actor's template policy class . add timed synchronous calls . add doc and samples for port based API . add more doc about Join internals. For people who are not familiar with the librayr. Here is a simple description: Join is an asynchronous, message based C++ concurrency library based on join calculus. It is applicable both to multi-threaded applications and to the orchestration of asynchronous, event-based applications. It follows Comega's design and implementation and builds with Boost facilities. It provides a high level concurrency API with asynchronous methods, synchronous methods, and chords which are "join-patterns" defining the synchronization, asynchrony, and concurrency. website and download: http://channel.sourceforge.net Any comments and suggestions are highly appreciated. Thanks Yigong

1 0

Streaming Lambda functions
by Robert Jones 14 Jul '08

14 Jul '08

Is it possible to invoke user defined streaming operators within boost lambda functions? In this style #include <iostream> #include <map> #include "boost/lambda/lambda.hpp" using namespace std; ostream & operator << ( ostream & ostrm, pair<string, string> const & input ); ostream & operator << ( ostream & ostrm, map<string, string> & inputs ) { using namespace boost :: lambda; for_each ( inputs.begin( ), inputs.end( ), ostrm << _1 << '\n' ); return ostrm; } Is this basically undoable, or am I doing it wrong? Also, does the online Comeau compiler understand the boost include directives? Thanks, Rob.

5 14

z/OS supported
by Dr. Franz Fehringer 14 Jul '08

14 Jul '08

Hello all, Is z/OS (recent version assumed) with USS (Unix System Services) a supported configuration with respect to the boost library components? Cheers Franz

2 1

Re: [boost] Bind question, is there any way to implicitly go through a reference_wrapper?
by Michael Goldshteyn 14 Jul '08

14 Jul '08

Sorry, post got garbled, here it is again: #include <boost/bind.hpp> #include <boost/ref.hpp> #include <string> // Define a simple class for our example class Crayon { public: explicit Crayon(const std::string &color=std::string()):m_color(color) {} const std::string &GetColor() const {return m_color;} private: std::string m_color; }; int main(int argc, char *argv[]) { using namespace std; using namespace boost; Crayon cr("blue"); boost::reference_wrapper<const Crayon> crefCr(cr); // This compiles std::string color(boost::bind(&Crayon::GetColor,_1)(cr)); // This also compiles, using an explicit get on crefCr std::string colorFromConstRef(boost::bind(&Crayon::GetColor,boost::bind(&boost::referenc e_wrapper<const Crayon>::get,_1))(crefCr)); // This doesn't compile, however, even though the reference_wrapper class template has // an overloaded operator T& () const function std::string colorFromConstRef2(boost::bind(&Crayon::GetColor,_1)(crefCr)); }

1 0

unmerged changes in boost function
by Emil Dotchevski 14 Jul '08

14 Jul '08

I can see that the new allocator semantics in boost::function have not been merged into the release branch. I would volunteer to do the merge but it seems like there are some other changes that I'm not familiar with. Doug, how should this be handled? I would hate 1.36 to go out without the new allocator support for boost::function as I already have code that depends on it. :) Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode

2 1