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

Boost::shared_ptr and CPP_UNIT
by Barry79 13 Nov '10

13 Nov '10

Hi there, In my unit test I do something like this - void setup() { m_a = ptr_t(new A()); m_b = ptr_t(new B(m_a)); m_c = ptr_t(new C()); m_b->Register(m_c); } void tearDown() { } I was wondering if I should be implementing anything in tearDown (like calling reset on these shared pointers) where I would normally call delete, and if so, why? Thanks, Barry -- View this message in context: http://boost.2283326.n4.nabble.com/Boost-shared-ptr-and-CPP-UNIT-tp3040738p… Sent from the Boost - Users mailing list archive at Nabble.com.

1 0

bug in date time library? local_microsec_clock::local_time() gives compilation error
by dobrov 12 Nov '10

12 Nov '10

hello Just simple call: boost::local_time::local_microsec_clock::local_time(). gives compilation error in boost header: /usr/include/boost/date_time/microsec_time_clock.hpp:116: error: no matching function for call to 'boost::local_time::local_date_time_base<boost::posix_time::ptime, boost::date_time::time_zone_base<boost::posix_time::ptime, char> >::local_date_time_base(boost::gregorian::date&, boost::posix_time::time_duration&)' I use boost 1.42 and gcc 4.4.5 I have information, that the same problem occurs with boost 1.44 and Sisual Studio. Is it a bug in library? best regards ---------------------------------------------------------------------- Najlepsza wyszukiwarka tanich lotĂłw! SprawdĹź >>> http://linkint.pl/f284a

1 0

Converting between two different enumerations
by John Dlugosz 12 Nov '10

12 Nov '10

I'm looking at a lot of boilerplate code where two different enumerations are used for the same semantic meaning, and a pair of functions (a bit switch statement) converts one to the other. In this case, all the values are #define constants, not typed enumerations. But there are lots of such pairs. I'm wondering if there is a simple "bi-map" class that can take a list of pairs and produce the effect of both functions. If one of the lists of values is consecutive it should be especially easy to initialize. - TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and subscription company, and TradeStation Europe Limited, a United Kingdom, FSA-authorized introducing brokerage firm. None of these companies provides trading or investment advice, recommendations or endorsements of any kind. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

2 1

[BGL] property_map for or with bundled properties
by Cedric Laczny 12 Nov '10

12 Nov '10

Hi, I was trying to use an iterator_property_map with bundled properties and ran into difficulties. For those having thought about that, I want to post my solution and also address a question. Let's start with the solution: Imagine, one uses bundled properties and has defined the following EdgeProperty: struct EdgeProperty{ int edge_index; } and typedef adjacency_list<...> Graph; Whether this makes sense or not may also be discussed but is not important for the demonstration purposes. So if you now want to define an iterator_property_map that is based on the edge_index, it get's IMHO a bit more complicated than using internal properties: typedef property_map<Graph, int EdgeProperty::*>::type EdgeIndexMap; EdgeIndexMap e_index = get(&EdgeProperty::edge_index,g); std::vector< int > flag_vec(num_edges(g), 0); // Create the external property map iterator_property_map< std::vector< int >::iterator, EdgeIndexMap > flags(flag_vec.begin(), e_index); versus an example using vertex_index that is automatically created when using vecS for the vertices: typedef property_map<Graph, vertex_index_t>::type VertexIndexMap; VertexIndexMap v_index = get(vertex_index, g); std::vector< int > flag_vec(num_vertices(g), 0); // Create the external property map iterator_property_map< std::vector< int >::iterator, VertexIndexMap > flags(flag_vec.begin(), v_index); So far for the solution. I have also a question in this place: What does the "EdgeProperty::*" exactly do? The EdgeProperty is of course the bundle, but what about the "::*" is this some sort of RegEx for "all attributes of this bundle"? I looked at the code in properties.hpp and was able to generally understand the idea, but it did not become clear to me why the "::*" is needed. Thank you. Best, Cedric

2 1

boost asio UDP issue...
by The Novice Coder 12 Nov '10

12 Nov '10

1 0

Simulating Multi domain networks in BGL
by giridhar 12 Nov '10

12 Nov '10

Hello All, I need to implement(simulate) Multi domain networks in BGL. I am thinking that each domain will be represented by each single graph. Say if there are 3 domains, then there would be 3 different graphs. And after this, I need to connect few edges of these inter-graphs. Is this good Idea to implement different domains as different graphs or is there any other better method in BGL to do this? -- Regards, Giridhar

1 0

boost::bind memory leak
by bit bit 11 Nov '10

11 Nov '10

I am using a shared_ptr to execute code on method exit as instructed in http://www.boost.org/doc/libs/1_44_0/libs/smart_ptr/sp_techniques.html#on_b… shared_ptr<void> shutdown(static_cast<void*>(0), bind(&Thread::AnnounceShutdown, this, ref(state_lock))); The above line of code causes a memory leak when an exception is thrown inside AnnounceShutdown(). I know I am not supposed to throw inside a destructor, but in this particular case I see no reason for a memory leak. AnnounceShutDown() does not allocate memory. I suspect ref() has something to do with that. debugger report: WARNING: Visual Leak Detector detected memory leaks! ---------- Block 14928 at 0x00000000006E6FF0: 56 bytes ---------- Call Stack: d:\program files\boost\boost_1_44_0\boost\smart_ptr\detail\shared_count.hpp (124): boost::detail::shared_count::shared_count<void * __ptr64,boost::_bi::bind_t<void,boost::_mfi::mf1<void,bIt::Thread,boost::upgrade_lock<boost::shared_mutex> & __ptr64>,boost::_bi::list2<boost::_bi::value<bIt::Thread * __ptr64>,boost::reference_wrapper<boos d:\program files\boost\boost_1_44_0\boost\smart_ptr\shared_ptr.hpp (199): boost::shared_ptr<void>::shared_ptr<void><void,boost::_bi::bind_t<void,boost::_mfi::mf1<void,bIt::Thread,boost::upgrade_lock<boost::shared_mutex> & __ptr64>,boost::_bi::list2<boost::_bi::value<bIt::Thread * __ptr64>,boost::reference_wrapper<boost::upgrade d:\ptyxiaki\owner\owner\thread\thread.cpp (690): bIt::Thread::Main ... .. . I have already resolved this issue using BOOST_SCOPE_EXIT instead of shared_ptr, but I am looking forward for a better solution with shared_ptr.

1 0

Hashtable
by Ricardo Uribe Lobello 11 Nov '10

11 Nov '10

Good afternoon, I have been trying to use the boost::intrusive::hashtable class but i don't understand clearly how it works. Additionally, I would like to change the hashing function used. Where can i get some example of the hashtable usage? Thanks in advance Ricardo

2 1

[1.45.0] Beta 1 available from SourceForge
by Beman Dawes 11 Nov '10

11 Nov '10

Boost release1.45.0 beta 1 is now available from SourceForge. For those who downloaded release candidate 1, note that beta 1 was build from a slightly later release candidate. See http://sourceforge.net/projects/boost/files/ This release contains numerous enhancements and bug fixes for existing libraries. For details of what's in the release, see http://beta.boost.org/users/news/version_1_45_0. 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. There are still a few serious bugs outstanding, and we will be working on clearing those before the final release. Thanks, -- The Boost Release Team

6 6

[date_time][1.45] added missing includes (was: [1.45.0] Beta 1 available from SourceForge)
by Eric Niebler 11 Nov '10

11 Nov '10

On 11/10/2010 2:46 PM, Ruediger Berlich wrote: > In order to get it to compile I hat to make a single change: > I had to add "#include <boost/serialization/nvp.hpp>" prior to the inclusion > of the date_time libraries in a single file This seems pretty cut-n-dry. I hope nobody minds, but I went ahead and added the missing #include to gregorian/greg_serialize.hpp and posix_time/time_serialize.hpp on both trunk and release. -- Eric Niebler BoostPro Computing http://www.boostpro.com

1 0