- Boost-users - lists.boost.org

Problem with linking to boost::signals
by René Möhring 24 Jan '03

24 Jan '03

I try to use boost signals and have the following code from the tutorial. #include <boost/signal.hpp> #include <iostream> struct HelloWorld { void operator()() const { std::cout << "Hello, World!" << std::endl; } }; int main() { // Signal with no arguments and a void return value boost::signal<void ()> sig; // Connect a HelloWorld slot HelloWorld hello; sig.connect(hello); // Call all of the slots sig(); } This compiles but gives these errors while linking: /usr/bin/ld: warning: libstdc++.so.3, needed by /usr/local/lib//libboost_signals.so, may conflict with libstdc++.so.4 test.o: In function `_ZN5boost4slotINS_8functionIFvvENS_6detail8function8unusableES5_S5_S5_ S5_S5_S5_S5_S5_S5_EEEC1I10HelloWorldEERKT_': test.o(.gnu.linkonce.t._ZN5boost4slotINS_8functionIFvvENS_6detail8funct ion8unusableES5_S5_S5_S5_S5_S5_S5_S5_S5_EEEC1I10HelloWorldEERKT_+0xac): undefined reference to `boost::signals::detail::slot_base::create_connection()' test.o: In function `_ZN5boost7signal0IvNS_10last_valueIvEEiSt4lessIiENS_8functionIFvvENS_6 detail8function8unusableES9_S9_S9_S9_S9_S9_S9_S9_S9_EEE7connectERKNS_4s lotISA_EE': test.o(.gnu.linkonce.t._ZN5boost7signal0IvNS_10last_valueIvEEiSt4lessIi ENS_8functionIFvvENS_6detail8function8unusableES9_S9_S9_S9_S9_S9_S9_S9_ S9_EEE7connectERKNS_4slotISA_EE+0x83): undefined reference to `boost::signals::detail::signal_base_impl::connect_slot(boost::any const&, boost::any const&, std::vector<boost::signals::trackable const*, std::allocator<boost::signals::trackable const*> > const&)' test.o: In function `_ZN5boost7signal0IvNS_10last_valueIvEEiSt4lessIiENS_8functionIFvvENS_6 detail8function8unusableES9_S9_S9_S9_S9_S9_S9_S9_S9_EEEclEv': test.o(.gnu.linkonce.t._ZN5boost7signal0IvNS_10last_valueIvEEiSt4lessIi ENS_8functionIFvvENS_6detail8function8unusableES9_S9_S9_S9_S9_S9_S9_S9_ S9_EEEclEv+0x15): undefined reference to `boost::signals::detail::call_notification::call_notification(boost::sh ared_ptr<boost::signals::detail::signal_base_impl> const&)' test.o(.gnu.linkonce.t._ZN5boost7signal0IvNS_10last_valueIvEEiSt4lessIi ENS_8functionIFvvENS_6detail8function8unusableES9_S9_S9_S9_S9_S9_S9_S9_ S9_EEEclEv+0x155): undefined reference to `boost::signals::detail::call_notification::~call_notification()' test.o(.gnu.linkonce.t._ZN5boost7signal0IvNS_10last_valueIvEEiSt4lessIi ENS_8functionIFvvENS_6detail8function8unusableES9_S9_S9_S9_S9_S9_S9_S9_ S9_EEEclEv+0x1c7): undefined reference to `boost::signals::detail::call_notification::~call_notification()' test.o: In function `_ZN5boost7signal0IvNS_10last_valueIvEEiSt4lessIiENS_8functionIFvvENS_6 detail8function8unusableES9_S9_S9_S9_S9_S9_S9_S9_S9_EEEC2ERKS2_RKS4_': test.o(.gnu.linkonce.t._ZN5boost7signal0IvNS_10last_valueIvEEiSt4lessIi ENS_8functionIFvvENS_6detail8function8unusableES9_S9_S9_S9_S9_S9_S9_S9_ S9_EEEC2ERKS2_RKS4_+0xa6): undefined reference to `boost::signals::detail::signal_base::~signal_base()' test.o: In function `boost::signals::connection::~connection()': test.o(.gnu.linkonce.t._ZN5boost7signals10connectionD1Ev+0x16): undefined reference to `boost::signals::connection::disconnect() const' test.o: In function `boost::signals::detail::signal_base::signal_base(boost::function2<bool, boost::any, boost::any, boost::empty_function_policy, boost::empty_function_mixin, std::allocator<boost::function_base> > const&)': test.o(.gnu.linkonce.t._ZN5boost7signals6detail11signal_baseC2ERKNS_9fu nction2IbNS_3anyES4_NS_21empty_function_policyENS_20empty_function_mixi nESaINS_13function_baseEEEE+0x41): undefined reference to `boost::signals::detail::signal_base_impl::signal_base_impl(boost::func tion2<bool, boost::any, boost::any, boost::empty_function_policy, boost::empty_function_mixin, std::allocator<boost::function_base> > const&)' test.o: In function `_ZN5boost7signal0IvNS_10last_valueIvEEiSt4lessIiENS_8functionIFvvENS_6 detail8function8unusableES9_S9_S9_S9_S9_S9_S9_S9_S9_EEED2Ev': test.o(.gnu.linkonce.t._ZN5boost7signal0IvNS_10last_valueIvEEiSt4lessIi ENS_8functionIFvvENS_6detail8function8unusableES9_S9_S9_S9_S9_S9_S9_S9_ S9_EEED2Ev+0x11): undefined reference to`boost::signals::trackable::~trackable()' test.o(.gnu.linkonce.t._ZN5boost7signal0IvNS_10last_valueIvEEiSt4lessIi ENS_8functionIFvvENS_6detail8function8unusableES9_S9_S9_S9_S9_S9_S9_S9_ S9_EEED2Ev+0x1f): undefined reference to`boost::signals::detail::signal_base::~signal_base()' test.o: In function `void boost::checked_delete<boost::signals::detail::signal_base_impl>(boost:: signals::detail::signal_base_impl*)': test.o(.gnu.linkonce.t._ZN5boost14checked_deleteINS_7signals6detail16si gnal_base_implEEEvPT_+0x19): undefined reference to`boost::signals::detail::signal_base_impl::~signal_base_impl()' My compiler is gcc 3.2 on FreeBSD. g++ -o signals test.cpp -I/usr/local/include -L/usr/local/lib/ -lboost_signals Do you have an idea what I am doing wrong?

1 0

Specifying a case-insensitive rule for a regex algorithm
by Amittai Aviram 23 Jan '03

23 Jan '03

Hi! I am using boost::regex_grep() and boost::regex_search(), and I've figured out how to set a given rule to be case-insensitive when I transform it from a string into a rule -- i.e., -- boost::regex("search[[:space:]]string", boost::regbase::normal | boost::regbase::icase) This is great. But in many regular expression processing environments, you also have the option to specify case-insensitivity (or sensitivity) within the rule string itself. For instance, in Perl, you do it with the /i switch at the end of the rule string, and in some environments you can use (?i) to make the following characters case-insensitive when processed and then (?-i) to switch case sensitivity back on. I didn't see any mention of any such thing in the regex documentation. Is this option not available in boost::regex? Thanks! Amittai Aviram amittai(a)amittai.com

4 3

Problems using date-time library
by Keno 22 Jan '03

22 Jan '03

Greets all, I'm in need of using the Date-Time library but I'm encountering a few issues. I tried compiling the following simple code: ----------------- #include <boost/date_time/gregorian/gregorian.hpp> #include <iostream> using namespace boost::gregorian; int main() { date birthday(1979,3,26); return 0; } ------------------- and got the following error(s): --------------------Configuration: boost_date - Win32 Debug-------------------- Compiling... test_date.cpp d:\softdev\vstudio6\vc98\include\new(35) : warning C4290: C++ Exception Specification ignored Linking... test_date.obj : error LNK2001: unresolved external symbol "public: static unsigned long __cdecl boost::date_time::gregorian_calendar_base<struct boost::date_time::year_month_day_base<class boost::gregorian::greg_year,class boost::gregorian::greg_mon th,class boost::gregorian::greg_day>,unsigned long>::day_number(struct boost::date_time::year_month_day_base<class boost::gregorian::greg_year,class boost::gregorian::greg_month,class boost::gregorian::greg_day> const &)" (?day_number@?$gregorian_ca lendar_base@U?$year_month_day_base@Vgreg_year@gregorian@boost@@Vgreg_month@2 3@Vgreg_day@23@@date_time@boost@@K@date_time@boost@@SAKABU?$year_month_day_b ase@Vgreg_year@gregorian@boost@@Vgreg_month@23@Vgreg_day@23@@23@@Z) Debug/boost_date.exe : fatal error LNK1120: 1 unresolved externals Error executing link.exe. boost_date.exe - 2 error(s), 1 warning(s) ------------------------------- Any clues as to what could be happening here folks?? I'm using MSVC6 with SP5 + STLPort 4.5.3 on WinXP .: Keno :.

3 7

random number lib: msvc6, prob compiling random_demo.cpp w mt19937
by Nick Toze <geeky_nick＠yahoo.co.uk> 15 Jan '03

15 Jan '03

Hello, I had a slight problem compiling random_demo.cpp after I had changed the typedef to: typedef boost::mt19937 base_generator_type; I got this error: --------------------Configuration: random_demo - Win32 Debug-------------------- Compiling... random_demo.cpp d:\c_plus_plus\boost_1_29_0\boost\random\mersenne_twister.hpp(104) : error C2064: term does not evaluate to a function d:\c_plus_plus\boost_1_29_0\boost\random\mersenne_twister.hpp(75) : see reference to function template instantiation 'void __thiscall boost::random::mersenne_twister<unsigned long,624,397,31,-1727483681,11,7,-1658038656,15,-272236544,18,-948 541730>::seed(const unsigned int &)' being compiled Error executing cl.exe. Creating browse info file... random_demo.exe - 1 error(s), 0 warning(s) I fixed it by adding an 'L' to the first line of main, i.e. base_generator_type generator(42Lu);

1 0

Boost/Python: method overloading w/out default args
by Bruce Lowery <bruce_lowery＠yahoo.com> 15 Jan '03

15 Jan '03

Using Boost/Python, how does one overload methods? For instance: struct Bar { void func( const std::string& s ); void func( int i ); }; BOOST_PYTHON_MODULE( Foo ) { class_<Bar>( "Bar" ) .def( "func", &Bar::func ) .def( ??? ) ; } The reference documentation discusses the BOOST_PYTHON_MEMBER_FUNCTION_OVERLOADS macro, but it only seems to apply to methods with default arguments. --bruce

2 2

Boost/Python: returning internal reference
by Bruce Lowery <bruce_lowery＠yahoo.com> 15 Jan '03

15 Jan '03

I have a simple C++ class that I've wrapped using Boost/Python, v1.29.0 (on Win 2K), and that has a simple accessor returning a const ref to an internal string. In the python interpreter, the accessor raises an exception (see below),whereas another access that returns a copy of the string works. Could someone explain my mistake? --bruce ------ Bar.cpp -------- #include <string> class Bar { public: Bar( const std::string& s ) : m_s( s ) {} std::string get_s_copy() const { return m_s; } const std::string& get_s_ref() const { return m_s; } std::string m_s; }; #include <boost/python.hpp> using namespace boost::python; BOOST_PYTHON_MODULE(Foo) { class_<Bar>( "Bar", init< const std::string& >( args("s") ) ) .def( "get_s_copy", &Bar::get_s_copy ) .def( "get_s_ref", &Bar::get_s_ref, return_internal_reference<>() ) .def_readonly( "m_s", &Bar::m_s ) ; } ----- Python session ---- Python 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import Foo >>> bar = Foo.Bar("hello") >>> bar.m_s 'hello' >>> bar.get_s_copy() 'hello' >>> bar.get_s_ref() Traceback (most recent call last): File "<stdin>", line 1, in ? TypeError: bad argument type for built-in operation >>>

2 3

Boost/Python: Solaris build errors
by Bruce Lowery <bruce_lowery＠yahoo.com> 15 Jan '03

15 Jan '03

In building the boost/python library on solaris using v6.2.p2 of the sunpro compiler, two compile-time errors occur, one in 'cast.hpp' and the other in 'inheritance.hpp'. Details are below. --bruce ----------------- 1 -------------------- boost/boost/python/cast.hpp: line 65: Error: Default arguments cannot be added in later declarations of the template function in the same scope. 57 template <class Target, class Source> 58 inline Target* downcast(Source* p, yes_convertible) 59 { 60 return static_cast<Target*>(p); 61 } 62 63 template <class Target, class Source> 64 inline Target* downcast(Source* p, no_convertible, boost::type<Target>* = 0) *** 65 { *** 66 typedef typename base_type_traits<Source>::type base; 67 return (Target*)detail::downcast<base>(p, convertible<Source*>::check((base*)0)); 68 } ----------------- 2 -------------------- boost/boost/python/object/inheritance.hpp: line 134: Error: ")" expected instead of ">". 130 template <class Source, class Target> 131 inline void register_conversion( 132 // We need this parameter because CWPro7 can't determine 133 // which is the base reliably. *** 134 bool is_downcast = !cast_generator<Source,Target>::is_upcast *** 132 133 // These parameters shouldn't be used, they're an MSVC bug workaround 134 , Source* = 0, Target* = 0) 135 { 136 typedef typename cast_generator<Source,Target>::type generator; 137 138 add_cast(python::type_id<Source>() 139 , python::type_id<Target>() 140 , &generator::execute 141 , is_downcast); 142 }

2 2

RE: [Boost-Users] [BGL] missing include in boost/graph/kruskal_mi n_spanning_tree.hpp
by bjorn.karlsson＠readsoft.com 13 Jan '03

13 Jan '03

> From: Jeppe N. Madsen [mailto:yg-boost-users@m.gmane.org] > > Hi, > > kruskal_min_spanning_tree uses bgl_named_params defined in > boost/graph/named_function_params.hpp, which is not included.... Fixed in CVS. Thanks! Bjorn

1 0

BGL: filtered graphs, write_graphviz, and out of memory messages
by sa3h1n <sa3h1n＠yahoo.com> 13 Jan '03

13 Jan '03

Hi all: I am seeing a strange interaction between filtered graphs and write_graphviz. Briefly, if I try to write out a filtered graph via write_graphviz, compilation ends with an out-of-memory message. A necessary condition for this to happen is that the value_type of the property map I am filtering cannot be of a native type -- int is ok, std::string is not. Example code is appended below. I am using Codewarrior Dev Tools 8.0 on WinXP Pro. Given that the code does not even compile, I am not sure how to move beyond this point. Any ideas? TIA, - S ----------------------------------------------------------------- #include "boost/config.hpp" #include <fstream.h> #include <iostream> // for std::cout #include <utility> // for std::pair #include <algorithm> // for std::for_each #include "boost/utility.hpp" // for boost::tie #include "boost/graph/graph_traits.hpp" // for boost::graph_traits #include "boost/graph/adjacency_list.hpp" #include "boost/graph/graphviz.hpp" #include "boost/graph/filtered_graph.hpp" using namespace boost; namespace boost { enum edge_prop_t { edge_prop = 389457 }; BOOST_INSTALL_PROPERTY(edge, prop); } template <typename T> struct positive_edge_prop { positive_edge_prop() {}; positive_edge_prop(T t) : m_prop(t) {}; template <typename Edge> bool operator() (const Edge& e) const { return "foo" == get(m_prop, e); } T m_prop; }; int main(void) { // create an edge property // if std::string is replaced with int, and some attendant changes are made, the code compiles typedef property<edge_prop_t, std::string> EdgeProperty; // create a simple graph type typedef adjacency_list<vecS, vecS, bidirectionalS, no_property, EdgeProperty> Pgraph; enum { A, B, C, D, E, F, N }; const int num_vertices = N; typedef std::pair<int, int> Edge; Edge edge_array[] = { Edge(A, B), Edge(B, C), Edge(C, D), Edge(D, E), Edge(E, F), Edge(F, A), }; const int num_edges = sizeof(edge_array)/sizeof(edge_array[0]); Pgraph pg(edge_array, edge_array + num_edges, num_vertices); // Add edge properties typedef boost::property_map<Pgraph, edge_prop_t>::type ewt; ewt ew = get(edge_prop_t(), pg); boost::graph_traits<Pgraph>::edge_iterator ei, ei_end; boost::tie(ei, ei_end) = edges(pg); for (ei; ei != ei_end; ei++) put(ew, *ei, "bar"); std::map<std::string,std::string> graph_attr, vertex_attr, edge_attr; boost::write_graphviz(std::cout, pg); positive_edge_prop<ewt> filter(get(edge_prop_t(), pg)); filtered_graph<Pgraph, positive_edge_prop<ewt> > fg(pg, filter); boost::write_graphviz(std::cout, fg); // if this line is commented out, the code compiles just fine return 0; } -----------------------------------------------------------------

1 0

Next release date???
by Alejandro Escalante Medina 13 Jan '03

13 Jan '03

Does anyone have an idea for the date of the next release??? Thanks, 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 1