March 2003 - Boost-users - lists.boost.org

[Signals-1.30.0] Linking problems
by Michael Kettner 01 Apr '03

01 Apr '03

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I've got problems in linking against the signals-library. I built the library defining <define>BOOST_SIGNALS_NAMESPACE=boost_signals and running bjam -sTOOLS=gcc-stlport -sBUILD=release Everythinig seemed to work fine, but when I now try to link against the shared library (see attached file), I get the following undefined references: undefined reference to `boost::boost_signals::detail::signal_base_impl::connect_slot(boost::any const&, boost::any const&, _STL::vector<boost::boost_signals::trackable const*, _STL::allocator<boost::boost_signals::trackable const*> > const&)' and undefined reference to `boost::boost_signals::detail::signal_base_impl::signal_base_impl[in-charge](boost::function2<bool, boost::any, boost::any, _STL::allocator<boost::function_base> > const&)' I'm using gcc-3.2.2 and STLport-4.5.3. May it be the case that something with the STL-namespace (std) went wrong? Thanks for any help, Michael - -- Dipl.-Ing. Michael Kettner, Wissenschaftlicher Mitarbeiter Institut für Verkehrswesen, Eisenbahnbau und -betrieb, Universitaet Hannover Appelstr. 9A # Tel: ++49/(0)511/762-4273 D-30167 Hannover # Fax: ++49/(0)511/762-3001 http://www.ive.uni-hannover.de # kettner(a)ive.uni-hannover.de -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+iIILkCdGnb0kVFMRAtewAJ9+MNdRW7hs4vHHbmnuashsi22d8gCaAm8W N8FnJqbRHiqU3S0EKDixD0U= =qEMK -----END PGP SIGNATURE----- [Non-text portions of this message have been removed]

3 5

[BGL] Problem with setS adjacency lists
by Pierre Barbier de Reuille 31 Mar '03

31 Mar '03

Hello, I want an undirected graph with non-multiple edges. So I use a graph defined as : adjacencylist<setS,vecS,undirectedS,SomeProperty> But, if I insert many times the same edge with: add_edge(2,3) add_edge(1,4) add_edge(2,3) add_edge(3,2) I obtain in fact 3 edges 2<->3 which I really don't want. Is there something else to do to avoid having multiple edges linking the same vertices ? And then, is there a way to user hash_set with g++-3.2 ? The problem being that hash_set is defined in the file ext/hash_set and in the namespace __gnu_cxx ... Thanks, -- Pierre Barbier de Reuille INRA - UMR Cirad/Inra/Cnrs/Univ.MontpellierII AMAP Botanique et Bio-informatique de l'Architecture des Plantes TA40/PSII, Boulevard de la Lironde 34398 MONTPELLIER CEDEX 5, France tel : (33) 4 67 61 65 77 fax : (33) 4 67 61 56 68

1 1

A bug in boost.lexical_cast 1.30
by Black Ice 31 Mar '03

31 Mar '03

When lexical_cast used under VC, and the option "Treat wchar_t as Build-in Type" is off The following code will cause compile error: int main(int argc, char * argv[]) { string str("10"); unsigned short n = lexical_cast<unsigned short>(str); return 0; } Because in lexical_cast::detail::widest_char, treat unsigned short as wchar_t!! -- /*******************/ ×ÔÓÉ£šliberty£©ÎÞ·ÇŸÍÊÇÕâÑùÒ»ÖÖ³ÐÅµ£ºÃ¿žöÈËœ«»áµÃµœÒ»ÖÖ±£ÕÏ£¬±£ÕÏÎÒÃÇ¿ÉÒÔÓë ÈšÍþ¡¢¶àÊý¡¢Á÷Ë×Œ°ÓßÂÛµÄÓ°ÏìÏà¿¹ºâ¡£ /*******************/

2 2

Another bug in boost.lexical_cast 1.30
by Black Ice 31 Mar '03

31 Mar '03

lexical_cast.hpp line 145: bool operator<<(const Source &input) { return stream << input; } Convert basic_stringstream & to bool? -- /*******************/ ×ÔÓÉ£šliberty£©ÎÞ·ÇŸÍÊÇÕâÑùÒ»ÖÖ³ÐÅµ£ºÃ¿žöÈËœ«»áµÃµœÒ»ÖÖ±£ÕÏ£¬±£ÕÏÎÒÃÇ¿ÉÒÔÓë ÈšÍþ¡¢¶àÊý¡¢Á÷Ë×Œ°ÓßÂÛµÄÓ°ÏìÏà¿¹ºâ¡£ /*******************/

2 2

Re: [boost] lexical_cast woes
by Terje Slettebø 30 Mar '03

30 Mar '03

>From: "Michel André" <michel.andre(a)swipnet.se> > I get the following errors when compiling with the lexical_cast version in > CVS on MSVC 7.0 do I have to enable wchar_t support on the command line or > disable it via DISABLE_WIDE_CHAR_SUPPORT or whats the solution. This problem was reported at the Boost-Users list, as well. It turns out that testing for MSVC 6, and disabling wide character support in that case, wasn't enough, as the same needs to be done if MSVC 7 is set to have wchar_t not as intrinsic type. I've therefore removed the "BOOST_MSVC <= 1200" test, again, and restored "BOOST_NO_INTRINSIC_WCHAR_T" test, which used to be, earlier. The reason the the test for MSVC was used first, was that the config for Intel C++ also defined BOOST_NO_INTRINSIC_WCHAR_T, regardless of whether it was the case or not, as the compiler didn't set a macro for it. However, it appears that the latest version of Intel C++ do get correct wide character support, when it's enabled. I've also changed bad_lexical_cast, to return the types used, in source()/target(), as given in Kevlin's suggestion (http://article.gmane.org/gmane.comp.lib.boost.devel/18240) As a small change, the warning with MSVC 7 for void * -> bool conversion is removed, using Kevlin's suggestion (http://article.gmane.org/gmane.comp.lib.boost.devel/18253) I've run the tests for Intel C++ 7.0 (strict mode), MSVC 7.0 (with and without wchar_t as intrinsic type), and MSVC 6.0, and it works. This is now fixed in the CVS. Thanks for the feedback. Regards, Terje

1 0

Bug in regex library?
by Andrey Sverdlichenko 30 Mar '03

30 Mar '03

boost::regex do not compile with STLPort-4.5.3 on FreeBSD 4.7-RELEASE-p3, gcc 2.95.4. This is a patch that fixed a problem. Is it just a typo in source? ==== //boost/libs/regex/src/cpp_regex_traits.cpp#1 - //boost/libs/regex/src/cpp_regex_traits.cpp ==== @@ -201,7 +201,7 @@ const std::messages<char>* pm = 0; #ifndef __IBMCPP__ - std::messages<char>::catalog cat = static_cast<std::messages<wchar_t>::catalog>(-1); + std::messages<char>::catalog cat = static_cast<std::messages<char>::catalog>(-1); #else std::messages<char>::catalog cat = reinterpret_cast<std::messages<wchar_t>::catalog>(-1); #endif

2 1

RE: [Boost-Users] Problem with 1.30.0 lexical_cast
by Tom Matelich 28 Mar '03

28 Mar '03

Well, actually, looks like it lies elsewhere. I rolled back to 1.29.0 and its still broken :( > -----Original Message----- > From: Terje Slettebø [mailto:tslettebo@chello.no] > Sent: Wednesday, March 26, 2003 9:15 PM > To: Boost-Users(a)yahoogroups.com > Subject: Re: [Boost-Users] Problem with 1.30.0 lexical_cast > > > >From: "Tom Matelich" <tmatelich(a)zetec.com> > > > Compiler: gcc 3.2 and 3.2.2 > > > > I believe this is actually a bug in gcc, but I'm going to > post it hopes > that > > someone can help me. We have a handy little tool for > generating enums > with > > associated string conversion and stream > insertion/extraction functions. > > When we upgraded to boost 1.30.0, lexical_cast'ing one of > these enums to > > std::string started behaving incorrectly, rather than the > name, it is > giving > > me the integral value. It seems that the lexical_stream is > being used. > > Unfortunately, my test case is working fine. The complete test case > > (including definition of ZAcquisition::PPG) is appended at > the end. The > > code I am seeing failure with looks like: > > > > void foo(ZAcquisition::PPG::Type gt) > > { > > ... > > std::string str; > > str = boost::lexical_cast<std::string>(gt); > > std::cerr << "DEBUG, storing encode for PPG: " << str << > ", aka " << gt > > << std::endl; > > ... > > } > > > > This outputs (for example): > > DEBUG, storing encode for PPG: 0, aka ONE > > > > I tried boost::lexical_cast<std::string, > ZAcquisition::PPG::Type>(gt) as > > well. > > > > Anyone have any ideas? For now I'm going to back out to 1.29.0's > > lexical_cast. > > > It happens on my Windows/Intel 7.0 box as well. > > It's a little difficult when you don't have a failing test > case. If you had > that, I could have looked into it. The above code works > correctly on Intel > C++ 7.0 (Windows), here. > > > Regards, > > Terje > > > ------------------------ Yahoo! Groups Sponsor > ---------------------~--> > Get 128 Bit SSL Encryption! > http://us.click.yahoo.com/xaxhjB/hdqFAA/xGHJAA/EbFolB/TM > -------------------------------------------------------------- > -------~-> > > 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/ > > ----------------------------------------------------------------------- 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

Why "explicit" in shared_ptr's constructor?
by Maurizio Colucci 28 Mar '03

28 Mar '03

Hello, I am a newbie user of boost. I have a question about boost::shared_ptr. Suppose you have a polimorphic list: class entity{ ...}; class simple_entity : public entity{ public: uint id; simple_entity(uint i) : id(i) {} }; int main(){ list<shared_ptr<entity> > l; ... I noticed the following code doesn't compile l.push_back(new simple_entity(1)); too bad, because it was very easy to read, and very similar to the behavior if standard pointers (not to speak about similarity to Java and C#). So I am forced to do l.push_back(shared_ptr<entity> (new simple_entity(1))); which is less readable and, IMHO, barely tolerable on the long run: too much typing. It seems that the reason is the explicit keyword in the constructor. My question is: why? what was the danger without the explicit? Thank you very much for any info, Maurizio

3 2

RE: [Boost-Users] Why "explicit" in shared_ptr's constructor?
by Tom Matelich 28 Mar '03

28 Mar '03

the danger comes from code like so: void foo(boost::shared_ptr<entity> p) { ... } void bar() { entity* e = new entity; foo(e); delete e; } Allowing a pointer to be converted to a shared_ptr implicitly could cause serious bugs. You could shorten things with this (untested) function: template <typename T> boost::shared_ptr<T> make_sp(T* p) { return boost::shared_ptr<T>(p); } > -----Original Message----- > From: Maurizio Colucci [mailto:seguso@email.it] > Sent: Friday, March 28, 2003 8:36 AM > To: Boost-Users(a)yahoogroups.com > Subject: [Boost-Users] Why "explicit" in shared_ptr's constructor? > > > Hello, > > I am a newbie user of boost. > > I have a question about boost::shared_ptr. Suppose you have a > polimorphic list: > > class entity{ ...}; > > > class simple_entity : public entity{ > public: > uint id; > simple_entity(uint i) : id(i) {} > }; > > int main(){ > list<shared_ptr<entity> > l; > ... > > > I noticed the following code doesn't compile > > l.push_back(new simple_entity(1)); > > too bad, because it was very easy to read, and very similar to the > behavior if standard pointers (not to speak about similarity to Java > and C#). So I am forced to do > > l.push_back(shared_ptr<entity> (new simple_entity(1))); > > which is less readable and, IMHO, barely tolerable on the long > run: too much typing. > > It seems that the reason is the explicit keyword in the > constructor. My question is: why? what was the danger without the > explicit? > > Thank you very much for any info, > > Maurizio > > > > > ------------------------ Yahoo! Groups Sponsor > ---------------------~--> > Get 128 Bit SSL Encryption! > http://us.click.yahoo.com/xaxhjB/hdqFAA/xGHJAA/EbFolB/TM > -------------------------------------------------------------- > -------~-> > > 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/ > > ----------------------------------------------------------------------- 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. -----------------------------------------------------------------------

2 1

Boost.Thread 1.30 cause lot's of warnings and errors under vc 7.1
by Black Ice 28 Mar '03

28 Mar '03

void foo(string & str) { str = "foo"; } int main(int argc, char * argv[]) { string str1("Hello world"); string str2(str1); thread trd1(bind(&foo, str1)); thread trd2(bind(&foo, str2)); trd1.join(); trd2.join(); return 0; } The following is the compile log: Compiling... testThread.cpp d:\Programming\boost\boost\boost\thread\exceptions.hpp(29) : warning C4275: non dll-interface class 'std::logic_error' used as base for dll-interface class 'boost::lock_error' c:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\stdexcept(14) : see declaration of 'std::logic_error' d:\Programming\boost\boost\boost\thread\exceptions.hpp(28) : see declaration of 'boost::lock_error' d:\Programming\boost\boost\boost\thread\exceptions.hpp(35) : warning C4275: non dll-interface class 'std::runtime_error' used as base for dll-interface class 'boost::thread_resource_error' c:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\stdexcept(136) : see declaration of 'std::runtime_error' d:\Programming\boost\boost\boost\thread\exceptions.hpp(34) : see declaration of 'boost::thread_resource_error' d:\Programming\boost\boost\boost\thread\mutex.hpp(37) : warning C4275: non dll-interface class 'boost::noncopyable' used as base for dll-interface class 'boost::mutex' d:\Programming\boost\boost\boost\noncopyable.hpp(22) : see declaration of 'boost::noncopyable' d:\Programming\boost\boost\boost\thread\mutex.hpp(36) : see declaration of 'boost::mutex' d:\Programming\boost\boost\boost\thread\mutex.hpp(75) : warning C4275: non dll-interface class 'boost::noncopyable' used as base for dll-interface class 'boost::try_mutex' d:\Programming\boost\boost\boost\noncopyable.hpp(22) : see declaration of 'boost::noncopyable' d:\Programming\boost\boost\boost\thread\mutex.hpp(74) : see declaration of 'boost::try_mutex' d:\Programming\boost\boost\boost\thread\mutex.hpp(115) : warning C4275: non dll-interface class 'boost::noncopyable' used as base for dll-interface class 'boost::timed_mutex' d:\Programming\boost\boost\boost\noncopyable.hpp(22) : see declaration of 'boost::noncopyable' d:\Programming\boost\boost\boost\thread\mutex.hpp(114) : see declaration of 'boost::timed_mutex' d:\Programming\boost\boost\boost\thread\thread.hpp(39) : warning C4275: non dll-interface class 'boost::noncopyable' used as base for dll-interface class 'boost::thread' d:\Programming\boost\boost\boost\noncopyable.hpp(22) : see declaration of 'boost::noncopyable' d:\Programming\boost\boost\boost\thread\thread.hpp(38) : see declaration of 'boost::thread' d:\Programming\boost\boost\boost\thread\thread.hpp(68) : warning C4275: non dll-interface class 'boost::noncopyable' used as base for dll-interface class 'boost::thread_group' d:\Programming\boost\boost\boost\noncopyable.hpp(22) : see declaration of 'boost::noncopyable' d:\Programming\boost\boost\boost\thread\thread.hpp(67) : see declaration of 'boost::thread_group' d:\Programming\boost\boost\boost\thread\thread.hpp(79) : warning C4251: 'boost::thread_group::m_threads' : class 'std::list<_Ty>' needs to have dll-interface to be used by clients of class 'boost::thread_group' with [ _Ty=boost::thread * ] d:\Programming\boost\boost\boost\bind.hpp(186) : error C2664: 'void (std::string &)' : cannot convert parameter 1 from 'const std::string' to 'std::string &' Conversion loses qualifiers d:\Programming\boost\boost\boost\bind\bind_template.hpp(21) : see reference to function template instantiation 'R boost::_bi::list1<A1>::operator ()<boost::_bi::bind_t<R,F,L>::result_type,void(__cdecl *)(std::string &),boost::_bi::list0>(boost::_bi::type<T>,F,A &) const' being compiled with [ R=boost::_bi::bind_t<void,void (__cdecl *)(std::string &),boost::_bi::list1<boost::_bi::list_av_1<std::string>::B1>>::result_type, A1=boost::_bi::list_av_1<std::string>::B1, F=void (__cdecl *)(std::string &), L=boost::_bi::list1<boost::_bi::list_av_1<std::string>::B1>, T=boost::_bi::bind_t<void,void (__cdecl *)(std::string &),boost::_bi::list1<boost::_bi::list_av_1<std::string>::B1>>::result_type, A=boost::_bi::list0 ] d:\Programming\boost\boost\boost\bind\bind_template.hpp(19) : while compiling class-template member function 'boost::_bi::bind_t<R,F,L>::result_type boost::_bi::bind_t<R,F,L>::operator ()(void)' with [ R=void, F=void (__cdecl *)(std::string &), L=boost::_bi::list1<boost::_bi::list_av_1<std::string>::B1> ] d:\Programming\project\testBoost\testThread\testThread.cpp(36) : see reference to class template instantiation 'boost::_bi::bind_t<R,F,L>' being compiled with [ R=void, F=void (__cdecl *)(std::string &), L=boost::_bi::list1<boost::_bi::list_av_1<std::string>::B1> ] Build log was saved at "file://d:\Programming\project\testBoost\testThread\Debug\BuildLog.htm" testThread - 1 error(s), 8 warning(s) Any suggestions are appreciated.

2 3