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

shared_ptr or weak_ptr in general
by Jason Winnebeck 22 Jul '03

22 Jul '03

I just wanted to follow up on my previous thread about my issues I've been discussing on the list with a general question. By default should I try to use shared_ptr or weak_ptr? I had always thought that shared_ptr should always be used except for rare cases where weak_ptr's semantics is either very desirable or needed. Now my pointers experience so far has been limited to explicit memory management (new/delete) and in Java with its references, where any reference keeps an object alive, and weak references exist but I've never used them despite a few years of using Java on the job. Based on some of the discussion (particularly from Mr Dimov), made me think that weak_ptr may be desirable a lot more often than I previously thought. I know that shared_ptr, unlike Java, is suceptable to cycles. And I feel that shared_ptr is better and less bug prone than new/delete but I'm afraid I'll have cycle problems if I just start throwing shared_ptr all over the place. I know that in my code I have back pointers all over the place, which I thought was pretty common, but I have realized that that only occurs when I'm following the generator/listener design scheme, and I've gotten that figured out. So A to B, B to A cycles don't concern me much but I do wonder about long cycles if I use shared_ptr a lot. The rule of thumb I'm using right now is to look for cycles if I "convert" a class to use shared_ptr (static crate method) that contains shared_ptr objects, similar to the rule I use to check for deadlocks with mutexes. But with all of these rules checking for safety I begin to question somewhat the benefits of shared_ptr over normal pointers. I suppose with shared_ptr you can only leak memory whereas with normal pointers you can do lots of nasty uninitialized accesses. I can see an argument that using shared_ptr only when needed and weak_ptr otherwise can help prevent cycles. But using weak_ptr requires the code to handle both cases of the lock operation, and I'm still unsure about any performance issues with lock if there is a mutex involved -- although too slight to not choose weak_ptr, it is enough to ask why not choose shared_ptr over weak_ptr if they both work equally well. Thank you for your comments and patience with my attemps at understanding, Jason Winnebeck

1 0

staticially linked STLport and Boost
by hh10k 20 Jul '03

20 Jul '03

I've compiled STLport for vc6, and can compile Boost with this: bjam "-sTOOLS=msvc-stlport" "-sBUILD=debug <stlport-iostream>on" So far so good, but when I try to compile a simple Boost.Python example (why I got Boost) I get a heap of link errors because Boost has linked with the DLL version of STLport, and I want it statically linked. I thought it's meant to default to static, but I can only guess that STLport is detecting otherwise. So, in order to force Boost to use the static verion, I tried: bjam "-sTOOLS=msvc-stlport" "-sBUILD=debug <stlport-iostream>on <define>_STLP_USE_STATIC_LIB" But now I get errors like: vc-Link libs\python\build\bin\boost_python.dll\msvc-stlport\debug\runtime-link-dynamic\stlport-cstd-namespace-std\stlport-iostream-on\stlport-version-4.5.3\boost_python_debug.dll libs\python\build\bin\boost_python.dll\msvc-stlport\debug\runtime-link-dynamic\stlport-cstd-namespace-std\stlport-iostream-on\stlport-version-4.5.3\boost_python_debug.lib msvcprtd.lib(MSVCP60D.dll) : error LNK2005: "public: __thiscall std::bad_alloc::bad_alloc(char const *)" (??0bad_alloc@std@@QAE@PBD@Z) already defined in stlport_vc6_stldebug_static.lib(dll_main.obj) LIBCMTD.lib(osfinfo.obj) : error LNK2005: __get_osfhandle already defined in MSVCRTD.lib(MSVCRTD.dll) LIBCMTD.lib(dbgheap.obj) : error LNK2005: _malloc already defined in MSVCRTD.lib(MSVCRTD.dll) ...lots more errors... This isn't just a problem with Boost.Python. Anything else that builds a dll or exe has the same errors. The first error seems really strange, because I can't understand how std::bad_alloc should exist in stlport_vc6_stldebug_static.lib(dll_main.obj). STLport does define it's own bad_alloc, but it also #defines std to _STL so there should be no 'std'. When I use bad_alloc in my own programs I don't have any problems, so I can only assume it's Boost. I've wasted so much time trying to work this out, but I don't know much about the Boost build process. What's going wrong?

3 3

Unusal regex behavior.
by sdf sdf 20 Jul '03

20 Jul '03

Hellos everyone! Here is a good one. I am using regex and am having some weird returns. I can assign my results to a std:vector <std:string>. The vector[0] does contain the correct match, but vector[1] does not contain what is in a set of parentheses as it should. In fact I usually get a segment fault when I try to access it. I then found I can access results from the grep by using the boost::Regex.What(n). However What(0) returns the next available match in the string, and What(1) and up will correctly report the substrings defined in this second match correctly. If no second match is available then the What() member will return the original match. How do I fix the vector problem? OR? Does using What() force another search to take place? And if so can I change that behavior? Code snippet: string reg_string ="[0-9]{3}(-[0-9]{2}-)[0-9]{4}"; //yes it is a SSN string search_string = "Big Bird \n123 sesame street \n the bronx NY 11722\n545-65-2343\nmorestuff\nandevenmore\nSnuff E Lufigous \n 234 sesame street \n the bronx NY 11722\n889-99-5527\nmorestuff\nandevenmore\n"; std::vector<std::string> results; boost::regex regsearch = boost::regex(reg_string,false); int num_matchs; num_matchs=regsearch.Grep(results, search_string, boost::match_any); cout << num_matchs << " Number of Matchs\n"; // this is 2 cout << results[0] << " results return string vector[0] \n"; // this is 545-65-2343 cout << regsearch.What(0) << " results from what(0) \n"; // this is 889-99-5527 cout << regsearch.What(1) << "results from what(1) \n";// this is -99- //this line aborts // cout << results[1] << " results return string vector[1] \n"; // this should be -65- HELP. Note I never ran the code above, but I think it is correct. __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com

4 5

filesystem help
by Christian Gmeiner 20 Jul '03

20 Jul '03

Hello! This is my problem: I have an std::string contains something like C:\Test\Media\Cloud.dds. Now i want to extract the Cloud.dds. This is, what i have tried: fs::path temp(Name, fs::native); fs::directory_iterator dir_itr(temp); Name = dir_itr->leaf(); Where is my error? This code throughs an exception. Thanks, Christian Gmeiner

2 1

Multiple inheritance and enable_shared_from_this
by Jason Winnebeck 20 Jul '03

20 Jul '03

Can you multiply inherit from objects that inherit from enable_shared_from_this? It seems not. My program compiled on MSVC.NET "crashes" due to shared_from_this throwing boost::bad_weak_ptr. Originally when I started using shared_ptr I wanted to have an ability to obtain a shared_ptr to this since my objects sometimes register themselves. The way I do it now is like this: static sptr create() { sptr ret( new Object() ); ret->setThisPtr( ret ); return ret; } However it is very easy to forget which classes you inherit from that force you to call setThisPtr. A good use of the assert statement helps but I'd rather not do this. The problem is that I use multiple inheritance in one place: static sptr create() { sptr ret( new ComplexObject() ); ret->BaseA::setThisPtr( ret ); ret->BaseB::setThisPtr( ret ); return ret; } I thought I'd use enable_shared_from_this but as I said it crashes. The following program as tested on MSVC.NET throws boost::bad_weak_ptr then the line "Base2::sptr b2 = c->Base2::getThis();" is executed. #include <iostream> #include <boost/smart_ptr.hpp> #include <boost/enable_shared_from_this.hpp> using namespace std; template <class T> class SharedThis : public boost::enable_shared_from_this<T> { public: boost::shared_ptr<T> getThis() { return shared_from_this(); } }; class Base1 : public SharedThis<Base1> { public: typedef boost::shared_ptr<Base1> sptr; typedef boost::weak_ptr<Base1> wptr; protected: Base1() { cout << "Base1 ctor" << endl; } public: virtual ~Base1() { cout << "Base1 dtor" << endl; } static sptr create() { return sptr( new Base1() ); } private: Base1( const Base1& o ); Base1& operator = ( const Base1& rhs ); }; //Base2 is identical to Base1 except different name class Base2 : public SharedThis<Base2> { public: typedef boost::shared_ptr<Base2> sptr; typedef boost::weak_ptr<Base2> wptr; protected: Base2() { cout << "Base2 ctor" << endl; } public: virtual ~Base2() { cout << "Base2 dtor" << endl; } static sptr create() { return sptr( new Base2() ); } private: Base2( const Base2& o ); Base2& operator = ( const Base2& rhs ); }; class Child : public Base1, public Base2 { public: typedef boost::shared_ptr<Child> sptr; typedef boost::weak_ptr<Child> wptr; protected: Child() { cout << "Child ctor" << endl; } public: virtual ~Child() { cout << "Child dtor" << endl; } static sptr create() { return sptr( new Child() ); } }; int main( int argc, char* argv[] ) { Child::sptr c = Child::create(); Base1::sptr b1 = c->Base1::getThis(); Base2::sptr b2 = c->Base2::getThis(); /* assert( c.get() == c->Base1::getThis().get() ); assert( c.get() == c->Base2::getThis().get() ); assert( c == c->Base1::getThis() ); assert( c == c->Base2::getThis() ); */ }

3 8

signals through Python
by mat_2775 19 Jul '03

19 Jul '03

Hi, I'm very new to BOOST so please forgive my ignorance. I want to use the signals library of BOOST through Python. My question is whether that is actually possible and if so how? Kind regards Mat

2 1

Bind To Lambda
by Richard Crossley 18 Jul '03

18 Jul '03

Hi, I'm trying merge some code some of which uses a mixture of BB and BLL to just use the BLL under VC7.1. Having changed some 200 expressions without incident if find I can't see the wood for the trees here. The existing code, working with BB, is; typedef boost::function<void(ICollection*)> FECCFunc; void ForEachCollectionInChannels(IAmplifier* pIAmp,FECCFunc const & fec); typedef boost::function<void(IProperty*)> FEPFunc; void ForEachProperty(ICollection* pCollection,FEPFunc const & fep); void CalcPropCurValMaxWidth(IProperty* pProp,CColumnMap& map); ... void Problem() { CColumnMap m_ChanCols; IAmplifier* pIAmp; ForEachCollectionInChannels(pAmp,bind(ForEachProperty,_1,cref(bind(&CalcProp CurValMaxWidth,_1,ref(m_ChanCols)))); //Here } What's the equivalent with using BLL? Thanks, Richard.

1 1

StlPort-4.5.3, ublas and MSVC 6.0 problem
by Bosko Ivanisevic 18 Jul '03

18 Jul '03

Although I found on the site that UBLAS supportes MSVC 6.0 with STLPort I couldn't compile any example with this configuration. It seems that using Boost ublas library with StlPort (with native MS streams) and MSVC 6.0 have some problems and require specific settings. Does anyone have any hint how this problem can be solved? When I try to compile some of the samples from libs\numeric\ublas\doc \samples (for example vecto_binary.cpp) I got following errors: c:\programming\boost_1_30_0\boost\numeric\ublas\hermitian.hpp(1534) : error C2027: use of undefined type 'const_iterator1' c:\programming\boost_1_30_0\boost\numeric\ublas\hermitian.hpp(1529) : see declaration of 'const_iterator1' c:\projects\test\boost_matrices\main.cpp(23) : see reference to class template instantiation 'boost::numeric::ublas::hermitian_adaptor <class boost::numeric::ublas::matrix<class std::complex<double>,struct boost::numeric::ublas::row_major,cla ss boost::numeric::ublas::unbounded_array<class std::complex<double> > >,struct boost::numeric::ublas::lower>' being compiled c:\programming\boost_1_30_0\boost\numeric\ublas\hermitian.hpp(1831) : error C2027: use of undefined type 'iterator1' c:\programming\boost_1_30_0\boost\numeric\ublas\hermitian.hpp(1826) : see declaration of 'iterator1' c:\projects\test\boost_matrices\main.cpp(23) : see reference to class template instantiation 'boost::numeric::ublas::hermitian_adaptor <class boost::numeric::ublas::matrix<class std::complex<double>,struct boost::numeric::ublas::row_major,cla ss boost::numeric::ublas::unbounded_array<class std::complex<double> > >,struct boost::numeric::ublas::lower>' being compiled c:\programming\boost_1_30_0\boost\numeric\ublas\hermitian.hpp(1950) : error C2027: use of undefined type 'const_iterator2' c:\programming\boost_1_30_0\boost\numeric\ublas\hermitian.hpp(1945) : see declaration of 'const_iterator2' c:\projects\test\boost_matrices\main.cpp(23) : see reference to class template instantiation 'boost::numeric::ublas::hermitian_adaptor <class boost::numeric::ublas::matrix<class std::complex<double>,struct boost::numeric::ublas::row_major,cla ss boost::numeric::ublas::unbounded_array<class std::complex<double> > >,struct boost::numeric::ublas::lower>' being compiled c:\programming\boost_1_30_0\boost\numeric\ublas\hermitian.hpp(2247) : error C2027: use of undefined type 'iterator2' c:\programming\boost_1_30_0\boost\numeric\ublas\hermitian.hpp(2242) : see declaration of 'iterator2' c:\projects\test\boost_matrices\main.cpp(23) : see reference to class template instantiation 'boost::numeric::ublas::hermitian_adaptor <class boost::numeric::ublas::matrix<class std::complex<double>,struct boost::numeric::ublas::row_major,cla ss boost::numeric::ublas::unbounded_array<class std::complex<double> > >,struct boost::numeric::ublas::lower>' being compiled c:\programming\boost_1_30_0\boost\numeric\ublas\hermitian.hpp(1534) : error C2027: use of undefined type 'const_iterator1' c:\programming\boost_1_30_0\boost\numeric\ublas\hermitian.hpp(1529) : see declaration of 'const_iterator1' c:\projects\test\boost_matrices\main.cpp(30) : see reference to class template instantiation 'boost::numeric::ublas::hermitian_adaptor <class boost::numeric::ublas::matrix<class std::complex<double>,struct boost::numeric::ublas::row_major,cla ss boost::numeric::ublas::unbounded_array<class std::complex<double> > >,struct boost::numeric::ublas::upper>' being compiled c:\programming\boost_1_30_0\boost\numeric\ublas\hermitian.hpp(1831) : error C2027: use of undefined type 'iterator1' c:\programming\boost_1_30_0\boost\numeric\ublas\hermitian.hpp(1826) : see declaration of 'iterator1' c:\projects\test\boost_matrices\main.cpp(30) : see reference to class template instantiation 'boost::numeric::ublas::hermitian_adaptor <class boost::numeric::ublas::matrix<class std::complex<double>,struct boost::numeric::ublas::row_major,cla ss boost::numeric::ublas::unbounded_array<class std::complex<double> > >,struct boost::numeric::ublas::upper>' being compiled c:\programming\boost_1_30_0\boost\numeric\ublas\hermitian.hpp(1950) : error C2027: use of undefined type 'const_iterator2' c:\programming\boost_1_30_0\boost\numeric\ublas\hermitian.hpp(1945) : see declaration of 'const_iterator2' c:\projects\test\boost_matrices\main.cpp(30) : see reference to class template instantiation 'boost::numeric::ublas::hermitian_adaptor <class boost::numeric::ublas::matrix<class std::complex<double>,struct boost::numeric::ublas::row_major,cla ss boost::numeric::ublas::unbounded_array<class std::complex<double> > >,struct boost::numeric::ublas::upper>' being compiled c:\programming\boost_1_30_0\boost\numeric\ublas\hermitian.hpp(2247) : error C2027: use of undefined type 'iterator2' c:\programming\boost_1_30_0\boost\numeric\ublas\hermitian.hpp(2242) : see declaration of 'iterator2' c:\projects\test\boost_matrices\main.cpp(30) : see reference to class template instantiation 'boost::numeric::ublas::hermitian_adaptor <class boost::numeric::ublas::matrix<class std::complex<double>,struct boost::numeric::ublas::row_major,cla ss boost::numeric::ublas::unbounded_array<class std::complex<double> > >,struct boost::numeric::ublas::upper>' being compiled c:\projects\test\boost_matrices\main.cpp(37) : warning C4508: 'main' : function should return a value; 'void' return type assumed Error executing cl.exe. Does anyone have any hint how this problem could be solved?

1 0

boost and Watcom
by filbico 18 Jul '03

18 Jul '03

Hello, I would like to use boost 1.29 under Watcom C++ complier (11.0C, Powersoft Optima 2.1). I am looking for configuration files. Robert Nowak.

1 0

Replace/Extend default execution_monitor
by aragorn_yes 18 Jul '03

18 Jul '03

Hi all, What is the best way to replace/extend the default execution_monitor (unit_test_monitor) in the test library. Thanks in advance. Manuel.

2 1

Known limitations of Boost threads across O/S platforms???
by Louis Caston 17 Jul '03

17 Jul '03

Are there any known limitations to Boost threads across Win, Solaris, and Linux? I'm in a planning cycle, and expect to be utilizing Boost as much as possible. Thanks, - Louis

2 2

indirect_iterator_generator<list<shared_ptr<X> >::iterator> again
by Raoul Gough 17 Jul '03

17 Jul '03

Using gcc 3.2 (on MinGW) the template parameter defaults for indirect_iterator_generator don't work with shared_ptr. This has been discussed* on the list before, but there doesn't seem to have been a user-friendly resolution to the issues involved (at least not in release 1_30_0). Using my compiler, the current situation requires the client code to supply all five of the template parameters. *some previous threads on the subject: http://groups.yahoo.com/group/Boost-Users/message/1618 http://lists.boost.org/MailArchives/boost/msg33273.php http://lists.boost.org/MailArchives/boost/msg33316.php My sample code: #include <boost/iterator_adaptors.hpp> #include <boost/shared_ptr.hpp> #include <list> int main () { typedef std::list<boost::shared_ptr<int> > ListType; typedef ListType::iterator BaseIterator; typedef boost::indirect_iterator_generator<BaseIterator>::type Adapter; } Error output: f:/mingw/include/c++/3.2/bits/stl_iterator_base_types.h: In instantiation of `std::iterator_traits<boost::shared_ptr<int> >': d:/CVS/boost/boost/boost/iterator_adaptors.hpp:1111: instantiated from `boost::detail::iterator_traits<boost::shared_ptr<int> >' d:/CVS/boost/boost/boost/iterator_adaptors.hpp:1111: instantiated from `boost::detail::traits_of_value_type<main()::BaseIterator>' iterator_adapter.cc:9: instantiated from here f:/mingw/include/c++/3.2/bits/stl_iterator_base_types.h:123: no type named ` iterator_category' in `class boost::shared_ptr<int>' f:/mingw/include/c++/3.2/bits/stl_iterator_base_types.h:125: no type named ` difference_type' in `class boost::shared_ptr<int>' Looking at iterator_adaptors.hpp:1111 we have (reformatted): struct traits_of_value_type { typedef typename boost::detail::iterator_traits<T>::value_type outer_value; typedef typename boost::detail::iterator_traits<outer_value>::value_type value_type; typedef typename boost::detail::iterator_traits<outer_value>::reference reference; typedef typename boost::detail::iterator_traits<outer_value>::pointer pointer; }; So traits_of_value_type tries to look up the *iterator_traits* of the *value type* for the supplied iterator. Does the value type really need to have complete iterator traits for the compiler to figure out the defaults here? Is anybody working on improving the ease-of-use for indirect_iterator_generator? -- Raoul Gough "Let there be one measure for wine throughout our kingdom, and one measure for ale, and one measure for corn" - Magna Carta

3 10

Preventing Cycles with shared_ptr
by Jason Winnebeck 17 Jul '03

17 Jul '03

Hello everyone, I am new to this list and a little new to Boost. I have a question on program design when using the excellent boost shared pointer's library. I am converting my old network library that uses explicit memory management to use shared_ptr where appropriate. So far this has gone well but I am having problem with cycles. This post is more of request for comments on my thought process, and if there is a "traditional" or better way of handling these issues. The question in general is "How to deal with the cycles that come about from event generator/listener designs?" The problem in more specific terms with my thinking follows. I'm having a problem with trying to mitigate reference cycles in a event generator/event listener paradigm. One creates a listener object, and registers itself as a listener of that object. As a result of the event, it may want to invoke methods of that object, so it contains a reference to that object. So Generator contains a reference to Listener, and Listener contains a reference to Generator. This is a problem with reference counted pointers. People tell me that cycles in general signify a flaw, so perhaps my fundamental design is indeed flawed. A real example from my library is a Connection object representing a network connection. Library user derives a new class implementing the ConnectionListener interface and registers it with Connection. When a packet arrives an event in the listener is invoked, and let's say the listener wants to process the packet and send a packet in response. It does this by passing a packet to the Connection. Thus the Connection refers to the listener, and the listener refers to the Connection (to send a packet). There are some possible solutions. One way to break cycles is to use weak references. In this way you can observe an object without preventing it from being collected. In the general case, cycles are very bad because you aren't sure which object can be deleted when. However in this case the relationship is simple. Generator can only generate events when it is alive, and Listener will only try to interact with Generator as a response to its event (so we know Generator is alive if we got its event). One could use a weak pointer in the Generator to the Listener, but then the Listener may die as soon as it is registered. The Listener can use a weak pointer to the Generator, and this seems intuitive since the Listener is merely an observer, but accessing a weak pointer safely in a multithreaded environment is expensive (I think so?) when we are positive it exists. The issue is compounded in my library since Generator is an object that I have written (therefore I can trust it to understand all of my "choices"), while the Listener is defined by the user. So I prefer to make the task as easy as possible on the user -- so I want to allow the user to use weak or strong references if possible so he doesn't have to worry about cycles. If I must impose a restriction along the lines of "you can have a pointer to object type x", I will, but I much prefer to not have restrictions like that. One way I've been considering (and have implemented some already) is to have the Generator release all its Listeners when it is done generating events. This works, but in my old API I have ways to retrieve the set listener, and this cannot work since the set listener may go to NULL at any time (as a weak pointer). So my best option for now seems to be to break my old API by allowing the user to set listeners and objects but not be able to retrieve them back (or allow retrieve function knowing that an empty shared_ptr may be returned). Another possible way is for the Generator always to pass a reference to itself in the event. This is possible and clean and very fast, but requires major changes to my API, but the prior way of disallowing gets is safe in that it allows the user to not have to think twice about keeping a reference to my object. I have more ideas but this post is getting long. If you have comments about how something like this using shared_ptr is typically designed, or comments related to my more specific problem, I would be grateful. Thanks in advance, Jason Winnebeck

2 2

RE: [Boost-Users] Preventing Cycles with shared_ptr
by Jim.Hyslop 17 Jul '03

17 Jul '03

Jason Winnebeck wrote: > I am converting my old network library that uses explicit memory > management to use shared_ptr where appropriate. So far this has gone > well but I am having problem with cycles. [...] > One could use a weak pointer in the Generator to the > Listener, but then > the Listener may die as soon as it is registered. That's OK, though - each time the Generator wants to use the Listener, it constructs a shared_ptr out of the weak_ptr it has. If the shared_ptr is NULL, the Generator knows the Listener has gone away, and can take the appropriate steps to unregister the Listener. > ... the Listener is defined by the user. So I prefer to > make the task as easy as possible on the user -- so I want to > allow the > user to use weak or strong references if possible so he > doesn't have to > worry about cycles. If you want to make things easy for the user, don't offer them a choice. Choice means complexity. Complexity is bad. Require the user to use a shared_ptr to the Generator. -- Jim

2 1

RE: [Boost-Users] vc6 stl's problem
by Jim.Hyslop 17 Jul '03

17 Jul '03

hlh771 wrot: > the stl's implementation of vc6 is buggy such as auto_ptr,xtree etc, > even if it is patched with sp5 The Service Packs do not include changes to the STL headers. The STL was provided by a third party, Dinkumware, which for a few years was unable to provide updates to Microsoft due to legal difficulties between Dinkumware and another party. You can find patches and fixes at Dinkumware's web site: http://www.dinkumware.com/vc_fixes.html -- Jim

2 1

how to empty a graph?
by Jeremie 17 Jul '03

17 Jul '03

Hello guys, I'm a newbie with boost and I need to empty a Mutable graph in the program I'm doing. is ther another method as remove_edge? /Jérémie

2 1

regex RegEx::Grep on Windows [callback problems with bind1st(mem_fun(callback))]
by Eric Brown (Propel) 16 Jul '03

16 Jul '03

I'm trying to use RegEx::Grep(GrepCallback cb, ...) on Windows with VC6. It works great with one exception. I really need the callback to be a method so that I can update attributes in my instance. I've tried about 10 ways and can't get anywhere - VC6 keeps sending back errors. Some of the errors are obvious and some - well, aren't templates wonderful whe it comes to error msgs?!@#$% I'm using MS stl and the example in the docs to get a generic function pointer doesn't work. This is the example in the regex docs: std::bind1st(std::mem_fun(&MyClass::callback), this) Then I tried: boost::bind(&MyClass::callback, this, _1) This simply produces a type that refuses to match GrepCallback. I wish the RegEx code just overloaded RegEx::Grep() to support this. (Is it more crossplatform and the STL way to do things?) I tried several other things including direct casts to GerpCallback, but I'm stuck. Any help in this area would be great. Thanks, Eric

3 2

Standardization of build
by Johannes Strömberg 16 Jul '03

16 Jul '03

Hi, I noticed that the build of some projects (filesystem, date_time, signals) differs from the build of the thread, regex and python libraries in that they they do not include a bin-stage and that debug and release versions have the same name. It would be nice if this could be standardized somehow (especially that debug and release versions should have different names). /Johannes

5 7

Re: [Boost-Users] Re: Is vc7 test unresolved external cpp_main still a problem?
by dick.bridges＠tais.com 16 Jul '03

16 Jul '03

I guess I must have missed those missives. I used <query>boost vc7 test "unresolved external" "cpp_main"</query> to query Google and, as I indicated, only found entrys from last February and none of them contained your nai as the sender. My query was apparently deficient in some manner. Which "FAQ section" mentions it? I tried (and just now reviewed) http://www.boost.org/more/faq.htm but didn't see anything that seemed to cover relevant changes since last February. In any case, my apologies for having not been more diligent. I guess I can assume from the referenced repetitions that the answers to my questions are: 1) no, you didn't miss an update; and 2) yes, it's still expected behavior when using the Jamfile included in the boost_1_30_0.zip currently on SourceForge. Thanks for your time and the clarification. "Gennadiy E. Rozental" To: Boost-Users(a)yahoogroups.com <rogeeff(a)mail.co cc: m> Subject: [Boost-Users] Re: Is vc7 test unresolved external cpp_main still a problem? 07/15/2003 07:33 PM Please respond to Boost-Users > libs\date_time\build\bin\boost_date_time.dll\vc7\debug\runtime- link-dynamic\boost_date_time.dll As I keep repeating DLL version of Boost.Test components is not available for NT platform at the moment. It's already fixed in Jamfile and mentioned in FAQ section. Use static linking instead. Gennadiy. Info: <http://www.boost.org> Wiki: <http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl> Unsubscribe: <mailto:boost-users-unsubscribe@yahoogroups.com> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

1 0

vc6 stl's problem
by hlh771 16 Jul '03

16 Jul '03

the stl's implementation of vc6 is buggy such as auto_ptr,xtree etc, even if it is patched with sp5, my question is: If I use the vc6's stl to build the boost library,is the boost library also buggy?If no, how boost library handle it? If I fix some stl's source files of vc6, will it affect boost?

1 0

RE: [Boost-Users] Re: Using date_time::microsec_clock in windows ?
by Jim.Hyslop 16 Jul '03

16 Jul '03

Russell Hind wrote: > We discussed this a few months back. I _thought_ the discussion sounded familiar ;=) -- Jim

1 0

bad/missing pictures in graph docs
by Ded Panas 16 Jul '03

16 Jul '03

Hello, group I'm studying the graph library now and found that some pictures in the documentation are bad, and some are missing: referenced from boost\libs\graph\doc\adjacency_list.html: adj-matrix-graph2.gif (bad) undir-adj-matrix-graph2.gif (missing) undir-adj-list2.gif (missing) referenced from boost\libs\graph\doc\adjacency_matrix.html: adj-matrix2.gif (missing) referenced from boost\libs\graph\doc\subgraph.html: subgraph.gif (bad) May be it is possible to fix it? DedPanas

1 0

smart pointer test failed
by hlh771 16 Jul '03

16 Jul '03

hello,everybody I want to test smart pointer library,but got some compile failure: vc- C++ ..\..\..\libs\smart_ptr\test\bin\shared_ptr_alloc_test.test\msvc\d ebug\runtime-link-dynamic\shared_ptr_alloc_test.obj shared_ptr_alloc_test.cpp M:\develop\boost_1_30_0\boost/detail/quick_allocator.hpp(165) : fatal error C1001: INTERNAL COMPILER ERROR (compiler file 'msc1.cpp', line 1794) Please choose the Technical Support command on the Visual C++ Help menu, or open the Technical Support help file for more information "cl" /Zm800 -nologo -GX -c /Z7 /Od /Ob0 /GX /GR /MDd - I"..\..\..\libs\smart_ptr\test" -I"M:\develop\boost_1_30_0" - I"D:\PROGRA~1\MICROS~1\VC98\include" - Fo"..\..\..\libs\smart_ptr\test\bin\shared_ptr_alloc_test.test\msvc\de bug\runtime-link-dynamic\shared_ptr_alloc_test.obj" - Tp"shared_ptr_alloc_test.cpp" ...failed vc- C++ ..\..\..\libs\smart_ptr\test\bin\shared_ptr_alloc_test.test\msvc\d ebug\runtime-link-dynamic\shared_ptr_alloc_test.obj... ...skipped <libs!smart_ptr! test\shared_ptr_alloc_test.test\msvc\debug\runtime-link- dynamic>shared_ptr_alloc_test.CMD for lack of <libs!smart_ptr! test\shared_ptr_alloc_test.test\msvc\debug\runtime-link- dynamic>shared_ptr_alloc_test.obj... ...skipped <libs!smart_ptr! test\shared_ptr_alloc_test.test\msvc\debug\runtime-link- dynamic>shared_ptr_alloc_test.exe for lack of <libs!smart_ptr! test\shared_ptr_alloc_test.test\msvc\debug\runtime-link- dynamic>shared_ptr_alloc_test.CMD... ...skipped <libs!smart_ptr! test\shared_ptr_alloc_test.test\msvc\debug\runtime-link- dynamic>shared_ptr_alloc_test.run for lack of <libs!smart_ptr! test\shared_ptr_alloc_test.test\msvc\debug\runtime-link- dynamic>shared_ptr_alloc_test.exe... ...failed updating 1 target... ...skipped 4 targets... ...updated 1 target... my test command is:bjam -sTOOLS=msvc test my compiler is vc6+sp5 It's seems like the compiler's error,but because the test's failure, I'm not sure it will work correctly if use it in my app. Thanks in advance.

2 1

Need Help (Spirit)!!!
by monaabs 16 Jul '03

16 Jul '03

Greetings !!! I need to use spirit to port existing yacc graamar that i have for parsing sql and its subselects. Can anybody please let me know if there is a parser for parsing SQL using spirit . I need to parse Japanese characters . I have looked at ANTLR and Spirit seems very reliable and easy . Plus ANTLR has no support for parsing MBCS characters for C++ :( Can anybody please send me a sample file (if possible) Any input greatly appreciated . Mona

2 1

RE: [Boost-Users] Using date_time::microsec_clock in windows ?
by Jim.Hyslop 16 Jul '03

16 Jul '03

Jérôme Poulin wrote: > How do you > guys suggest to emulate the microsec_clock on a Windows compilation ? I don't know how the boost developers are planning on it, but the NTP (Network Time Protocol) uses the high performance counter functions (QueryHighPerformanceCounter and QueryHighPerformanceFrequency, IIRC) and interpolates based on that. -- Jim

2 1