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

linking Signals Library
by John Fletcher 01 Apr '03

01 Apr '03

System: Red Hat 8.0 with gcc 3.2 Boost 1_30_0 I have built the boost signals library using bjam. The test suite runs and passes all tests. How do I make the resulting libraries available to my own programs? Is there an equivalent of 'make install' which will move the results to somewhere from which linking is possible? I have searched the documentation on Boost Signal and also on building libraries and have found nothing on this. Thanks John Fletcher

2 3

[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

[uBLAS] operations thoughts
by vladimir josef sykora 28 Mar '03

28 Mar '03

Hello, Had a quick look into uBLAS library, and noted the incompatibility between std::vector<> and ublas' binary operations. For example, I have an ublas::matrix<> and wanted to multiply it by a std::vector<>. Since _all_ of ublas data containers provide iterators, I'm wondering why the library doesn't provide algorithms that work on iterators? In this way data structures and operators will be decoupled. For example, to do the product between a matrix and a vector: ********* untested code ********* template <class MatrixRowIterator, class MatrixColIterator, class InputIterator, class OutputIterator> OutputIterator prod(MatrixRowIterator first_row, MatrixRowIterator last_row, MatrixColIterator, InputIterator first_vec, OutputIterator result) { InputIterator cp_first=first_vec; while(first_row!=last_row) { typename MatrixRowIterator::value_type val(0); MatrixColIterator first_col, last_col; first_col=first_row.begin(); last_col=first_row.end(); while(first_col!=last_col) val+= *first_col++ * *first_vec++; *result++ = val; ++first_row; first_vec=cp_first; } return result; } // user side : prod(umatrix.begin1(), umatrix.end1(), umatrix.begin2(), std_vector.begin(), std::back_inserter(std_vector_result)); This of course with the respective preconditions. Also, wouldn't be a good idea to provide copy c'tor and operators accepting std::vector<> for the ublas::vector<> ? Regards, -- vladimir josef sykora morphochem AG gmunder str. 37-37a 81379 muenchen tel. ++49-89-78005-0 fax ++49-89-78005-555 vladimir.sykora(a)morphochem.de http://www.morphochem.de

2 1

BGL properties question
by Jeff Holle 28 Mar '03

28 Mar '03

I would like to write a "generic" routine that prints the named vertex and edges properties. I can see in this code sibit (from graphviz.cpp) that the info that I want is present: > vertex_label(const Vertex& u, const GraphvizDigraph& g) { > boost::property_map<GraphvizDigraph, > boost::vertex_attribute_t>::const_type > va = boost::get(boost::vertex_attribute, g); > return (*(va[u].find("label"))).second; > } It appears that va is a map<Vertex, map<string, "property value"> > How would I write code that prints the names of the properites of a given vertex? (It would involve iterating over the map whose find method is used in the above code segment).

2 1

BGL 1.30.0 upgrade problem
by Jeff Holle 28 Mar '03

28 Mar '03

Having switched from boost_1_29_0 to boost_1_30_0, code that was compiling and running now produces this error message: I'm using Mandrake linux 9.0 with the gcc v3.22 compiler. /home/jholle/boost_1_30_0/boost/graph/connected_components.hpp: In function `boost::property_traits<IndexMap>::value_type boost::connected_components(const Graph&, ComponentMap) [with Graph = boost::subgraph<boost::adjacency_list<boost::vecS, boost::vecS, boost::directedS, boost::GraphvizVertexProperty, boost::GraphvizEdgeProperty, boost::GraphvizGraphProperty, boost::listS> >, ComponentMap = boost::iterator_property_map<__gnu_cxx::__normal_iterator<size_t*, std::vector<size_t, std::allocator<size_t> > >, boost::subgraph_property_map<boost::subgraph<boost::adjacency_list<boost::vecS, boost::vecS, boost::directedS, boost::GraphvizVertexProperty, boost::GraphvizEdgeProperty, boost::GraphvizGraphProperty, boost::listS> >*, boost::vec_adj_list_vertex_id_map<boost::GraphvizVertexProperty, size_t> >, unsigned int, unsigned int&>]': BGLLayout.cpp:49: instantiated from here /home/jholle/boost_1_30_0/boost/graph/connected_components.hpp:99: `sizeof' applied to incomplete type `boost::STATIC_ASSERTION_FAILURE<false>' The code that produced this error is: void BGLLayout::FindComponents(void) { typedef vector<unsigned int> Ints; Ints c(num_vertices(m_graph)); connected_components(m_graph, make_iterator_property_map(c.begin(), get(vertex_index, m_graph), c[0])); << -- line 49 (error source) m_componentStartVertex.clear(); unsigned int i=0; for (Ints::const_iterator iter=c.begin(); iter != c.end(); ++iter,++i) if (m_componentStartVertex.size() <= *iter) m_componentStartVertex.push_back(i); } Note this code is largely taken from connected_components.cpp. Can anybody tell me what is wrong here?

3 5

'boost::detail' problem
by Alejandro Escalante Medina 27 Mar '03

27 Mar '03

I do also a problem with some code that used to work in 1.29. The following is the output of VC7: d:\development\boost\libs\test\src\unit_test_main.cpp(63) : error C2872: 'detail' : ambiguous symbol could be 'boost::unit_test_framework::detail' or 'boost::detail' I saw someone reported something similar, but I couln't figure out what's wrong... Any ideas? Alex _________________________________________________________ Do You Yahoo!? La mejor conexión a internet y 25MB extra a tu correo por $100 al mes. http://net.yahoo.com.mx

2 4

Re: bjam issue related to boost::python
by Ben Hutchings 27 Mar '03

27 Mar '03

In article <23681.5566233874$1028263753(a)news.gmane.org>, Srivatsan Raghavan wrote: > hi all , > i created a c++ extension module using python which worked fine.. > > then i wanted to embed a call to PyRun_SimpleFile in another app, > and the script i was calling is attempting to use my extension module > > but i was getting telling me that the interpreter wasn't initialized > after much searching, research, and work with msvc's Dependency Walker > i narrowed it down to the fact that boost_python_debug.dll is trying to > link to the release version of python22.dll , whereas it should be > linking to python22_d.dll (which unfortunately does not come with the > python installer , that has to be compiled manually ) > > at any rate, how can the boost::python Jamfile be modified to try this > check when it comes boost::python ? This is correct. The 'debug' configuration is meant to work with a release version of Python, though I don't know why. However, there is no need to modify the Jamfile; just use the 'debug-python' configuration instead. Also, make sure you include <pyconfig.h> before any of the Boost.Python headers, because not all of them do that and you can end up with incorrect structure definitions in a debug build if you don't. (I should report this bug.)

2 4

newbie build question (threads and win32)
by Dave Viner 27 Mar '03

27 Mar '03

Hi, I'm trying to use Boost's threads on WIN32 using VC++ and having some difficulty. I've built the source cd D:\boost\boost_1_30_0; bjam "-sTOOLS=msvc" and after the build is done, there are some errors, but they all appear related to the regression testing. Then I cd libs\thread\build; bjam "-sTOOLS=msvc" and everything appears to work fine. However, my simple program can't compile. I get this error: d:\boost\boost_1_30_0\boost\thread\thread.hpp(17) : fatal error C1189: #error : Thread support is unavailable! My test program simply is: #include <boost/thread/thread.hpp> int main(int argc, char* argv[]) { printf("Hello World!\n"); return 0; } I can't seem to figure out why threads aren't enabled. I realize this is a very simple question, but I'd love to hear what silly thing I've done wrong. Thanks in advance for your help. dave

2 2

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

27 Mar '03

I agree :( I tried to use the debugger, but once it went into stlport_icl.dll I couldn't see which ostream function was being called. I'm currently trying to change the ostream signature to take a reference rather than a copy, in hopes that that will help. Unfortunately the amount of code to compile between these areas is quite large. > -----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

very basic questions
by jeremmim 27 Mar '03

27 Mar '03

hello, i have downloaded the boost_1_30_0.tar.gz package. and have unzipped it. it has worked succesfully. we don't know what to do next: we'd like to use this library to build a graph. jeremie

2 1

test report_level in 1.30.0
by John Van Horne 27 Mar '03

27 Mar '03

We just upgraded from 1.29.0 to 1.30.0 and started having a problem running in the unit test framework. When we start the test with the command line parameter "--report_level=detailed" the tests crash. They work fine if we set the environment parameter BOOST_TEST_REPORT_LEVEL=detailed, or when we set other command line parameters, such as "--log_level=detailed". I looked at the code in libs/test/src/unit_test_main.cpp and saw that the command line parsing for report_level doesn't occur until after the unit test suite has been invoked. It appears that the unit test is then getting a command line that contains "--report_level=detailed". In our case, it doesn't know what to do with this. I hacked our copy of unit_test_main.cpp to parse the command line for --report_level before starting the unit test suite, storing the value locally. Has anyone else had this problem? Are we using the unit test framework the wrong way? Do you think I fixed it the right way, and will there be an official fix soon? Thanks, -John Van Horne

3 3

Building Boost with MSVC 6
by Alex 27 Mar '03

27 Mar '03

I fail to build the Boost libraries with MSVC 6. Specifically, I need to build the BGL but is complains that GRAPHVIZ_GRAPH is not defined. I am running: bjam "-sTOOLS=msvc" Please help!

3 4

Most efficient way to convert a run of Perl substitutions til boost::regex?
by Anders Johansen 27 Mar '03

27 Mar '03

Hi! I'm converting a Perl program that basically consists of a succession of regex transformations of the input string, eg.: #Case 1 - mutually exclusive endings s/erens$/\@r\@ns_/; s/ernes$/\@rn\@s_/; s/endes$/\@n\@s_/; s/estes$/\@st\@s_/; #Case 2: - a load of manipulations done in sequence s/jou/sju/g; s/jau/sjo/g; s/nch/ngk/g; Now the question is, how do I convert this to boost::regex code that runs as fast as possible. I expect to have to call the function implementing these transformations (there are /many/) about half a million times at runtime, and as I'm concerned about runtime performance, I'd obviously like to use the most efficient method available. I expect that Case #2 is simple, as I can use the regex_merge function, and nest the calls as in: static const boost::regex re1("jou"); static const boost::regex re1("jau"); static const boost::regex re1("nch"); static const std::string fs1("sju"); static const std::string fs2("sjo"); static const std::string fs3("ngk"); std::string res = regex_merge( regex_merge( regex_merge(input_string, re1, fs1) , re2, fs2) , re3, fs3); As to case 1, I guess I'd have to use a combination of the grep and format functions, and in the case as shown it'd be easy, as there is either one match or none for each line. Any suggestions wrt. improving run-time performance? Sincerely Anders S. Johansen

2 3

Re: [Boost-Users] newbie build question (threads and win32)
by p_i_r_x＠gmx.net 27 Mar '03

27 Mar '03

From: Dave Viner [mailto:daveviner@yahoo.com] Hi, I'm trying to use Boost's threads on WIN32 using VC++ and having some difficulty. I've built the source cd D:\boost\boost_1_30_0; bjam "-sTOOLS=msvc" and after the build is done, there are some errors, but they all appear related to the regression testing. Then I cd libs\thread\build; bjam "-sTOOLS=msvc" and everything appears to work fine. However, my simple program can't compile. I get this error: d:\boost\boost_1_30_0\boost\thread\thread.hpp(17) : fatal error C1189: #error : Thread support is unavailable! My test program simply is: #include <boost/thread/thread.hpp> int main(int argc, char* argv[]) { printf("Hello World!\n"); return 0; } I can't seem to figure out why threads aren't enabled. I realize this is a very simple question, but I'd love to hear what silly thing I've done wrong. Thanks in advance for your help. dave try to set up project/settings/c++/code generation/run-time libary to multithreaded ... ciao andreas -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!

1 0

Error with Thread in 1.30.0: Tempate Depth
by Reed Hedges 27 Mar '03

27 Mar '03

Hello, Has anyone else had this problem? I am trying to build a program that uses the boost_thread library (v. 1.30.0), but get this error repeatedly: /usr/local/include/boost/type_traits/is_convertible.hpp: At top level: /usr/local/include/boost/type_traits/is_convertible.hpp:184: template instantiation depth exceeds maximum of 17 (use -ftemplate-depth-NN to increase the maximum) instantiating `struct boost::add_reference<VOS::AsyncConnect &>' /usr/local/include/boost/type_traits/is_convertible.hpp:184: instantiated from `boost::detail::is_convertible_impl<VOS::AsyncConnect &, boost::detail::int_convertible>' /usr/local/include/boost/type_traits/is_enum.hpp:91: instantiated from `boost::is_convertible<VOS::AsyncConnect &, boost::detail::int_convertible>' /usr/local/include/boost/type_traits/is_enum.hpp:91: instantiated from `boost::detail::is_enum_helper<false>::type<VOS::AsyncConnect &>' /usr/local/include/boost/type_traits/is_enum.hpp:91: instantiated from `boost::detail::is_enum_impl<VOS::AsyncConnect>' /usr/local/include/boost/type_traits/is_scalar.hpp:30: instantiated from `boost::is_enum<VOS::AsyncConnect>' /usr/local/include/boost/type_traits/is_scalar.hpp:30: instantiated from `boost::detail::is_scalar_impl<VOS::AsyncConnect>' /usr/local/include/boost/type_traits/is_pod.hpp:35: instantiated from `boost::is_scalar<VOS::AsyncConnect>' /usr/local/include/boost/type_traits/is_pod.hpp:35: instantiated from `boost::detail::is_pod_impl<VOS::AsyncConnect>' /usr/local/include/boost/type_traits/has_trivial_constructor.hpp:28: instantiated from `boost::is_POD<VOS::AsyncConnect>' /usr/local/include/boost/type_traits/has_trivial_constructor.hpp:28: instantiated from `boost::is_pod<VOS::AsyncConnect>' /usr/local/include/boost/type_traits/has_trivial_constructor.hpp:28: instantiated from `boost::detail::has_trivial_ctor_impl<VOS::AsyncConnect>' /usr/local/include/boost/type_traits/is_stateless.hpp:31: instantiated from `boost::has_trivial_constructor<VOS::AsyncConnect>' /usr/local/include/boost/type_traits/is_stateless.hpp:31: instantiated from `boost::detail::is_stateless_impl<VOS::AsyncConnect>' /usr/local/include/boost/function/function_base.hpp:195: instantiated from `boost::is_stateless<VOS::AsyncConnect>' /usr/local/include/boost/function/function_base.hpp:195: instantiated from `boost::detail::function::get_function_tag<VOS::AsyncConnect>' /usr/local/include/boost/function/function_template.hpp:431: instantiated from `boost::function0<R, Allocator>::assign_to (Functor) [with Functor = VOS::AsyncConnect, R = void, Allocator = allocator<boost::function_base>]' /usr/local/include/boost/function/function_template.hpp:293: instantiated from `boost::function0<R, Allocator>::function0 (Functor) [with Functor = VOS::AsyncConnect, R = void, Allocator = allocator<boost::function_base>]' remotesocketsite.cc:565: instantiated from here /usr/local/include/boost/type_traits/is_convertible.hpp:184: invalid use of undefined type `struct boost::add_reference<VOS::AsyncConnect &>' /usr/local/include/boost/type_traits/add_reference.hpp:78: forward declaration of `struct boost::add_reference<VOS::AsyncConnect &>' VOS::AsyncConnect is my program's class. Setting -ftempate-depth-20 resolves the problem. This problem does not appear in Boost 1.29.0 Any information is greatly appreciated. Thanks reed PS. Here is the full source files: http://www-robotics.cs.umass.edu/~reed/remotesocketsite.hh http://www-robotics.cs.umass.edu/~reed/remotesocketsite.cc The entire project can be downloaded from anonymous CVS (see http://interreality.org)

2 1

Problem with 1.30.0 lexical_cast
by Tom Matelich 27 Mar '03

27 Mar '03

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. Thanks, Tom --------Complete Passing Test Case #include <boost/lexical_cast.hpp> #include <string> #include <cassert> #include <iostream> namespace ZAcquisition { namespace PPG { enum Type { ONE = 0, TWO, THREE, FOUR, INVALID = 100 }; Type stringToType(std::string const&); std::string typeToString(PPG::Type); const int size = 5; const Type values[size] = { ONE, TWO, THREE, FOUR, INVALID }; } } std::ostream& operator<<(std::ostream&, ZAcquisition::PPG::Type); std::istream& operator>>(std::istream&, ZAcquisition::PPG::Type&); namespace { const char s_PPG_ONE[] = "ONE"; const char s_PPG_TWO[] = "TWO"; const char s_PPG_THREE[] = "THREE"; const char s_PPG_FOUR[] = "FOUR"; const char s_PPG_INVALID[] = "INVALID"; } std::string ZAcquisition::PPG::typeToString(ZAcquisition::PPG::Type type) { std::string ret("Invalid_PPG_type"); switch(type) { case PPG::ONE: ret = s_PPG_ONE; break; case PPG::TWO: ret = s_PPG_TWO; break; case PPG::THREE: ret = s_PPG_THREE; break; case PPG::FOUR: ret = s_PPG_FOUR; break; case PPG::INVALID: ret = s_PPG_INVALID; break; default: std::cerr << static_cast<int>(type) << " is not a valid PPG enumeration." << std::endl; } return ret; } ZAcquisition::PPG::Type ZAcquisition::PPG::stringToType(std::string const& str) { PPG::Type ret = PPG::ONE; if(0 == str.compare(s_PPG_TWO)) { ret = PPG::TWO; } else if(0 == str.compare(s_PPG_THREE)) { ret = PPG::THREE; } else if(0 == str.compare(s_PPG_FOUR)) { ret = PPG::FOUR; } else if(0 == str.compare(s_PPG_INVALID)) { ret = PPG::INVALID; } return ret; } std::ostream& operator<<(std::ostream& out, ZAcquisition::PPG::Type type) { return out << ZAcquisition::PPG::typeToString(type); } std::istream& operator>>(std::istream& in, ZAcquisition::PPG::Type& type) { std::string str; in >> str; type = ZAcquisition::PPG::stringToType(str); return in; } int main() { assert(std::string("ONE") == boost::lexical_cast<std::string>(ZAcquisition::PPG::ONE)); return 0; } ----------------------------------------------------------------------- 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