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

Boost::shared_ptr and memory leaks
by INsideR 15 Dec '03

15 Dec '03

Hello, I have wrote simple programm: using namespace boost; shared_ptr<int> a(new int(10)); shared_ptr<int> b; b=a; a.reset(new int(20)); std::cout<<"a=="<<*a<<" b=="<<*b; return 0; Checking this programm with DevPartner BoundsChecker, i found memory leak: Type Quantity Total (bytes) Allocation Location Sequence Leak exiting program 1 84 setlocale - [setlocal.c, line 547 (Boostt.exe)] 9 Memory Leak Exiting Program: Address 0x00E44F88 (84) allocated by _malloc_dbg. <if ( (ptloci = _malloc_crt( sizeof(threadlocinfo) )) == NULL )> Where is the problem? May be i write incorrect code? Best Wishes, Yury mailto:insider83@inbox.lv

2 1

problem with shared_ptr
by Eyal Fink 14 Dec '03

14 Dec '03

I am using boost share_ptr and I have a very strange problem. it looks to me more like a compiler problem but since it is a boost code I decided to post it here. I haven't succeeded to creating a small example which I can post here and demonstrate the problem (I know it is hard to help that way but I am working on creating an example) so I will just describe it. The symptom is that the shared_ptr call the delete on a random pointer. Going into the shared_ptr and shared_count objects, I sow that the ptr field of sp_counted_base_impl has a wrong value. I have added prints out all over the code and saw that inside the constructor of sp_counted_base_impl the value is set correctly but on the return when I try to look at the value and it is a wrong value. adding some more prints I saw that inside the shared_count constructor: template<class P, class D> shared_count(P p, D d) when casting pi_ to (sp_counted_base_impl<P, D>*) and calling a member function, the sizeof(*this) in side the member function is not the same every time (resulting with a different address to ptr and thus different value). the problem occurs only when compiling -O I am attaching the two file I have changes (shared_count.hpp is from boost/detail/) and the prints there created. I am sorry I can't supplied a complete example, this problems can just disappear when I remove any object file from the compilation. my configuration: compiler: gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7) OS: Red Hat Linux release 8.0 (Psyche) boost: boost-1.30.2 any help will be appreciated #ifndef BOOST_SHARED_PTR_HPP_INCLUDED #define BOOST_SHARED_PTR_HPP_INCLUDED // // shared_ptr.hpp // // (C) Copyright Greg Colvin and Beman Dawes 1998, 1999. // Copyright (c) 2001, 2002, 2003 Peter Dimov // // Permission to copy, use, modify, sell and distribute this software // is granted provided this copyright notice appears in all copies. // This software is provided "as is" without express or implied // warranty, and with no claim as to its suitability for any purpose. // // See http://www.boost.org/libs/smart_ptr/shared_ptr.htm for documentation. // #include <boost/config.hpp> // for broken compiler workarounds #if defined(BOOST_NO_MEMBER_TEMPLATES) && !defined(BOOST_MSVC6_MEMBER_TEMPLATES) #include <boost/detail/shared_ptr_nmt.hpp> #else #include <boost/assert.hpp> #include <boost/checked_delete.hpp> #include <boost/throw_exception.hpp> #include <boost/detail/shared_count.hpp> #include <boost/detail/workaround.hpp> #include <memory> // for std::auto_ptr #include <algorithm> // for std::swap #include <functional> // for std::less #include <typeinfo> // for std::bad_cast #include <iosfwd> // for std::basic_ostream #ifdef BOOST_MSVC // moved here to work around VC++ compiler crash # pragma warning(push) # pragma warning(disable:4284) // odd return type for operator-> #endif namespace boost { template<class T> class weak_ptr; template<class T> class enable_shared_from_this; namespace detail { struct static_cast_tag {}; struct dynamic_cast_tag {}; struct polymorphic_cast_tag {}; template<class T> struct shared_ptr_traits { typedef T & reference; }; template<> struct shared_ptr_traits<void> { typedef void reference; }; #if !defined(BOOST_NO_CV_VOID_SPECIALIZATIONS) template<> struct shared_ptr_traits<void const> { typedef void reference; }; #endif // enable_shared_from_this support template<class T, class Y> void sp_enable_shared_from_this(boost::enable_shared_from_this<T> * pe, Y * px, shared_count const & pn) { if(pe != 0) pe->_internal_weak_this._internal_assign(px, pn); } inline void sp_enable_shared_from_this(void const *, void const *, shared_count const &) { } } // namespace detail // // shared_ptr // // An enhanced relative of scoped_ptr with reference counted copy semantics. // The object pointed to is deleted when the last shared_ptr pointing to it // is destroyed or reset. // template<class T> class shared_ptr { private: // Borland 5.5.1 specific workaround typedef shared_ptr<T> this_type; public: typedef T element_type; typedef T value_type; typedef T * pointer; typedef typename detail::shared_ptr_traits<T>::reference reference; shared_ptr(): px(0), pn() // never throws in 1.30+ { } template<class Y> explicit shared_ptr(Y * p): px(p), pn(p, checked_deleter<Y>()) // Y must be complete // Eyal Fink changed that!!! //shared_ptr(Y * p): px(p), pn(p, checked_deleter<Y>()) // Y must be complete { print_ptrs(); detail::sp_enable_shared_from_this(p, p, pn); print_ptrs(); } void print_ptrs() { //cout <<"px= "<<px<<" ptr= "<< pn.get_ptr(p, checked_deleter<Y>())<<endl; } // ~shared_ptr() // { // print_ptrs(); // } // // Requirements: D's copy constructor must not throw // // shared_ptr will release p by calling d(p) // template<class Y, class D> shared_ptr(Y * p, D d): px(p), pn(p, d) { detail::sp_enable_shared_from_this(p, p, pn); } // generated copy constructor, assignment, destructor are fine... // except that Borland C++ has a bug, and g++ with -Wsynth warns #if defined(__BORLANDC__) || defined(__GNUC__) shared_ptr & operator=(shared_ptr const & r) // never throws { px = r.px; pn = r.pn; // shared_count::op= doesn't throw return *this; } #endif template<class Y> explicit shared_ptr(weak_ptr<Y> const & r): pn(r.pn) // may throw { // it is now safe to copy r.px, as pn(r.pn) did not throw px = r.px; } template<class Y> shared_ptr(shared_ptr<Y> const & r): px(r.px), pn(r.pn) // never throws { } template<class Y> shared_ptr(shared_ptr<Y> const & r, detail::static_cast_tag): px(static_cast<element_type *>(r.px)), pn(r.pn) { } template<class Y> shared_ptr(shared_ptr<Y> const & r, detail::dynamic_cast_tag): px(dynamic_cast<element_type *>(r.px)), pn(r.pn) { if(px == 0) // need to allocate new counter -- the cast failed { pn = detail::shared_count(); } } template<class Y> shared_ptr(shared_ptr<Y> const & r, detail::polymorphic_cast_tag): px(dynamic_cast<element_type *>(r.px)), pn(r.pn) { if(px == 0) { boost::throw_exception(std::bad_cast()); } } #ifndef BOOST_NO_AUTO_PTR template<class Y> explicit shared_ptr(std::auto_ptr<Y> & r): px(r.get()), pn() { Y * tmp = r.get(); pn = detail::shared_count(r); detail::sp_enable_shared_from_this(tmp, tmp, pn); } #endif #if !defined(BOOST_MSVC) || (BOOST_MSVC > 1200) template<class Y> shared_ptr & operator=(shared_ptr<Y> const & r) // never throws { px = r.px; pn = r.pn; // shared_count::op= doesn't throw return *this; } #endif #ifndef BOOST_NO_AUTO_PTR template<class Y> shared_ptr & operator=(std::auto_ptr<Y> & r) { this_type(r).swap(*this); return *this; } #endif void reset() // never throws in 1.30+ { this_type().swap(*this); } template<class Y> void reset(Y * p) // Y must be complete { BOOST_ASSERT(p == 0 || p != px); // catch self-reset errors this_type(p).swap(*this); } template<class Y, class D> void reset(Y * p, D d) { this_type(p, d).swap(*this); } reference operator* () const // never throws { BOOST_ASSERT(px != 0); return *px; } T * operator-> () const // never throws { BOOST_ASSERT(px != 0); return px; } T * get() const // never throws { return px; } // implicit conversion to "bool" #if defined(__SUNPRO_CC) && BOOST_WORKAROUND(__SUNPRO_CC, <= 0x530) operator bool () const { return px != 0; } #else typedef T * (this_type::*unspecified_bool_type)() const; operator unspecified_bool_type() const // never throws { return px == 0? 0: &this_type::get; } #endif // operator! is redundant, but some compilers need it bool operator! () const // never throws { return px == 0; } bool unique() const // never throws { return pn.unique(); } long use_count() const // never throws { return pn.use_count(); } void swap(shared_ptr<T> & other) // never throws { std::swap(px, other.px); pn.swap(other.pn); } template<class Y> bool _internal_less(shared_ptr<Y> const & rhs) const { return pn < rhs.pn; } void * _internal_get_deleter(std::type_info const & ti) const { return pn.get_deleter(ti); } // Tasteless as this may seem, making all members public allows member templates // to work in the absence of member template friends. (Matthew Langston) #ifndef BOOST_NO_MEMBER_TEMPLATE_FRIENDS private: template<class Y> friend class shared_ptr; template<class Y> friend class weak_ptr; #endif T * px; // contained pointer detail::shared_count pn; // reference counter }; // shared_ptr template<class T, class U> inline bool operator==(shared_ptr<T> const & a, shared_ptr const & b) { return a.get() == b.get(); } template<class T, class U> inline bool operator!=(shared_ptr<T> const & a, shared_ptr const & b) { return a.get() != b.get(); } #if __GNUC__ == 2 && __GNUC_MINOR__ <= 96 // Resolve the ambiguity between our op!= and the one in rel_ops template<class T> inline bool operator!=(shared_ptr<T> const & a, shared_ptr<T> const & b) { return a.get() != b.get(); } #endif template<class T, class U> inline bool operator<(shared_ptr<T> const & a, shared_ptr const & b) { return a._internal_less(b); } template<class T> inline void swap(shared_ptr<T> & a, shared_ptr<T> & b) { a.swap(b); } template<class T, class U> shared_ptr<T> static_pointer_cast(shared_ptr const & r) { return shared_ptr<T>(r, detail::static_cast_tag()); } template<class T, class U> shared_ptr<T> dynamic_pointer_cast(shared_ptr const & r) { return shared_ptr<T>(r, detail::dynamic_cast_tag()); } // shared_*_cast names are deprecated. Use *_pointer_cast instead. template<class T, class U> shared_ptr<T> shared_static_cast(shared_ptr const & r) { return shared_ptr<T>(r, detail::static_cast_tag()); } template<class T, class U> shared_ptr<T> shared_dynamic_cast(shared_ptr const & r) { return shared_ptr<T>(r, detail::dynamic_cast_tag()); } template<class T, class U> shared_ptr<T> shared_polymorphic_cast(shared_ptr const & r) { return shared_ptr<T>(r, detail::polymorphic_cast_tag()); } template<class T, class U> shared_ptr<T> shared_polymorphic_downcast(shared_ptr const & r) { BOOST_ASSERT(dynamic_cast<T *>(r.get()) == r.get()); return shared_static_cast<T>(r); } // get_pointer() enables boost::mem_fn to recognize shared_ptr template<class T> inline T * get_pointer(shared_ptr<T> const & p) { return p.get(); } // operator<< #if defined(__GNUC__) && (__GNUC__ < 3) template<class Y> std::ostream & operator<< (std::ostream & os, shared_ptr<Y> const & p) { os << p.get(); return os; } #else # if defined(BOOST_MSVC) && BOOST_WORKAROUND(BOOST_MSVC, <= 1200 && __SGI_STL_PORT) // MSVC6 has problems finding std::basic_ostream through the using declaration in namespace _STL using std::basic_ostream; template<class E, class T, class Y> basic_ostream<E, T> & operator<< (basic_ostream<E, T> & os, shared_ptr<Y> const & p) # else template<class E, class T, class Y> std::basic_ostream<E, T> & operator<< (std::basic_ostream<E, T> & os, shared_ptr<Y> const & p) # endif { os << p.get(); return os; } #endif // get_deleter (experimental) #if defined(__GNUC__) && (__GNUC__ < 3) // g++ 2.9x doesn't allow static_cast<X const *>(void *) template<class D, class T> D * get_deleter(shared_ptr<T> const & p) { void const * q = p._internal_get_deleter(typeid(D)); return const_cast<D *>(static_cast<D const *>(q)); } #else template<class D, class T> D * get_deleter(shared_ptr<T> const & p) { return static_cast<D *>(p._internal_get_deleter(typeid(D))); } #endif } // namespace boost #ifdef BOOST_MSVC # pragma warning(pop) #endif #endif // #if defined(BOOST_NO_MEMBER_TEMPLATES) && !defined(BOOST_MSVC6_MEMBER_TEMPLATES) #endif // #ifndef BOOST_SHARED_PTR_HPP_INCLUDED #ifndef BOOST_DETAIL_SHARED_COUNT_HPP_INCLUDED #define BOOST_DETAIL_SHARED_COUNT_HPP_INCLUDED #if defined(_MSC_VER) && (_MSC_VER >= 1020) # pragma once #endif // // detail/shared_count.hpp // // Copyright (c) 2001, 2002, 2003 Peter Dimov and Multi Media Ltd. // // Permission to copy, use, modify, sell and distribute this software // is granted provided this copyright notice appears in all copies. // This software is provided "as is" without express or implied // warranty, and with no claim as to its suitability for any purpose. // #include <boost/config.hpp> #if defined(BOOST_SP_USE_STD_ALLOCATOR) && defined(BOOST_SP_USE_QUICK_ALLOCATOR) # error BOOST_SP_USE_STD_ALLOCATOR and BOOST_SP_USE_QUICK_ALLOCATOR are incompatible. #endif #include <boost/checked_delete.hpp> #include <boost/throw_exception.hpp> #include <boost/detail/lightweight_mutex.hpp> #if defined(BOOST_SP_USE_QUICK_ALLOCATOR) #include <boost/detail/quick_allocator.hpp> #endif #include <memory> // std::auto_ptr, std::allocator #include <functional> // std::less #include <exception> // std::exception #include <new> // std::bad_alloc #include <typeinfo> // std::type_info in get_deleter #include <cstddef> // std::size_t #ifdef __BORLANDC__ # pragma warn -8026 // Functions with excep. spec. are not expanded inline # pragma warn -8027 // Functions containing try are not expanded inline #endif namespace boost { // Debug hooks #if defined(BOOST_SP_ENABLE_DEBUG_HOOKS) void sp_scalar_constructor_hook(void * px, std::size_t size, void * pn); void sp_array_constructor_hook(void * px); void sp_scalar_destructor_hook(void * px, std::size_t size, void * pn); void sp_array_destructor_hook(void * px); #endif // The standard library that comes with Borland C++ 5.5.1 // defines std::exception and its members as having C calling // convention (-pc). When the definition of bad_weak_ptr // is compiled with -ps, the compiler issues an error. // Hence, the temporary #pragma option -pc below. The version // check is deliberately conservative. #if defined(__BORLANDC__) && __BORLANDC__ == 0x551 # pragma option push -pc #endif class bad_weak_ptr: public std::exception { public: virtual char const * what() const throw() { return "boost::bad_weak_ptr"; } }; #if defined(__BORLANDC__) && __BORLANDC__ == 0x551 # pragma option pop #endif namespace detail { class sp_counted_base { private: typedef detail::lightweight_mutex mutex_type; public: sp_counted_base(): use_count_(1), weak_count_(1) { } virtual ~sp_counted_base() // nothrow { } virtual void *get_ptr() { exit(-1); } virtual void set_ptr(void *ptr) { //cout <<"we are not supposed to be here!"<<endl; exit(-1); } // dispose() is called when use_count_ drops to zero, to release // the resources managed by *this. virtual void dispose() = 0; // nothrow // destruct() is called when weak_count_ drops to zero. virtual void destruct() // nothrow { delete this; } virtual void * get_deleter(std::type_info const & ti) = 0; void add_ref() { #if defined(BOOST_HAS_THREADS) mutex_type::scoped_lock lock(mtx_); #endif if(use_count_ == 0 && weak_count_ != 0) boost::throw_exception(boost::bad_weak_ptr()); ++use_count_; ++weak_count_; } void release() // nothrow { { #if defined(BOOST_HAS_THREADS) mutex_type::scoped_lock lock(mtx_); #endif long new_use_count = --use_count_; if(new_use_count != 0) { --weak_count_; return; } } dispose(); weak_release(); } void weak_add_ref() // nothrow { #if defined(BOOST_HAS_THREADS) mutex_type::scoped_lock lock(mtx_); #endif ++weak_count_; } void weak_release() // nothrow { long new_weak_count; { #if defined(BOOST_HAS_THREADS) mutex_type::scoped_lock lock(mtx_); #endif new_weak_count = --weak_count_; } if(new_weak_count == 0) { destruct(); } } long use_count() const // nothrow { #if defined(BOOST_HAS_THREADS) mutex_type::scoped_lock lock(mtx_); #endif return use_count_; } private: sp_counted_base(sp_counted_base const &); sp_counted_base & operator= (sp_counted_base const &); // inv: use_count_ <= weak_count_ long use_count_; long weak_count_; #if defined(BOOST_HAS_THREADS) mutable mutex_type mtx_; #endif }; #if defined(BOOST_SP_ENABLE_DEBUG_HOOKS) template<class T> void cbi_call_constructor_hook(sp_counted_base * pn, T * px, checked_deleter<T> const &, int) { boost::sp_scalar_constructor_hook(px, sizeof(T), pn); } template<class T> void cbi_call_constructor_hook(sp_counted_base *, T * px, checked_array_deleter<T> const &, int) { boost::sp_array_constructor_hook(px); } template<class P, class D> void cbi_call_constructor_hook(sp_counted_base *, P const &, D const &, long) { } template<class T> void cbi_call_destructor_hook(sp_counted_base * pn, T * px, checked_deleter<T> const &, int) { boost::sp_scalar_destructor_hook(px, sizeof(T), pn); } template<class T> void cbi_call_destructor_hook(sp_counted_base *, T * px, checked_array_deleter<T> const &, int) { boost::sp_array_destructor_hook(px); } template<class P, class D> void cbi_call_destructor_hook(sp_counted_base *, P const &, D const &, long) { } #endif // // Borland's Codeguard trips up over the -Vx- option here: // #ifdef __CODEGUARD__ # pragma option push -Vx- #endif template<class P, class D> class sp_counted_base_impl: public sp_counted_base { private: D del; // copy constructor must not throw P ptr; // copy constructor must not throw sp_counted_base_impl(sp_counted_base_impl const &); sp_counted_base_impl & operator= (sp_counted_base_impl const &); typedef sp_counted_base_impl<P, D> this_type; public: // pre: initial_use_count <= initial_weak_count, d(p) must not throw sp_counted_base_impl(P p, D d): ptr(p), del(d) { cout <<"IN sp_counted_base_impl ocnstructro ptr="<<ptr<<" p="<<p<<endl; #if defined(BOOST_SP_ENABLE_DEBUG_HOOKS) detail::cbi_call_constructor_hook(this, p, d, 0); #endif cout <<"sizeof(*this)= "<<sizeof(*this)<<endl; cout <<"IN sp_counted_base_impl end ocnstructro ptr=" <<ptr<<" ptr addr: "<<&ptr<<" p="<<p<<endl; } virtual void dispose() // nothrow { #if defined(BOOST_SP_ENABLE_DEBUG_HOOKS) detail::cbi_call_destructor_hook(this, ptr, del, 0); #endif //cout <<"IN boost::dispose ptr="<<ptr<<endl; del(ptr); } P get_ptr() { cout <<"this= "<<this<<" ptr in get_ptr= "<<ptr<<endl; cout <<"sizeof(*this)= "<<sizeof(*this)<<endl; cout <<"ptr addr: "<<&ptr<<endl; return ptr; } void set_ptr(P _ptr) { cout <<"this= "<<this<<" setting ptr to: "<<_ptr<<endl; ptr=_ptr; cout <<"sizeof(*this)= "<<sizeof(*this)<<endl; cout <<"ptr= "<<ptr<<endl; cout <<"ptr addr: "<<&ptr<<endl; } virtual void * get_deleter(std::type_info const & ti) { return ti == typeid(D)? &del: 0; } #if defined(BOOST_SP_USE_STD_ALLOCATOR) void * operator new(std::size_t) { return std::allocator<this_type>().allocate(1, static_cast<this_type *>(0)); } void operator delete(void * p) { std::allocator<this_type>().deallocate(static_cast<this_type *>(p), 1); } #endif #if defined(BOOST_SP_USE_QUICK_ALLOCATOR) void * operator new(std::size_t) { return quick_allocator<this_type>::alloc(); } void operator delete(void * p) { quick_allocator<this_type>::dealloc(p); } #endif }; #if defined(BOOST_SP_ENABLE_DEBUG_HOOKS) int const shared_count_id = 0x2C35F101; int const weak_count_id = 0x298C38A4; #endif class weak_count; class shared_count { private: sp_counted_base * pi_; #if defined(BOOST_SP_ENABLE_DEBUG_HOOKS) int id_; #endif friend class weak_count; public: shared_count(): pi_(0) // nothrow #if defined(BOOST_SP_ENABLE_DEBUG_HOOKS) , id_(shared_count_id) #endif { } template<class P, class D> shared_count(P p, D d): pi_(0) #if defined(BOOST_SP_ENABLE_DEBUG_HOOKS) , id_(shared_count_id) #endif { cout <<"in shared_count: p= "<<p<<endl; #ifndef BOOST_NO_EXCEPTIONS try { pi_ = new sp_counted_base_impl<P, D>(p, d); cout <<"return from new sp_counted_base_impl1: p= "<ptr= "<<pi_->get_ptr()<<endl; } catch(...) { d(p); // delete p throw; } #else pi_ = new sp_counted_base_impl<P, D>(p, d); cout <<"return from new sp_counted_base_impl2: p= "<ptr= "<<pi_->get_ptr()<<endl; if(pi_ == 0) { d(p); // delete p boost::throw_exception(std::bad_alloc()); } #endif ((sp_counted_base_impl<P, D>*)pi_)->set_ptr(p); cout <<"after fix: pi_->ptr= " <<((sp_counted_base_impl<P, D>*)pi_)->get_ptr()<<endl; cout <<"end of shared_count: ptr= "<<pi_->get_ptr()<<endl; } #ifndef BOOST_NO_AUTO_PTR // auto_ptr<Y> is special cased to provide the strong guarantee template<class Y> explicit shared_count(std::auto_ptr<Y> & r): pi_(new sp_counted_base_impl< Y *, checked_deleter<Y> >(r.get(), checked_deleter<Y>())) #if defined(BOOST_SP_ENABLE_DEBUG_HOOKS) , id_(shared_count_id) #endif { r.release(); } #endif ~shared_count() // nothrow { if(pi_ != 0) pi_->release(); #if defined(BOOST_SP_ENABLE_DEBUG_HOOKS) id_ = 0; #endif } shared_count(shared_count const & r): pi_(r.pi_) // nothrow #if defined(BOOST_SP_ENABLE_DEBUG_HOOKS) , id_(shared_count_id) #endif { if(pi_ != 0) pi_->add_ref(); } explicit shared_count(weak_count const & r); // throws bad_weak_ptr when r.use_count() == 0 shared_count & operator= (shared_count const & r) // nothrow { sp_counted_base * tmp = r.pi_; if(tmp != 0) tmp->add_ref(); if(pi_ != 0) pi_->release(); pi_ = tmp; return *this; } void swap(shared_count & r) // nothrow { sp_counted_base * tmp = r.pi_; r.pi_ = pi_; pi_ = tmp; } long use_count() const // nothrow { return pi_ != 0? pi_->use_count(): 0; } bool unique() const // nothrow { return use_count() == 1; } friend inline bool operator==(shared_count const & a, shared_count const & b) { return a.pi_ == b.pi_; } friend inline bool operator<(shared_count const & a, shared_count const & b) { return std::less<sp_counted_base *>()(a.pi_, b.pi_); } void * get_deleter(std::type_info const & ti) const { return pi_? pi_->get_deleter(ti): 0; } template<class P, class D> P get_ptr() { return pi_?((sp_counted_base_impl<P, D>*)pi_)->get_ptr() : 0; } void set_ptr(void *ptr) { if(pi_) pi_->set_ptr(ptr); } }; #ifdef __CODEGUARD__ # pragma option pop #endif class weak_count { private: sp_counted_base * pi_; #if defined(BOOST_SP_ENABLE_DEBUG_HOOKS) int id_; #endif friend class shared_count; public: weak_count(): pi_(0) // nothrow #if defined(BOOST_SP_ENABLE_DEBUG_HOOKS) , id_(weak_count_id) #endif { } weak_count(shared_count const & r): pi_(r.pi_) // nothrow #if defined(BOOST_SP_ENABLE_DEBUG_HOOKS) , id_(shared_count_id) #endif { if(pi_ != 0) pi_->weak_add_ref(); } weak_count(weak_count const & r): pi_(r.pi_) // nothrow #if defined(BOOST_SP_ENABLE_DEBUG_HOOKS) , id_(shared_count_id) #endif { if(pi_ != 0) pi_->weak_add_ref(); } ~weak_count() // nothrow { if(pi_ != 0) pi_->weak_release(); #if defined(BOOST_SP_ENABLE_DEBUG_HOOKS) id_ = 0; #endif } weak_count & operator= (shared_count const & r) // nothrow { sp_counted_base * tmp = r.pi_; if(tmp != 0) tmp->weak_add_ref(); if(pi_ != 0) pi_->weak_release(); pi_ = tmp; return *this; } weak_count & operator= (weak_count const & r) // nothrow { sp_counted_base * tmp = r.pi_; if(tmp != 0) tmp->weak_add_ref(); if(pi_ != 0) pi_->weak_release(); pi_ = tmp; return *this; } void swap(weak_count & r) // nothrow { sp_counted_base * tmp = r.pi_; r.pi_ = pi_; pi_ = tmp; } long use_count() const // nothrow { return pi_ != 0? pi_->use_count(): 0; } friend inline bool operator==(weak_count const & a, weak_count const & b) { return a.pi_ == b.pi_; } friend inline bool operator<(weak_count const & a, weak_count const & b) { return std::less<sp_counted_base *>()(a.pi_, b.pi_); } }; inline shared_count::shared_count(weak_count const & r): pi_(r.pi_) #if defined(BOOST_SP_ENABLE_DEBUG_HOOKS) , id_(shared_count_id) #endif { if(pi_ != 0) { pi_->add_ref(); } else { boost::throw_exception(boost::bad_weak_ptr()); } } } // namespace detail } // namespace boost #ifdef __BORLANDC__ # pragma warn .8027 // Functions containing try are not expanded inline # pragma warn .8026 // Functions with excep. spec. are not expanded inline #endif #endif // #ifndef BOOST_DETAIL_SHARED_COUNT_HPP_INCLUDED in shared_count: p= 0x8127738 IN sp_counted_base_impl ocnstructro ptr=0x8127738 p=0x8127738 sizeof(*this)= 44 IN sp_counted_base_impl end ocnstructro ptr=0x8127738 ptr addr: 0x8127fd8 p=0x81 27738 this= 0x8127fb0 ptr in get_ptr= 0 sizeof(*this)= 20 ptr addr: 0x8127fc0 return from new sp_counted_base_impl1: p= 0x8127738 pi_->ptr= 0 this= 0x8127fb0 setting ptr to: 0x8127738 sizeof(*this)= 44 ptr= 0x8127738 ptr addr: 0x8127fd8 this= 0x8127fb0 ptr in get_ptr= 0 sizeof(*this)= 20 ptr addr: 0x8127fc0 after fix: pi_->ptr= 0 this= 0x8127fb0 ptr in get_ptr= 0 sizeof(*this)= 20 ptr addr: 0x8127fc0 end of shared_count: ptr= 0

2 2

Newbie question: block read inputs to regex
by annirak＠shaw.ca 13 Dec '03

13 Dec '03

I'm using regex_grep() to search through file contents for matches. I want to read the file in blocks to keep memory use down for large files. What I want to know is whether there is some way of adding the next block of memory to the grep where the last one left off. The best solution I can come up with is using some sort of double-buffering scheme, but that would take an awful lot of memory copies and searching some text multiple times. Both things I would prefer to avoid. What can I do? --Brendan

3 2

Re: Re: find japanese character with boost regex++
by moscao＠free.fr 13 Dec '03

13 Dec '03

>> Actually I have a text with a lot of strange characters and japanese >> one ( Hiragana, Katakana, Kanji everything..!) and I want to find these >>japanese sentence in order to translate them and replace in the text. >>I need hence a way in order to identify a japanese sentence . A kind >>of function const bool isJap( const wchar ) const would be fine. >Do you need to use regexes? I've not tried boost.regex yet so cannot help >there. >Is your text just ascii and Japanese? Or do you need to distinguish from >other languages as well? >If just ascii and Japanese, you could define a Japanese char as anything >that is not ascii (beware shift-jis encoding though, as 2nd byte of a double >byte character is in the ascii range). If your data is unicode it should >also be easy to treat European characters as non-Japanese as well. >Darren Thanks Darren for your reply, Well actually I can avoid using regex but my text is more than ascii and japanese. Actually it is a byte file where some pieces are japanese sentences and others are byte controls like 0x00 ( which introduces more difficulties because you cannot parse the text as a string because 0x00 is an end character... ). So I thinks I have to parse bytes by pair and try to identify them as Shift-JIS when it is the case. Any idea of a function or program that does it? Thanks, jschmid

3 2

R: [Boost-users] filesystem::copy_file throws -- but why?
by Galante Michele 12 Dec '03

12 Dec '03

I think you should rewrite your code either as: int processFile(const fs::path& fileName) { fs::path copyFileName(fileName.string() + ".bak"); fs::copy_file(fileName, copyFileName); } or as: int processFile(const fs::path& fileName) { fs::path copyFileName(fileName.native_file_string() + ".bak", fs::native); fs::copy_file(fileName, copyFileName); } In your example you are creating a fs::path from a string in "native" form by using the default constructor, which expects the string to be in "generic" form. Hope this helps. Regards, Michele Galante Zucchetti Centro Sistemi s.p.a. m.galante(a)centrosistemi.it -----Messaggio originale----- Da: Scott Meyers [mailto:Usenet@aristeia.com] Inviato: giovedì 11 dicembre 2003 7.11 A: boost-users(a)lists.boost.org Oggetto: [Boost-users] filesystem::copy_file throws -- but why? [...] int processFile(const fs::path& fileName) { fs::path copyFileName(fileName.native_file_string() + ".bak"); fs::copy_file(fileName, copyFileName); } This throws an exception: boost::filesystem::path: invalid name "D:\Temp\CDFix\INDEX.HTM.bak" in path: "D:\Temp\CDFix \INDEX.HTM.bak" [...]

4 4

Boost::Variant
by Akim Demaille 12 Dec '03

12 Dec '03

What is the status of Boost::Variant? It used to be documented in replicas of the real Boost documentation, but now these sites seem to be closed, and I can't find any information on boost.org. Thanks!

2 2

Need linking help for boost::filesystem
by Scott Meyers 12 Dec '03

12 Dec '03

I'd like to play with boost::filesystem, and this turns out to be the first boost library I've tried to use that requires that I build something first. I downloaded bjam, and it appears that I have successfully built filesystem libraries for the compilers I care about (VC6, VC7.1, gcc, and como), because there is a subdirectory for each of them under the libboost_filesystem.lib directory, and each subdirectory, if you push down far enough, has .obj files under both debug and release. But I can't get anything to link. I can get the sample filesystem app (simple_ls.cpp) to compile cleanly under all compilers, but nothing will link. It seems clear that I somehow need to tell the linker where to find the appropriate filesystem libraries, but I'm not sure where to point it. Help? I'm running Windows 2000. Thanks, Scott

10 15

newbie BGL problem: core dump due to graph size
by duccio.medini＠tin.it 12 Dec '03

12 Dec '03

Hi all. I am calculating the connected components of af graph with a c++ code written with BGL. My graph is huge (4E+05 vertexes, 10^6 ~ 10^8 edges). The code uses the connected_components algorithm (or, in a different version, directly the depth_first_visit one) and works well up to a "reasonable" number of edges in the graph. Over this threshold it core dumps. I have the same problem both on SPARC Solaris 9 g++3.2.2 and on Intel Linux 2.4 g++3.1 . I know that it should not be a problem of the RAM memory available on the system (or addressable form a single istance). I am able to use up to 6-7 GBs of RAM, and it tipically core dumps at 2.5-5 GBs. I suspect that I'm violating some intrinsic size limit in the BGL adjacency_list class or similar. Are there such limits, and can they be extended? Any clue would be really appreciated. Thanks in advance! Duccio Medini

4 4

Shared_ptr and constness
by cyril.godart＠bnpparibas.com 12 Dec '03

12 Dec '03

Hi, Just out of curiosity. I am increasingly using the smart_ptr and more specifically the shared_ptr but I came to realize that actually it rather violently breaches the constness rules. The example below is one of the many things you can do with a shared pointer that is forbidden with a naked pointer. As the shared_ptr penetrates even further in my code I come to realize that what I am gaining on the comfort side I loose on the safety. Clearly, that's my call but I was curious to know if it is a known fact that it is impossible to enforce constness rules. Cyril Godart Quantitative Analyst BNP Paribas. struct A { int bar; }; typedef boost::shared_ptr<A> A_ptr_t; void foo(const A_ptr_t& a) { a->bar++;//semantically this should not be possible. } int main(int argc, char* argv[]) { A_ptr_t a(new A); a->bar = 1; foo(a); return 0; } This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. --------------------------------------------- Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie.

2 1

ISO C++ does not support `long long'
by Joshua Moore-Oliva 11 Dec '03

11 Dec '03

When compiling programs that use boost, I get multiple warnings along these lines.. /home/josh/boost/type_traits/is_convertible.hpp:274: warning: ISO C++ does not support `long long' /home/josh/boost/type_traits/is_convertible.hpp:274: warning: ISO C++ does not support `long long' In file included from /home/josh/boost/iterator_adaptors.hpp:125, from /home/josh/boost/token_iterator.hpp:15, from /home/josh/boost/tokenizer.hpp:21, Am I doing something wrong? do I need to #define something? Using FreeBSD 4.9, gcc 3.2.3. Thanks, Joshua Moore-Oliva

3 3

filesystem::copy_file throws -- but why?
by Scott Meyers 11 Dec '03

11 Dec '03

I'm trying to use copy_file to, well, copy a file to a backup file (signified by adding ".bak" to the file's name). Here's what I'm doing, chopped way down: int processFile(const fs::path& fileName) { fs::path copyFileName(fileName.native_file_string() + ".bak"); fs::copy_file(fileName, copyFileName); } This throws an exception: boost::filesystem::path: invalid name "D:\Temp\CDFix\INDEX.HTM.bak" in path: "D:\Temp\CDFix \INDEX.HTM.bak" I don't see what's invalid about this name. From what I can tell, I'm fulfilling copy_file's preconditions and not falling into one of the cases where it's supposed to throw. What am I doing wrong? Thanks, Scott

1 0

RE: [Boost-users] Re: Re: Need linking help for boost::filesystem
by Ben Hutchings 10 Dec '03

10 Dec '03

Scott Meyers <Usenet(a)aristeia.com> wrote: > > Try a slight variation: > > > > cl /TP /W4 /WL /GX /GR -ID:\C++\Boost\Current simple_ls.cpp > > %BOOST_FILESYSTEM_LIB% > > Alas, that doesn't help. I still get multiply defined symbols. > This is with 1.30.2. It looks like your program and the filesystem library are built against different versions of the C/C++ run-time library. Under the control of #pragma directives, Visual C++ compiler can insert references into object files that tell the linker which libraries to link with. In this case the linker tries to link with both run-time libraries and finds conflicting definitions. Check that you're linking with the right build of the filesystem library. > Is there any reason to expect that the > problem will magically go away if the get the CVS version? Perhaps. The Boost headers are now using the abovementioned pragma to (hopefully) select the right library to link with. Ben.

2 1

Need linking help for boost::filesystem
by Witz 10 Dec '03

10 Dec '03

I had the same problem on VC7.1 - multiply defined symbols and thought i was just being dumb - with Scott having the same problem, maybe i wasn't :) I got round it by including the source files in the project i was working on - not the solution i'd have liked but it has the benefit of working and allowing me to get on with doing my 'proper' coding. So, are we going to be seeing 'Effective Boost' in the near future then Scott? :) Ian Whittley

2 1

RE: [Boost-users] Re: newbie question: graph library with gcc 3.2.1
by Vikram Anantha 09 Dec '03

09 Dec '03

Answered my own question. I replaced libbgl-viz with bgl-viz in lib/graph/example/Jamfile. I seem to be getting a little further. I'll get back with the other harder questions. Didn't want to waste people's time with questions I can answer myself :) Thanks Vik -----Original Message----- From: Vikram Anantha Sent: Tuesday, December 09, 2003 9:56 AM To: Boost Users mailing list Subject: RE: [Boost-users] Re: newbie question: graph library with gcc 3.2.1 I am using the released version 1.30.2. I had to make a change to the lib/graph/Jamfile.v2 as detailed in this email http://aspn.activestate.com/ASPN/Mail/Message/boost/1802962 in order to make the graph library compile. If at all possible, I would like to not use the current snaphot on CVS and make small local changes based on the released version. If possible, could somebody give me a little diff on the jamfile or something like that. Also, Volodya, Do your changes fix the problem with the graph examples failing or do they fix the warnings in the graph library? Thanks Vik -----Original Message----- From: Vladimir Prus [mailto:ghost@cs.msu.su] Sent: Monday, December 08, 2003 10:13 PM To: boost-users(a)lists.boost.org Subject: [Boost-users] Re: newbie question: graph library with gcc 3.2.1 Hi Vikram, > I tried building the graph library and the graph examples with bjam. I > am using gcc 3.2.1 on Solaris 2.8. > > The library seemed to build successfully but did have warnings. The > examples failed to build complaining that it could not find the > dependent graph library which seems to be a problem with my > LD_LIBRARY_PATH or something like that. The build outputs for both > cases are given below. I did not do any customizing for either of > these builds. My cmd line was bjam "-sTOOLS=gcc" > > Any help is appreciated. Thanks in advance What version of Boost are you using? If it's CVS version, then you might try to run "cvs up" now and try again. I've fixed some typos which were causing the above error. - Volodya _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

RE: [Boost-users] Re: newbie question: graph library with gcc 3.2.1
by Vikram Anantha 09 Dec '03

09 Dec '03

I am using the released version 1.30.2. I had to make a change to the lib/graph/Jamfile.v2 as detailed in this email http://aspn.activestate.com/ASPN/Mail/Message/boost/1802962 in order to make the graph library compile. If at all possible, I would like to not use the current snaphot on CVS and make small local changes based on the released version. If possible, could somebody give me a little diff on the jamfile or something like that. Also, Volodya, Do your changes fix the problem with the graph examples failing or do they fix the warnings in the graph library? Thanks Vik -----Original Message----- From: Vladimir Prus [mailto:ghost@cs.msu.su] Sent: Monday, December 08, 2003 10:13 PM To: boost-users(a)lists.boost.org Subject: [Boost-users] Re: newbie question: graph library with gcc 3.2.1 Hi Vikram, > I tried building the graph library and the graph examples with bjam. I > am using gcc 3.2.1 on Solaris 2.8. > > The library seemed to build successfully but did have warnings. The > examples failed to build complaining that it could not find the > dependent graph library which seems to be a problem with my > LD_LIBRARY_PATH or something like that. The build outputs for both > cases are given below. I did not do any customizing for either of > these builds. My cmd line was bjam "-sTOOLS=gcc" > > Any help is appreciated. Thanks in advance What version of Boost are you using? If it's CVS version, then you might try to run "cvs up" now and try again. I've fixed some typos which were causing the above error. - Volodya _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

newbie question: graph library with gcc 3.2.1
by Vikram Anantha 09 Dec '03

09 Dec '03

I tried building the graph library and the graph examples with bjam. I am using gcc 3.2.1 on Solaris 2.8. The library seemed to build successfully but did have warnings. The examples failed to build complaining that it could not find the dependent graph library which seems to be a problem with my LD_LIBRARY_PATH or something like that. The build outputs for both cases are given below. I did not do any customizing for either of these builds. My cmd line was bjam "-sTOOLS=gcc" Any help is appreciated. Thanks in advance Vik Anantha <GRAPH EXAMPLES BEGIN> unknown dependent target <libs!graph!build>liblibbgl-viz.a </GRAPH EXAMPLES END> <BGL BUILD BEGIN> ...patience... ...found 437 targets... ...updating 11 targets... MkDir1 ../../../libs/graph/build/bin MkDir1 ../../../libs/graph/build/bin/libbgl-viz.a MkDir1 ../../../libs/graph/build/bin/libbgl-viz.a/gcc MkDir1 ../../../libs/graph/build/bin/libbgl-viz.a/gcc/debug MkDir1 ../../../libs/graph/build/bin/libbgl-viz.a/gcc/debug/inlining-on MkDir1 ../../../libs/graph/build/bin/libbgl-viz.a/gcc/debug/inlining-on/runtime -link-dynamic gcc-C++-action ../../../libs/graph/build/bin/libbgl-viz.a/gcc/debug/inlining-on/runtime -link-dynamic/graphviz_graph_lex.o lex.yy.c:1169: warning: `void yyunput(int, char*)' defined but not used gcc-C++-action ../../../libs/graph/build/bin/libbgl-viz.a/gcc/debug/inlining-on/runtime -link-dynamic/graphviz_digraph_lex.o lex.yy.c:1169: warning: `void yyunput(int, char*)' defined but not used gcc-C++-action ../../../libs/graph/build/bin/libbgl-viz.a/gcc/debug/inlining-on/runtime -link-dynamic/graphviz_graph_parser.o graphviz_parser.y: In function `void boost::read_graphviz(const std::string&, boost::GraphvizGraph&)': graphviz_parser.y:492: warning: unused variable `void*in' graphviz_parser.y: In function `void boost::read_graphviz(FILE*, boost::GraphvizGraph&)': graphviz_parser.y:497: warning: unused variable `void*in' /home/installs/boost-1.30.2/boost/tuple/detail/tuple_basic.hpp: At top level: graphviz_parser.y:81: warning: `const std::string& graphviz::get_graph_name(const graphviz::Subgraph&)' defined but not used gcc-C++-action ../../../libs/graph/build/bin/libbgl-viz.a/gcc/debug/inlining-on/runtime -link-dynamic/graphviz_digraph_parser.o graphviz_parser.y: In function `void boost::read_graphviz(const std::string&, boost::GraphvizDigraph&)': graphviz_parser.y:492: warning: unused variable `void*in' graphviz_parser.y: In function `void boost::read_graphviz(FILE*, boost::GraphvizDigraph&)': graphviz_parser.y:497: warning: unused variable `void*in' /home/installs/boost-1.30.2/boost/tuple/detail/tuple_basic.hpp: At top level: graphviz_parser.y:81: warning: `const std::string& graphviz::get_graph_name(const graphviz::Subgraph&)' defined but not used gcc-Archive-action ../../../libs/graph/build/bin/libbgl-viz.a/gcc/debug/inlining-on/runtime -link-dynamic/libbgl-viz.a ar: creating ../../../libs/graph/build/bin/libbgl-viz.a/gcc/debug/inlining-on/runtime -link-dynamic/libbgl-viz.a ...updated 11 targets... </BGL BUILD END>

2 1

link fail against boost_filesystem on FreeBSD 5 with gcc 3.3.3
by Ying-Chieh Liao 04 Dec '03

04 Dec '03

It's my first time using boost I'm using boost 1.30.2 with FreeBSD 5, where gcc version is 3.3.3 following is my code, quite simple <code> #include <boost/filesystem/operations.hpp> #include <boost/filesystem/fstream.hpp> #include <string> #include <iostream> namespace fs = boost::filesystem; const std::string LogFileName = "ggyy"; int main(void) { fs::ifstream LogFile(LogFileName); return 0; } </code> it compiles well, but failed on linking : <error> g++ -L/usr/local/lib -lboost_filesystem -o LogParser LogParser.o LogParser.o: In function `main': LogParser.o(.text+0x27): undefined reference to `boost::filesystem::path::path(std::string const&)' LogParser.o(.text+0x51): undefined reference to `boost::filesystem::path::native_file_string() const' *** Error code 1 </error> My boost is built from the ports system, and I'm sure I have libboost_filesystem.a and other related boost libraries TEST [/usr/local/lib] -ijliao- ls -al *boost* -r--r--r-- 1 root wheel 4058 Dec 1 11:51 libboost_date_time.a -r-xr-xr-x 1 root wheel 4524 Dec 1 11:51 libboost_date_time.so -r--r--r-- 1 root wheel 66680 Dec 1 11:51 libboost_filesystem.a -r--r--r-- 1 root wheel 23888 Dec 1 11:51 libboost_prg_exec_monitor.a -r-xr-xr-x 1 root wheel 15524 Dec 1 11:51 libboost_prg_exec_monitor.so -r--r--r-- 1 root wheel 524054 Dec 1 11:51 libboost_regex.a -r-xr-xr-x 1 root wheel 352124 Dec 1 11:51 libboost_regex.so -r--r--r-- 1 root wheel 3861324 Dec 1 11:51 libboost_regex_debug.a -r-xr-xr-x 1 root wheel 496028 Dec 1 11:51 libboost_regex_debug.so -r--r--r-- 1 root wheel 167428 Dec 1 11:51 libboost_signals.a -r-xr-xr-x 1 root wheel 82980 Dec 1 11:51 libboost_signals.so -r--r--r-- 1 root wheel 192482 Dec 1 11:51 libboost_test_exec_monitor.a -r-xr-xr-x 1 root wheel 106912 Dec 1 11:51 libboost_test_exec_monitor.so -r-xr-xr-x 1 root wheel 31636 Dec 1 11:51 libboost_thread.so -r-xr-xr-x 1 root wheel 53920 Dec 1 11:51 libboost_threadd.so -r--r--r-- 1 root wheel 185892 Dec 1 11:51 libboost_unit_test_framework.a -r-xr-xr-x 1 root wheel 103008 Dec 1 11:51 libboost_unit_test_framework.so so... could someone tell me how to solve this problem ? -- KISS : Keep It Simple, Stupid.

1 1

Re: regex static lib for x86 emulator
by Reuti_Raman_Babu＠sdc.canon.co.in 03 Dec '03

03 Dec '03

Thank for the earlier responses. It seems almost impossible to build regex lib to Pocket PC platform. I am getting following errors: regexs.lib(src.obj) : error LNK2001: unresolved external symbol "public: __cdecl boost::w32_regex_traits<unsigned short>::w32_regex_traits<unsigned short>(void)" (??0?$w32_regex_traits@G@boost@@QAA@XZ) regexs.lib(src.obj) : error LNK2019: unresolved external symbol CreateFileMappingA referenced in function "public: void __cdecl boost::re_detail::mapfile::open(char const *)" (?open@mapfile@re_detail@boost@@QAAXPBD@Z) regexs.lib(src.obj) : error LNK2019: unresolved external symbol CreateFileA referenced in function "public: void __cdecl boost::re_detail::mapfile::open(char const *)" (?open@mapfile@re_detail@boost@@QAAXPBD@Z) regexs.lib(src.obj) : error LNK2019: unresolved external symbol FindFirstFileA referenced in function "public: __cdecl boost::re_detail::file_iterator::file_iterator(char const *)" (??0file_iterator@re_detail@boost@@QAA@PBD@Z) regexs.lib(src.obj) : error LNK2019: unresolved external symbol FindNextFileA referenced in function "public: void __cdecl boost::re_detail::file_iterator::next(void)" (?next@file_iterator@re_detail@boost@@QAAXXZ) regexs.lib(src.obj) : error LNK2019: unresolved external symbol "public: static class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > __fastcall boost::re_detail::w32_traits_base::error_string(unsigned int)" (?erro This error description "regexs.lib(src.obj) : error LNK2001: unresolved external symbol "public: __cdecl boost::w32_regex_traits<unsigned short>::w32_regex_traits<unsigned short>(void)" (??0?$w32_regex_traits@G@boost@@QAA@XZ)" doesn't make much sense to me. Others are not supported by Pocket PC 2003 SDK.Although unicode version of corresssponding API is supported. Please suggest any solution . Regards, Reuti "John Maddock" <john@johnmaddock To: <Reuti(a)sdc.canon.co.in> .co.uk> cc: Subject: Re: regex static lib for x86 emulator 11/20/2003 06:57 PM > I can build static library for ARM processor. > But when building for X86 emulator I am getting following error. > > LINK : fatal error LNK1104: cannot open file 'boost_regex_vc6_sss.lib' > > Please help. You shouldn't see that when building the source, only when trying to link a dll of exe that uses the lib - but in any case defining BOOST_REGEX_NO_LIB when building your code will stop the headers from looking for a lib to link to, and allow you to specify your own lib to link to. I hope that makes it clear :-) John.

2 1

bind/function/??? - accessing global function static type with runtime dll
by Jeff Flinn 01 Dec '03

01 Dec '03

I'm interfacing with several 'C' dynamic link libraries each with the same interface. The appropriate libraries get loaded/unloaded at run time. The following is an attempt create a wrapper that returns a function pointer of the proper static type as declared for the 'C' functions. //------------------------------ class DLL { HMODULE mDLLHdl; public: ~DLL(){ FreeLibrary( mDLLHdl ); } DLL( const std::string& aDLLName ) :mDLLHdl( LoadLibrary( aDLLName.c_str() ) ){} operator bool()const{ return mDLLHdl; } operator HMODULE()const{ return mDLLHdl; } template< typename TFnc > TFnc Fnc( const std::string& aName, TFnc )const { return (TFnc)GetProcAddress( mDLLHdl, aName.c_str() ); } }; //------------------------------ With: typedef int (FAR WINAPI *FARPROC)(); FARPROC GetProcAddress( HMODULE hModule, // handle to DLL module LPCSTR lpProcName // function name ); For example, it's used as follows: //------------------------------ // declared in an included header with extern "C" int DoAttach( const char* aName, int attachMode ); DLL lSomeDll( "Some.dll" ); boost::function0<int> lFnc = boost::bind( lSomeDll.Fnc( "DoAttach", DoAttach ), "Name", 123 ); //------------------------------ Which compiles fine, but results in unresolved external symbols errors during linking for 'DoAttach' in this example. I can force-link and run the resulting executable w/out problem. Is there a way to get the type of the function without the compiler needing to use the function pointer itself? Thanks, Jeff

1 0

ublas + msvc 7.1
by Witz 01 Dec '03

01 Dec '03

hi, I seem to be having problems with ublas in combination with msvc 7.1. Compiling the code below results in a whole slew of errors of the form: 'use of undefined type 'boost::numeric::SOME_MATRIX_TYPE<ARGS>::const_iterator2' Am i doing something dumb or is something broken? #include <boost/numeric/ublas/triangular.hpp> int main() { using namespace boost::numeric::ublas; triangular_matrix<int,lower> ldm(4,4); } I.M.Whittley

3 2

Vertex descriptors in adjacancy_list
by Ali Tofigh 01 Dec '03

01 Dec '03

Is there any guarantee that Vertex descriptors are some kind of integers? In the examples provided add_edge is called with integers as vertex descriptors. Does the choice of parameters for the adjacency_list graph make a difference on this issue? E.g. whether the we choose vecS or listS as VertexList? If future flexibility of the program being written is a factor (e.g. if we want it to be easy to change the definition of the graphs without necessarily changing other parts of the code) is it better to use add_vertex, followed by add_edge using the vertex descriptors returned by add_vertex? Regards, A. T.

3 4

Re: [Boost-users] Re: ublas + msvc 7.1
by cyril.godart＠bnpparibas.com 01 Dec '03

01 Dec '03

I have noticed something similar with msvc 7.1. Could you try please to locate the first occurence of the error and prefix any template deduced type with "typename". In the example you give: typename boost::numeric::SOME_MATRIX_TYPE<ARGS>::const_iterator2 and check that this precise compile error disappears ? (I have realised the code is boost::ublas'). This does not intend to solve your problem but to point to what vc7.1 is expecting. I am not sure whether that should be strict ISO C++. Regards, Cyril Godart. Internet fuxiaowei9999@hotmail.com@lists.boost.org - 25/11/2003 12:21 Please respond to boost-users(a)lists.boost.org Sent by: boost-users-bounces(a)lists.boost.org To: boost-users cc: Subject: [Boost-users] Re: ublas + msvc 7.1 Hi Whittley: I think this may be a bug in VC7.1. I try it successly under VC6.0 and find that the ublas is develop under VC6.0 with Dinkumware STL in its document. Yours f_x_w ----- Original Message ----- From: "Witz" <witz(a)nildram.co.uk> Newsgroups: gmane.comp.lib.boost.user Sent: Monday, November 24, 2003 9:09 AM Subject: ublas + msvc 7.1 > hi, > > I seem to be having problems with ublas in combination with msvc 7.1. > Compiling the code below results in a whole slew of errors of the form: > > 'use of undefined type > 'boost::numeric::SOME_MATRIX_TYPE<ARGS>::const_iterator2' > > Am i doing something dumb or is something broken? > > #include <boost/numeric/ublas/triangular.hpp> > > int main() > { > using namespace boost::numeric::ublas; > triangular_matrix<int,lower> ldm(4,4); > } > > I.M.Whittley _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. --------------------------------------------- Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie.

2 1

Help! Error in quote.hpp...
by Dan W. 01 Dec '03

01 Dec '03

Hi, first-time poster. Got an automated reply to the effect that my first post would be moderated; but later I got another automated email about the moderator being on vacation; and I'm in a hurry, so I hope it's okay for me to re-post here. I'm using latest betas for Digital Mars, STLport and BOOST, and I'm trying to compile a state-machine using boost's fsm::state_machine. My include line is as follows: G:\boost-1.30.2;G:\boost-1.30.2\boost\mpl;G:\boost-1.30.2\libs\mpl\example\fsm;G:\dm\STLport-5.0-1031\stlport;G:\dm\include Here's the top of my file: ............................................................................... #include <iostream> #include "boost/mpl/list.hpp" #include "state_machine.hpp" namespace mpl = boost::mpl; class rec_frm_sm : fsm::state_machine<rec_frm_sm> { public: ............................................................................... What I get on the output window is: sc rec_frm.cpp -Ae -Aa -r -mn -C -WA -S -3 -a8 -c -gf -IG:\boost-1.30.2 -IG:\boost-1.30.2\boost\mpl -IG:\boost-1.30.2\libs\mpl\example\fsm -IG:\dm\STLport-5.0-1031\stlport -IG:\dm\include -orec_frm.obj Error: G:\boost-1.30.2\boost/mpl/aux_/preprocessed/plain /quote.hpp(7): no type for argument 'T' Error: G:\boost-1.30.2\boost/mpl/aux_/has_type.hpp(23): no type for argument 'T' ..................................... Build failed I'm not sure how to track the include path for quote.hpp and has_type.hpp. I notice there's a link at www.boost.org for tracking header file inclusion, but the link appears to be broken. Any help would be appreciated. Yours. dan

2 1

Re: [Boost-users] Help with function and/or bind libraries
by John.Wismar＠alldata.com 30 Nov '03

30 Nov '03

On Sun, 30 Nov 2003 Douglas Paul Gregor <gregod(a)cs.rpi.edu> wrote: > You can replace the body of get_total with: > > return std::accumulate(myVec.begin(), myVec.end(), 0, > boost::bind(std::plus<int>(), //bind 1 > _1, > boost::bind(&B::stretch_it, //bind 2 > this, > boost::bind(&A::size, //bind 3 > _2)))); > > You can decide whether that's better than the hand-coded loop or not :) >From a maintainability standpoint, I don't think I'll make that switch. ; -) Thanks for the reply, though! (Now I just have to try to figure out what it's doing!) --------------------- John Wismar -- RPI '90 john.wismar(a)alldata.com

1 0

Help with function and/or bind libraries
by John.Wismar＠alldata.com 30 Nov '03

30 Nov '03

Here's the situation I'm trying to remedy, boiled down: class A { public: int size() const; }; class B { public: int stretch_it(int size) const; int get_total() const; private: std::vector<A> myVec; }; int B::get_total() const { int retVal = 0; for (std::vector<A>::const_iterator it = myVec.begin(); it != myVec.end (); ++it) { retVal += stretch_it(it->size()); } return retVal; } I'd love to use std::accumulate() or equivalent instead of a hand-coded loop, but I don't know if it's possible to specify a combination of operations like I have here.... Or if the result would be readable! Any suggestions would be much appreciated! --------------------- John Wismar john.wismar(a)alldata.com

2 1

boost::function - why does this work??
by Matt S Trentini 29 Nov '03

29 Nov '03

Heya Everyone, I am trying to create a generic way to extract a list of objects from another list of objects. Let me explain! Say I have a vector (or any container with fwd iterators and value_type) that contains objects that have a function which returns a long (could actually be any type). I want to iterate over that vector and extract each of the longs into a list (or any container that supports push_back and defines value_type). Something like the following: class HandleClass { public: long handle() const { return val_++; } private: static long val_; }; // ... std::vector<HandleClass> listOfHcs; // ... fill listOfHcs here std::list<long> needToFill; OK so far. I then wrote this extraction function (yes, there are many ways I could have done this - with a functor and using foreach is another possibility worth exploring, but not now :) ). template < class ReturnContainer, class FwdIterator > void Extract(const FwdIterator & itBegin, const FwdIterator & itEnd, ReturnContainer & container, boost::function1<ReturnContainer::value_type, FwdIterator::value_type> f) { for (FwdIterator it = itBegin ;it != itEnd; ++it) { container.push_back(f(*it)); } }; And I was able to do this: Extract(listOfHcs.begin(), listOfHcs.end(), needToFill, &HandleClass::handle); And it worked like a charm. needToFill gets filled and I was happy. :) However we also had containers of _pointers_to_ HandleClasses. So in some cases our vector looked like: std::vector<HandleClass *> listOfHcs; Yet the same code worked! I couldn't, and can't, for the life of me understand what was going on (I expected that I would have to wrap the (*it) in a boost::remove_pointer which worried me because my compiler - MSVC7.0 - doesn't support partial template specialization). Don't get me wrong, I'm happy that it work but can anyone explain what fandangelory is going on inside boost::function (or perhaps it's some C++ magic?) to allow this? Cheers, Matt

2 4

Compilation troubles on BSD..
by Joshua Moore-Oliva 28 Nov '03

28 Nov '03

I'm having trouble compiling code on BSD with boost, specifically boost_filesystem. I'm using gcc 3.2.3 On linux, there is no problem, buit on BSD.. this is what happens. Notice that there is no trouble FINDING -lboost_filesystem to link with, but that I'm getting undefined references to anything boost-related. This compiles without any errors on both BSD and linux, but the linking on BSD is the problem. Has anyone had any experiences getting boost to work on BSD before? Thanks, Josh. <snip> signalConfigReload.o \ signalShutdown.o -o Batcher -L. -lChatsUtils -lConfig -lFfm -lFfmStream -lShared -lboost_filesystem -L/usr/local/pqxx/lib -lpqxx markFinished.o: In function `Batcher::markFinished()': /home/josh/src/mastermailings/code/daemons/Batcher/Batcher/markFinished.cpp:9: undefined reference to `boost::filesystem::path::path[in-charge](std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' /home/josh/src/mastermailings/code/daemons/Batcher/Batcher/markFinished.cpp:9: undefined reference to `boost::filesystem::path::path[in-charge](std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' /home/josh/src/mastermailings/code/daemons/Batcher/Batcher/markFinished.cpp:9: undefined reference to `boost::filesystem::rename(boost::filesystem::path const&, boost::filesystem::path const&)' restore.o: In function `Batcher::restore(Ffm&, std::basic_ifstream<char, std::char_traits<char> >&)': /home/josh/src/mastermailings/code/daemons/Batcher/Batcher/restore.cpp:8: undefined reference to `boost::filesystem::path::path[in-charge](std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' /home/josh/src/mastermailings/code/daemons/Batcher/Batcher/restore.cpp:8: undefined reference to `boost::filesystem::exists(boost::filesystem::path const&)' collect2: ld returned 1 exit status

1 0

graph library: internal property problem
by Vasco Lohrenscheit 28 Nov '03

28 Nov '03

Hello, I have some problems with graph properties. For a project I created a layer above the boost graph library. So i have: template <typename N, typename E, typename GT> GraphNode : public N {} template <typename N, typename E, typename GT> GraphEdge : public E {} template <typename N, typename E> Graph {} with BGL properties like: typedef GraphNode<N,E,GraphTraits> tNode; typedef property <typename tNode::vertex_property, tNode*> NodeProperty; As internal graph properties i use pointers to GraphNode and GraphEdge with property tags defined in N and E, e.g. class LogicState { public: enum vertex_state_t {vertex_state=123;} static const vertex_state_t PropertyTag; } const LogicState::vertex_state_t LogicState::PropertyTag=vertex_state; and template specialization for property_kind: template <> struct property_kind <GraphEdge<LogicState, LogicConstraint, GraphTraits> > { typedef vertex_property_tg type; }; with using put(tNode::PropertyTag, graph, somestate); i get the following compile error: error C2679: binary '=' : no operator found which takes a right-hand operand of type 'GraphEdge<N,E,G> ' (or there is no acceptable conversion) with [ N=LogicState, E=LogicConstraint, G=Graph<LogicState,LogicConstraint>::tGraphTraits ] in line 316 in property_map.hpp: "static_cast<const PropertyMap&>(pa)[k] = v;" I'm using the current cvs version of boost and vc++7.1. Any ideas what can cause this problem ? Why there exist no "=" operator ? Where should it be defined/generated in normal cases ? Without my layer, with pure BGL and BOOST_INSTALL_PROPERTY I had it already working. Shouldn't it also be of type GraphEdge<N,E,G>* ? I've checked my code and everywhere I used pointers (in the property definition and with the put). Then another questions: The online docs for the BGL weren't very helpfull for me. Is the BGL book better, or is it only an enhanced version of the online docs ? best regards, Vasco Lohrenscheit

1 0

Re: [Boost-install] Installing BOOST1_30_2 under HP UX 11.11 - URGENT
by David Abrahams 27 Nov '03

27 Nov '03

"Lalit Seth" <laalit_seth(a)hotmail.com> writes: > hi all, > > I m trying to install BOOST1_30_2 under HPUX11.11 > i did bjam to make > I m hving gcc3.2 on HPUX11.11 > > Its giving me failed 22 targets, > skipped 15 targets > done 384 targets. > > Is this right or do i have to change / add parameters to bjam. > > ITS QUITE URGENT. > > Rgds > Lalit Seth Lalit, First please take your Boost installation problems to the Boost.Users list or Boost.Build list (http://www.boost.org/more/mailing_lists.htm#jamboost) This list is out of commission. Second of all, though I am not sure why we don't have the 1.30.2 regression logs posted so I can check, it's not entirely surprising to see 22 targets failing with GCC-3.2. IIRC It does have bugs which prevent a few libraries from compiling. -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

C++Builder and Boost Graph Library
by Guilherme Mello de Moura 26 Nov '03

26 Nov '03

Hi guys, My name is Guilherme and I'm trying to use Boost Graph Library with Borland C++Builder.. I'm getting several compilation errors.. I downloaded the latest BGL version (1.30.2) and tried to compile the first graph example I saw.. Here's what I got: Using Boost Graph Library (BGL) version 1.30.2 with C++Builder 5.0 (6.0).. [C++ Error] tuple_basic.hpp(158): E2434 Template declaration missing template parameters ('template<...>') [C++ Error] tuple_basic.hpp(158): E2238 Multiple declaration for 'element<N,T>' [C++ Error] tuple_basic.hpp(143): E2344 Earlier declaration of 'element<N,T>' I also tried to compile the example tests that come with BGL .. And I got some problems with some of them .. Has anybody had the same problem ?!?! Am I doing something wrong ?!?! Regards, Guilherme Mello de Moura

1 0

unit_test_framework - redirect output
by Steven Ketcham 25 Nov '03

25 Nov '03

Perhaps I am making this difficult or even missing the point but... Can I create tests with the unit_test_framework and redirect the output to a GUI? As it stands this is not possible because of int main(...) being defined. Using Windows 2000. Thanks! -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

2 1

[BGL] Using default_dfs_visitor on a graph with std::list as the vertex type
by sashan 25 Nov '03

25 Nov '03

I'm trying to use a vistitor class on a graph I have defined. The visitor class is very simple and inherits from default_dfs_visitor: class OpenGLVisitor : public boost::default_dfs_visitor { public: OpenGLVisitor(void); virtual ~OpenGLVisitor(void); }; My graph type is: typedef adjacency_list < vecS, listS, directedS > graph_t; The code to perform a dfs on the graph is as follows: graph_t g; depth_first_search(g, visitor(OGLVisitor)); However I get the compiler error (see attachment). If I change the typedef to typedef adjacency_list < vecS, vecS, directedS > graph_t; then there is no error. This seems odd since it should also work when the vertices of the graph use the std::list as their container class. I'm using VC++7.1.

3 2

Using boost::lamba with a vector of shared_ptr's
by Allen Bierbaum 24 Nov '03

24 Nov '03

Hello all. I am having trouble with the boost lambda library. I am convinced that my troubles come from some little thing I am overlooking, but for the life of me I can't seem to find the problem. I have been looking at it for the entire afternoon with no solution in sight. I have included some sample code below showing the basic idea of what I am trying to accomplish. Can anyone provide me with a working solution? The summary is: - I have a vector of shared_ptr's to a class A - That class has a method that returns a value I would like to test for in a find_if call ============================================================ namespace bl = boost::lambda class A { int getInt(); }; class Foo { A bar(); } std::vector<shared_ptr<Foo> > foos; shared_ptr<Foo> foo_ptr; A test_val; test_val = (bl::_1 ->* &Foo::bar )(foo_ptr); int find_int = 10; iter found = find_if(foos.begin(), foos.end(), (bl::_1->* &Foo::bar).getInt() == child_guid); ==================================================================== Can anyone tell me how I can call a method from a lamda method iterating over a sequence of shared_ptrs? And then how do I have this method also call another method? Thanks, Allen

4 7

regex question
by Paul Scruby 24 Nov '03

24 Nov '03

I have question about match_result. How can I find out what was matched from the regular expression? In the boost documentation, the example for regex_search does something similar to this... regex needle("foo|bar"); string haystack("blah bar blah"); string::const_iterator start = haystack.begin(); string::const_iterator end = haystack.end(); boost::match_results<string::const_iterator> what; *unsigned* *int* flags = boost::match_default; * while*(regex_search(start, end, what, expression, flags)) { // please output 'bar' string match(string(what[5].first, what[5].second) + std::string(what[6].first, what[6].second)); cout << "Found '" << match << "'\n"; start = what[0].second; flags |= boost::match_prev_avail; flags |= boost::match_not_bob; } However, this is outputing nothing. I also tried what.str(), but that gave me nothing too. Thanks again, Paul

2 1

problem with lexical_cast<int>(std::wstring)
by Ronnie Lazar 24 Nov '03

24 Nov '03

Hi, I'm trying to use lexical_cast<int>(std::wstring), on msvc6 with STLPort, and I get compilation errors. The reason for them is that DISABLE_WIDE_CHARS_SUPPORT is defined in the beginning of lexical_cast.hpp. If I add a line to undef this, in the file, it compiles and works fine, which leads me to belice that this define sould not really be defined. I searched a little more and found that it is defined because BOOST_NO_INTRINSIC_WCHAR_T is defined. My understanding is that this define specifies that the environment does not have wchar_t as a real type, but as a typedef. Why should this interfere with lexical_cast? Any suggestions on how to work around this (apart from changing lexical_cast.hpp source at my site? Thanks Ronnie Lazar

1 0

problem using function lib in MSVC6
by Kim 22 Nov '03

22 Nov '03

Boost version: 1.30.2 Boost Lib: Function OS: Windows XP Pro SP 1 Dev. Env.: Microsoft VS6 SP 6, .NET 2003 Platform SDK Feb 2003, DirectX9 SDK Problem: Can't get an example similar to the one found in the tutorial to work. // ************************************* #include <boost/function.hpp> #include <functional> struct X { int foo(int v) { return v;} }; int main(int argc, char* argv[]) { boost::function1<int, int> f; X x; f = std::bind1st ( std::mem_fun(&X::foo), &x ); f(5); // Call x.foo(5) return 0; } //*************************************** I get this error message: : error C2784: 'class std::mem_fun_t<_R,_Ty> __cdecl std::mem_fun(_R (__thiscall _Ty::*)(void))' : could not deduce template argument for '<Unknown>' from 'int (__thiscall X::*)(int)'

2 1

Boost.Thread problem with thread_specific_ptr<>::release ?
by Roland 21 Nov '03

21 Nov '03

Dear Boosters! As I am still trying to figure out how to use the thread local storage pointer I found another strange behaviour. Perhaps I am misunderstanding the docs, or this might be a bug. System: VC6.0 CVS Head Problem: When using release on a tss variable, the associated automatic cleanup routine seems not to be updated correctly as it tries to delete the original pointer, instead of the 0-pointer. Example (simple modification of tss.cpp example): boost::thread_specific_ptr<int> value; void increment() { int* p = value.get(); ++*p; } void thread_proc() { value.reset(new int(0)); // initialize the thread's storage for (int i=0; i<10; ++i) { increment(); int* p = value.get(); assert(*p == i+1); } //******** added the following two lines int* p = value.release(); delete p; // deleting the released pointer //******* } int main(int argc, char* argv[]) { boost::thread_group threads; for (int i=0; i<5; ++i) threads.create_thread(&thread_proc); threads.join_all(); } In the debug version the program faults at exit, as the pointers are beeing freed a second time. I suspect the problem lies in the following function, as it does not set the cleanup handler if the value is 0 bool tss::set(void* value) { if (value && m_cleanup) { cleanup_handlers* handlers = get_handlers(); assert(handlers); if (!handlers) return false; cleanup_info info(m_cleanup, value); (*handlers)[m_key] = info; } return !!TlsSetValue(m_key, value); } Regards, Roland Schwarz

2 2

When to use which functors?
by Bruce Johnston 21 Nov '03

21 Nov '03

I'm somewhat new to Boost, but pretty familiar with STL and Loki. I'm a bit puzzled by the wide array of similar-sounding libraries in Boost for dealing with function objects: Lambda, Function, Functional, and Bind/Mem_fn. Why are there so many of these libraries and under what circumstances would I want to choose one over the other? Thanks. - Bruce Johnston Simba Technologies

2 1

RE: [Boost-users] lexical_cast causes level 4 warnings w/ VC7.1
by Sam Partington 21 Nov '03

21 Nov '03

Peter Dimov <mailto:pdimov@mmltd.net> wrote: > Sam Partington wrote: >> >> 4511 and 4512 are useless warnings. They are telling you that the >> copy constructor and assignment operator are inaccessible. Even >> though you're not trying to call them. [...] > >> C4127 is also awkward. As it gives warnings for some common idioms. >> It refers to conditional expressions being constant. > > These warnings can be annoying, but they aren't useless. They do find > bugs. I agree that 4127 can help you find bugs. But I can't think of any situation where 4511 or 4512 will help you find a bug. If you actually try to call an inaccesible copy constructor or assignement operator, then the compiler (correctly) fails to compile it. Thats why I used the word "awkward" rather than "useless" for 4127. I'll happily be proved wrong though. Sam ****************** This e-mail has been sent from Imagination Technologies Limited. PowerVR, Metagence, Ensigma and PURE Digital are divisions of Imagination Technologies Limited. The information contained in this e-mail, including any attachment, is confidential and may be legally privileged. It is intended solely for the addressee(s) and access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying or distribution or use of the information contained in this e-mail, is prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender by return e-mail and then delete it from your system. Internet communications cannot be guaranteed to be secure, error or virus-free. The sender does not accept liability for any errors or omissions which arise as a result. Any views expressed in this message are those of the author, except where the author specifies and, with authority, states them to be the views of Imagination Technologies Ltd.

2 1

RE: [Boost-users] boost::shared_ptr performance
by Tom Matelich 21 Nov '03

21 Nov '03

> -----Original Message----- > From: Matthew Wilson [mailto:stlsoft@hotmail.com] > Sent: Friday, November 14, 2003 4:23 PM > To: boost-users(a)lists.boost.org > Subject: [Boost-users] boost::shared_ptr performance > > > [I posted this in boost.devel, but got no response. > Presumably that was the > wrong group. :)] > I'm going to respond, but I don't have much to say. I would think that with all the work you put into making this comparison that you could probably determine why smart_ptr is slower than yours. To me this comparison is interesting but not without comparing your code with smart_ptr. Given the lack of code, I have to assume you're waiting for someone to say something like, "WOW!!! I gotta get me some of that!" boost::smart_ptr is already a well used class, so if you're looking to contribute, either post your code so we can maybe see how it is better, or see what it is that is missing from your code to make it faster. Benchmarks are useless without more information. Please make your code available so we can improve boost. If that is not your goal, come out and say so. Tom Matelich Boost Lover ----------------------------------------------------------------------- DISCLAIMER: Information contained in this message and/or attachment(s) may contain confidential information of Zetec, Inc. If you have received this transmission in error, please notify the sender by return email. -----------------------------------------------------------------------

3 3

RE: [Boost-users] lexical_cast causes level 4 warnings w/ VC7.1
by Sam Partington 20 Nov '03

20 Nov '03

Bruce Johnston <mailto:c_kernel@hotmail.com> wrote: > I'm working on a project with strict requirements for the > build settings, > including mandatory warning level 4 and "treat warnings as errors". I > discovered that lexical_cast causes warnings C4127, C4511, > and C4512 when > compiling with warning level 4 using VC7.1. Try the following > code for a > quick repro: 4511 and 4512 are useless warnings. They are telling you that the copy constructor and assignment operator are inaccessible. Even though you're not trying to call them. Take the following code class noncopyable { private: noncopyable(const noncopyable&); noncopyable& operator=(const noncopyable&); }; class a_resource : noncopyable { // ... }; // ... { a_resource res; } Clearly a_resource is not meant to be copied, the developer has gone to lengths to make that clear. Indeed it never is copied, or assigned, yet the warnings will still be issued. C4127 is also awkward. As it gives warnings for some common idioms. It refers to conditional expressions being constant. So : do { XXX } while(0); Gives the warning, which is a common implementation of an ASSERT() macro, and likewise // in an header : const bool debug = false; // in code : if (debug) { } does also. None of these technigues indicate a possible error in code. Ideally all three of these warnings would be disabled in config.hpp. > As an aside, what warning level is typically used by > developers working on > Boost? On VC6 we build on warning level 3, 4 is just too noisy with the built in headers. On VC7.1 we use level 4, but with C4127, C4511, C4512 switched off. HTH Sam ****************** This e-mail has been sent from Imagination Technologies Limited. PowerVR, Metagence, Ensigma and PURE Digital are divisions of Imagination Technologies Limited. The information contained in this e-mail, including any attachment, is confidential and may be legally privileged. It is intended solely for the addressee(s) and access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying or distribution or use of the information contained in this e-mail, is prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender by return e-mail and then delete it from your system. Internet communications cannot be guaranteed to be secure, error or virus-free. The sender does not accept liability for any errors or omissions which arise as a result. Any views expressed in this message are those of the author, except where the author specifies and, with authority, states them to be the views of Imagination Technologies Ltd.

2 1

Re: [Boost-users] Re: filesystem::directory_iterator::operator++() never returns <--never mind
by Beman Dawes 20 Nov '03

20 Nov '03

At 07:02 PM 11/19/2003, John.Wismar(a)alldata.com wrote: > >OK, I found it. > >Upon yet another search of the archive, I found it: I was using the >single-threaded version of the library in a multi-threaded app. > >Sorry for the bandwidth! Actually, it is helpful. It gives us more incentive to work on reliability enhancements. Thanks, --Beman

1 0

RE: [Boost-users] Re: boost::shared_ptr performance
by Tom Matelich 20 Nov '03

20 Nov '03

> -----Original Message----- > From: Matthew Wilson [mailto:stlsoft@hotmail.com] > Sent: Wednesday, November 19, 2003 11:27 AM > To: boost-users(a)lists.boost.org > Subject: [Boost-users] Re: boost::shared_ptr performance > > > > > > > > [I posted this in boost.devel, but got no response. > > > Presumably that was the > > > wrong group. :)] > > > > > > > I'm going to respond, but I don't have much to say. I > would think that > with all the work you put into making this comparison that you could > probably determine why smart_ptr is slower than yours. To me this > comparison is interesting but not without comparing your code with > smart_ptr. Given the lack of code, I have to assume you're > waiting for > someone to say something like, "WOW!!! I gotta get me some of that!" > > No, I was seeking information, as I said. > > "There are environment settings for which boost::shared_ptr will > perform much better. If that's so, can someone help me out > with suggestions > of what defines to make?" > > It turns out that there are. > > If I was wanting to make a splash, I'd got for a dip down at > the beach. :) Sorry for any appearance of hostility. I'll check out the devel thread. ----------------------------------------------------------------------- DISCLAIMER: Information contained in this message and/or attachment(s) may contain confidential information of Zetec, Inc. If you have received this transmission in error, please notify the sender by return email. -----------------------------------------------------------------------

1 0

lexical_cast causes level 4 warnings w/ VC7.1
by Bruce Johnston 20 Nov '03

20 Nov '03

I'm working on a project with strict requirements for the build settings, including mandatory warning level 4 and "treat warnings as errors". I discovered that lexical_cast causes warnings C4127, C4511, and C4512 when compiling with warning level 4 using VC7.1. Try the following code for a quick repro: #include <string> #include <iostream> #include "boost/lexical_cast.hpp" int main() { std::string helloFactor = boost::lexical_cast<std::string>( 7 ) ; std::cout << "Hello # " << helloFactor << std::endl ; return 0 ; } Builds fine at warning level 3, fails with /W4 and /WX. As an aside, what warning level is typically used by developers working on Boost? -Bruce Johnston Simba Technologies

1 0

Re: filesystem::directory_iterator::operator++() never returns <--never mind
by John.Wismar＠alldata.com 20 Nov '03

20 Nov '03

OK, I found it. Upon yet another search of the archive, I found it: I was using the single-threaded version of the library in a multi-threaded app. Sorry for the bandwidth! --------------------- John Wismar john.wismar(a)alldata.com In a previous state of enlightnment, I wrote: I'm using the fielsystem library's directory_iterator class to collect information about the files in a directory. I'm using VC7.0, and Boost 1.30.2. My logic looks something like this: ---------------------------------------------------------------------- class DirInfo { public: DirInfo(fs::path aPath) : myPath(aPath){} void scan(); void addFile(fs::path); private: fs::path myPath; } void DirInfo::scan () { fs::directory_iterator itEnd; for (fs::directory_iterator it(myPath); it != itEnd; ++it) { TRACE("File: %s\n", it->string().c_str()); if (!fs::is_directory(*it)) { addFile(*it); } } } DirInfo di(fs::path("C:\\temp\\", fs::native); di.scan(); ---------------------------------------------------------- This successfully goes through all of the files (and subdirectories) in the given directory, but after the last item, the next call to fs::directory_iterator::operator ++() never returns. If anyone has any suggestions or ideas, I would love to hear them!! Thanks! The call stack at the point where execution seems to lock up looks like this: ntdll.dll!NtDelayExecution() + 0xc kernel32.dll!_Sleep@4() + 0xb MyApp.exe.exe!boost::detail::lightweight_mutex::scoped_lock::scoped_lock(boost::detail::lightweight_mutex & m={...}) Line 96 + 0xa C++ MyApp.exe.exe!boost::detail::sp_counted_base::release() Line 132 + 0xf C++ MyApp.exe.exe!boost::detail::shared_count::~shared_count() Line 380 C++ MyApp.exe.exe!boost::shared_ptr<boost::filesystem::directory_iterator::dir_itr_imp>:: ~shared_ptr<boost::filesystem::directory_iterator::dir_itr_imp>() + 0x2e C++ MyApp.exe.exe!boost::shared_ptr<boost::filesystem::directory_iterator::dir_itr_imp>::reset () Line 217 C++ MyApp.exe.exe!boost::filesystem::directory_iterator::m_inc() Line 256 C++ > MyApp.exe.exe!boost::filesystem::directory_iterator::operator++() Line 88 + 0x2b C++ MyApp.exe.exe!DirInfo::scan() Line 63 + 0x1a C++ --------------------- John Wismar john.wismar(a)alldata.com

1 0

filesystem::directory_iterator::operator++() never returns
by John.Wismar＠alldata.com 19 Nov '03

19 Nov '03

I'm using the fielsystem library's directory_iterator class to collect information about the files in a directory. I'm using VC7.0, and Boost 1.30.2. My logic looks something like this: ---------------------------------------------------------------------- class DirInfo { public: DirInfo(fs::path aPath) : myPath(aPath){} void scan(); void addFile(fs::path); private: fs::path myPath; } void DirInfo::scan () { fs::directory_iterator itEnd; for (fs::directory_iterator it(myPath); it != itEnd; ++it) { TRACE("File: %s\n", it->string().c_str()); if (!fs::is_directory(*it)) { addFile(*it); } } } DirInfo di(fs::path("C:\\temp\\", fs::native); di.scan(); ---------------------------------------------------------- This successfully goes through all of the files (and subdirectories) in the given directory, but after the last item, the next call to fs::directory_iterator::operator ++() never returns. If anyone has any suggestions or ideas, I would love to hear them!! Thanks! The call stack at the point where execution seems to lock up looks like this: ntdll.dll!NtDelayExecution() + 0xc kernel32.dll!_Sleep@4() + 0xb MyApp.exe.exe!boost::detail::lightweight_mutex::scoped_lock::scoped_lock(boost::detail::lightweight_mutex & m={...}) Line 96 + 0xa C++ MyApp.exe.exe!boost::detail::sp_counted_base::release() Line 132 + 0xf C++ MyApp.exe.exe!boost::detail::shared_count::~shared_count() Line 380 C++ MyApp.exe.exe!boost::shared_ptr<boost::filesystem::directory_iterator::dir_itr_imp>:: ~shared_ptr<boost::filesystem::directory_iterator::dir_itr_imp>() + 0x2e C++ MyApp.exe.exe!boost::shared_ptr<boost::filesystem::directory_iterator::dir_itr_imp>::reset () Line 217 C++ MyApp.exe.exe!boost::filesystem::directory_iterator::m_inc() Line 256 C++ > MyApp.exe.exe!boost::filesystem::directory_iterator::operator++() Line 88 + 0x2b C++ MyApp.exe.exe!DirInfo::scan() Line 63 + 0x1a C++ --------------------- John Wismar john.wismar(a)alldata.com

1 0

regex static lib for x86 emulator
by Reuti＠sdc.canon.co.in 19 Nov '03

19 Nov '03

I can build static library for ARM processor. But when building for X86 emulator I am getting following error. LINK : fatal error LNK1104: cannot open file 'boost_regex_vc6_sss.lib' Please help. Thanks in advance. Reuti

1 0

gregorian: explicit date::date(date_int_type) ?
by Michael Haubenwallner 19 Nov '03

19 Nov '03

Hi, I'm preparing my company's step from C to C++, and when i use boost::date_time::*, there's a great danger to make mistakes like this with boost-1.30.2: #include <time.h> #include <iostream> #include <boost/date_time/posix_time/posix_time.hpp> using namespace boost::posix_time; using namespace boost::gregorian; int main() { time_t now = time(0); try { ptime time(now); // mistake cerr << to_simple_string(time) << endl; } catch (exception const& e) { cerr << "error: " << e.what() << endl; } } The problem is that the time_t in this case is treated as a day-count from which a gregorian::date() is implicitly constructed. When digging through the gregorian::date, i see that the constructors of date_time::date() from date_int_type and date_rep_type protected. So, wouldn't it be better to make the gregorian::date() constructors from date_int_type and date_rep_type explicit, to get a compile-time error with this sample rather than the out-of-range-exception "Year is out of valid range: 1400..10000" ? And another reason to make this constructor explicit might be that date_rep_type is the internal representation of date(), so when constructing date() with a day_count, you have to know the epoch, and then constructing date() should be done explicitly... What do you think about this ? Thanks, Michael Haubenwallner -- Michael Haubenwallner SALOMON Automation GmbH Forschung & Entwicklung A-8114 Friesach bei Graz T +43 3127 200 308 F +43 3127 200 22 mailto:michael.haubenwallner@salomon.at http://www.salomon.at

2 3

Invert Matrix
by JEFFREY CULLINA 18 Nov '03

18 Nov '03

I have devoleped code to derive a simple matrix expression: [K]*[D]=[R] wher D is an unknown vector. I am looking for code to do two things: 1. Invert [K] to get the expression [D]=inv([K])*[R] 2. Solve the equation in 1 It looks like the UBLAS toolkit provides a function _t_sv to solve the equation, but I do not see anything to help me invert the matrix. Is there code available to help me invert a matrix? While I am at it, I may as well ask if _t_sv is the best function to use to solve the system. Thanks, Jeff

1 0

Smart pointers and STL allocators
by Mark A. Gibbs 18 Nov '03

18 Nov '03

I have a couple of questions about combining smart pointers and STL allocators. First of all, am I right in assuming that I can use the shared_* templates right out of the box, as long as I define a custom deleter that uses the allocator's deallocate function? But if that's so, how exactly is it done? Part of my confusion comes from the fact that the STL allocator documentation I've come across isn't exactly clear on the semantics of allocators (I don't have a copy of the standard). For instance, I'm not 100% sure whether or not I have to call construct() after allocate() and destroy() before deallocate(). This is what I have so far: class allocator_helper { public: allocator_helper(allocator_type& a) : a_(a) {} void operator()(void const* p) const { a_.deallocate(static_cast<allocator_type::pointer>(p)); } private: allocator_type& a_; }; foo* bar = static_cast<foo*>(get_allocator().allocate(1)); shared_ptr<foo> p_foo(bar, allocator_helper(get_allocator())); foo* baz = static_cast<foo*>(get_allocator().allocate(10)); shared_array<foo> p_foo(baz, allocator_helper(get_allocator())); Now, for scoped_* I would probably have to rewrite them to use the allocator, right? Or is there a way to use allocators with the existing scoped_* templates? Mark

2 3