- Boost - lists.boost.org

Boost filesystem and windows drives
by jrg＠dsl.pipex.com 13 Feb '05

13 Feb '05

Boost filesystem paths checked using filsystem::windows_name cannot contain a colon (":"). But the standard way to specify a particular drive in Windows is to use a colon (e.g. "C:\Windows"). Shouldn't colons be allowed for specifying a drive in Windows? Thanks, James

2 1

[config] How to test for GCC <= 4.0
by Jonathan Turkanis 12 Feb '05

12 Feb '05

Hi, I have a workaround which I want to apply to all known versions of GCC but not to future versions unless I later determine that it is necessary. Currently I have something like this: #if !defined(BOOST_INTEL) && ( BOOST_WORKAROUND(__GNUC__, <= 3) || \ BOOST_WORKAROUND(__GNUC__, == 4) && \ BOOST_WORKAROUND(__GNUC_MINOR__, BOOST_TESTED_AT(0)) ) \ /**/ ... #endif but I can see from the regression reports that GCC 4.0 is not picking up the workaround code. What am I doing wrong? Jonathan .

2 3

Singleton Library Ready for Review
by Jason Hise 12 Feb '05

12 Feb '05

Recent changes: * The dependency lifetime now works by using the pointers themselves as dependencies, and using lazy creation to determine whether creation of the pointer or dereferencing of the pointer creates the instance. Using the pointer instead of a separate dependency class allows the lifetime to achieve a consistent interface with the other lifetime policies. * All lifetime policies now work uniformly for Singletons, Multitons, and potentially any Somethingtons that an end user might choose to implement (HashedMultiton, TwoKeyedMultiton, etc...). The only caveat is that the Multiton instance holder (a singleton used in the implementation of the multiton), must use a leaky lifetime. If any other type of lifetime is used, combining the longevity lifetime policy with the multiton ends up being disastrous. If the OS cleans up leaked memory when the program exits, this should not be a problem. Even so, I would like to find a better solution if possible. Because I have no experience with multi threading, I need someone to verify that I am locking in all of the right places, and that any singleton/multiton operations that need to be thread safe actually are thread safe. A sample test program is provided below, whose lifetime policies can be easily edited to verify order of creation and destruction in all circumstances. I am fairly confident that my singleton library is now complete. What are the next steps to take in adding it to Boost? -Jason // Sample Program #include <sstream> #include <fstream> #include "../Include/StaticAllocator.h" #include "../Include/MallocAllocator.h" #include "../Include/LongevityLifetime.h" #include "../Include/Singleton.h" #include "../Include/Multiton.h" using namespace boost::singleton; using std::stringstream; using std::ofstream; class TestLog : public Singleton < TestLog, LongevityLifetime < TestLog, 10 > > { private: ofstream out; protected: TestLog ( ) : out ( "log.dat" ) { out << "Test log created.\n"; } ~ TestLog ( ) { out << "Test log destroyed.\n"; out.close ( ); } public: void Write ( const char * msg ) { out << msg; } }; class A : public Multiton < int, A, LongevityLifetime < A, 5 > > { private: TestLog :: Pointer log; protected: A ( ) { log->Write ( "A created.\n" ); } ~ A ( ) { log->Write ( "A destroyed.\n" ); } }; // lifetime longevity higher than A, to verify that even though A is created first, it is still destroyed after B class B : public Singleton < B, LongevityLifetime < B, 7 > > { private: TestLog :: Pointer log; A :: Pointer a1; A :: Pointer a2; A :: Pointer a3; protected: B ( ) : a1 ( 0 ), a2 ( 1 ), a3 ( 1 ) { log->Write ( "B created.\n" ); } ~ B ( ) { log->Write ( "B destroyed.\n" ); } public: void foo ( ) { log->Write ( "foo called.\n" ); } }; int main ( ) { B::Pointer ptr; ptr->foo ( ); }

5 16

CVS has a stale lock
by Carlo Wood 12 Feb '05

12 Feb '05

This is majorly annoying, can this be fixed ASAP please? cvs checkout: Updating boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:46:22] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:46:52] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:47:22] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:47:52] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:48:22] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:48:53] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:49:23] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:49:53] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:50:23] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:50:53] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:51:23] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:51:53] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:52:23] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:52:53] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:53:23] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:53:53] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:54:23] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:54:53] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:55:23] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:55:53] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:56:23] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:56:53] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:57:23] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:57:53] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:58:23] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:58:53] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:59:23] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [04:59:53] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:00:23] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:00:53] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:01:23] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:01:53] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:02:23] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:02:53] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:03:23] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:03:53] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:04:23] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:04:53] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:05:23] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:05:54] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:06:24] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:06:54] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:07:24] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:07:54] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:08:24] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:08:54] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:09:24] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:09:54] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:10:24] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:10:54] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:11:24] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:11:54] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:12:24] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:12:54] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:13:24] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:13:54] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:14:24] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:14:54] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:15:24] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib cvs checkout: [05:15:54] waiting for david_abrahams's lock in /cvsroot/boost/boost/tools/build/v1/example/sublib_use/sublib etc -- Carlo Wood <carlo(a)alinoe.com>

2 1

unit-test always seg-faulting
by amerio 12 Feb '05

12 Feb '05

Hello, We are trying to use boost unit test framework for our unit tests. It works fine, except it will always seg fault when quitting. Even the smallest simplest empty test will seg fault. Compiler is gcc 2.95.4, on a Woody Debian. Compiling with -g -pg -pthread Linking with -g -pg -lboost_thread-gcc-mt -lboost_unit_test_framework-gcc-1_32 unit_test.cpp is only : #define BOOST_AUTO_TEST_MAIN #include <boost/test/auto_unit_test.hpp> #include <iostream> BOOST_AUTO_UNIT_TEST(autofct) { std::cout <<"ok" << std::endl; } Seg fault is when calling dispose(), in shared_count::release() (line 147) Thanks for your help.

2 1

Unordered associative containers and swap's exception safety
by Daniel James 12 Feb '05

12 Feb '05

Hello everyone, I've got an exception safety problem implementing the hash containers. The draft standard says (from 6.3.1.1): 'For unordered associative containers, no swap function throws an exception unless that exception is thrown by the copy constructor or copy assignment operator of the container's Hash or [equality] Pred object (if any).' This is a problem, because for the container to be valid, its hash buckets, equality predicate and hash function need to consistent. Since both the hash and predicate can throw, this is impossible (or hard?) to achieve. If swapping/copying the first one succeeds, and the second one throws they won't match. Any ideas on what I should do? I don't think this can cause any major problems, like memory leaks or access to unowned memory, but it can cause unpredictable behaviour - since equal keys can end up in different buckets. Basically the invariant ends up totally broken. The only solution that I've come up with, is to store the two function objects in a seperate structure, allocated on the heap, so that only pointers have to be swapped. But this seems unfortunate since most function objects won't throw. This problem also applies to the copy assignment operator. Daniel

3 3

RE: [boost] new version of profiling library
by Brian Braatz 12 Feb '05

12 Feb '05

I will not be able to deeply look at this til tomorrow. But my initial reaction is THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU :) > -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of christopher diggins > Sent: Friday, February 11, 2005 4:36 PM > To: Boost mailing list > Subject: [boost] new version of profiling library > > The profiling library has been updated in a big way. > The new files are at: > > http://www.cdiggins.com/profiler/v2/profiler.hpp > http://www.cdiggins.com/profiler/v2/profile_manager.hpp > http://www.cdiggins.com/profiler/v2/high_resolution_timer.hpp > > and as a special treat for Brian there is: > > http://www.cdiggins.com/profiler/v2/custom_profile_manager.hpp > > This last version shows one possible way of using the current library to > associate meta-data with profiles. Instead of using a multi-index > internally, I push the data into a multi-index to generate a custom > report. > I am not super happy with this version, it is more complicated than I > would > like, but it does work. > > Christopher Diggins > Object Oriented Template Library (OOTL) > http://www.ootl.org > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

new version of profiling library
by christopher diggins 12 Feb '05

12 Feb '05

The profiling library has been updated in a big way. The new files are at: http://www.cdiggins.com/profiler/v2/profiler.hpp http://www.cdiggins.com/profiler/v2/profile_manager.hpp http://www.cdiggins.com/profiler/v2/high_resolution_timer.hpp and as a special treat for Brian there is: http://www.cdiggins.com/profiler/v2/custom_profile_manager.hpp This last version shows one possible way of using the current library to associate meta-data with profiles. Instead of using a multi-index internally, I push the data into a multi-index to generate a custom report. I am not super happy with this version, it is more complicated than I would like, but it does work. Christopher Diggins Object Oriented Template Library (OOTL) http://www.ootl.org

1 0

Proposal for an extension of the boost::signals::connection interface
by Frantz Maerten 11 Feb '05

11 Feb '05

I took a look at libsidc++ and found very interresting the way of blocking/unblocking connections. I added some small modifications in boost::signals lib in order to have this functionality (2 patches in attachment to apply at the parent of the boost_1_32_0 distrib). Only the interface of connection has changed (3 new methods), and I added a boolean flag in basic_connection struct. Also, a functor is_callable was added in the file connection.hpp, in replacement of the is_disconnected functor (used in the class slot_call_iterator). So, my questions are: 1) is it interresting/useful to incorporate it (for me, yes of course)? 2) is it a safe implementation? You can test it like that: \code void fct1(int) ; void fct2(int) ; MySignal sig ; boost::signals::connection conn = sig.connect(&fct1) ; sig(10) ; // call fct1 and fct2 conn.block() ; sig(20) ; // call only fct2 conn.unblock() ; sig(30) ; // call fct1 and fct2 \endcode --Frantz

1 0

RE: [boost] [Signals] Named slot group usage?
by Brian Braatz 11 Feb '05

11 Feb '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Doug Gregor > Sent: Friday, February 11, 2005 12:40 PM > To: boost(a)lists.boost.org > Subject: Re: [boost] [Signals] Named slot group usage? > > On Feb 11, 2005, at 3:21 PM, Brian Braatz wrote: > > What about allowing the internal type to be policy\traited? > > > > i.e. I can use a vector instead of a map<> > > That gets really messy, really quick, and I only really know how to > give sane semantics for list<> and map<>. > I'm against policies except in very extreme circumstances. > > > and is it possible to allow for meta-data while you're at it? > > Worry not, we'll find a way to get meta-data into slots :) > > Doug > [Brian Braatz] (Imagine an entire football stadium standing up and cheering!) OR (just me :) )

1 0