I want to use windows\'s message queue facilities to 开发者_开发技巧send a struct to another thread.
What actu开发者_StackOverflow中文版ally is the point of declaring a boost::shared_ptr to a container like std::vector or std::list?
In the boost doc of make_shared, it says: Besides convenience and style, 开发者_高级运维such a function is also exception safe and considerably
I am using Poco C++ library and cause strange problem. Poco using own shared pointer class SharedPtr for internal pointer operations. At my case static object Poco::SSLManager has SharedPtr members of
So we have (pseudo code): class A { A(sh开发者_JS百科ared_ptr parent){} } class B { A *a; B() { a = new A(boost::shared_ptr(this));
I have a: template<class K,class V> struct Node { node_ptr parent_;//node_ptr is a shared_ptr<Node<K,V>>
I am getting compilation error with g++4.6 and boost 1.42 when using boost::make_shared<T>(...), whereas shared_ptr<T>(new T(...)) compiles just fine. I am unfortunately not able to isolat
This question already has answers here: Closed 11 years ago. Possible Duplicates: pimpl: shared_ptr or unique_ptr
When I\'m using raw pointers it is pretty easy to \'travers\' up/down the tree, but when I\'ve employed shared_ptr instead of built-in pointers it isn\'t so. I m开发者_StackOverflow社区ean I just can\
I\'m in the process of learning boost::lambda and I\'ve managed to create a situation that I can\'t resolve with what I know so far.
加载中,请稍侯......