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

Borland 5.5.1, STLPort, and regex
by adhalejr 18 Jul '02

18 Jul '02

A few questions about this configuration... I'm trying to compile Boost 1.28.0 using Borland C++ 5.5.1 with the STLPort 4.5.3 STL. I get the following errors on files which include the regex/config.hpp file: libs\regex\build\../src\c_regex_traits.cpp: Error E2272 D:\Tools\Boost\boost_1_28_0\boost/regex/config.hpp 538: Identifier expected Error E2272 D:\Tools\Boost\boost_1_28_0\boost/regex/config.hpp 554: Identifier expected Error E2272 D:\Tools\Boost\boost_1_28_0\boost/regex/config.hpp 578: Identifier expected Error E2272 D:\Tools\Boost\boost_1_28_0\boost/regex/config.hpp 579: Identifier expected Error E2272 D:\Tools\Boost\boost_1_28_0\boost/regex/config.hpp 580: Identifier expected Error E2272 D:\Tools\Boost\boost_1_28_0\boost/regex/config.hpp 581: Identifier expected Error E2272 D:\Tools\Boost\boost_1_28_0\boost/regex/config.hpp 582: Identifier expected Error E2272 D:\Tools\Boost\boost_1_28_0\boost/regex/config.hpp 583: Identifier expected I believe this all has to do with the various C standard library symbols (e.g. fseek) not being "known" when placed in the using ::<symbol> construct. I've wandered through the various config.hpp files, the stuff for platform, compiler, and stdlib, etc. It would seem that the right set of stuff is being picked but there's some unexpected behavior being encountered when #include-ing standard headers from STLPort via Borland. Any ideas on correcting this? Other, somewhat related, questions: If I build w/o STLPort, things seem OK. The regex static libraries are placed in a "runtime-link-dynamic" directory. Threads, on the other hand, has that directory as well as a "runtime-link-static" directory variation. Does the directory name imply which version of the compiler's RTL is required when linking w/ that version of the Boost library? And is there a reason that regex didn't have a "runtime-link-static" directory and associated static library created? I want to statically link the RTL and boost w/ my app. Finally, how do I go about creating just a single boost library (so I can try building threads w/ STLPort w/o encountering the regex errors). Many thanks, Donnie

2 6

Where's MPL
by Ihsan Ali Al Darhi 17 Jul '02

17 Jul '02

Hi... I downloaded Boost 1.28 but there's no MPL. Why? Mo

2 1

Compiling a threads DLL using VC6
by sdussin 17 Jul '02

17 Jul '02

I just downloaded Boost and am trying to do some development using it. Our product will be developed and fielded on both Win2K and Solaris. So far I've been using Boost solely on VC6, and I have a question regarding building the threads library. I've gotten the build to run correctly, but it doesn't seem to build a DLL version of the library. I looked in the both the runtime-link-static and runtime-link-dynamic dirs, and both contain only a .LIB version of the library. Is there something I'm doing wrong here? Or am I misunderstanding what should be generated? Any clarification or pointers would be greatly welcomed. Thanx, Steve Dussinger

2 1

problems w/ msvc6-sp5 and boost::python
by srivatsan raghavan 17 Jul '02

17 Jul '02

i'm having problems w/ vc6 and python.. i'm trying to compile examples\getting_started2.cpp and it compiles , but i get like 23 warnings, and when i throw the getting_started2.dll into the python syspath (specifically in C:\Python22\Lib\site-packages\ ) i get errors form the example\test_getting_started2.py what am i doing wrong? :/ here are the warnings : Compiling... getting_started2.cpp c:\libraries\include\boost\python\detail\types.hpp(37) : warning C4275: non dll-interface struct 'boost::python::detail::base_object<struct _typeobject>' used as base for dll-interface class 'boost::python::detail::type_object_base' c:\libraries\include\boost\python\detail\types.hpp(36) : see declaration of 'type_object_base' c:\libraries\include\boost\python\detail\types.hpp(389) : warning C4251: 'm_storage' : class 'std::vector<struct std::pair<char *,unsigned int>,class std::allocator<struct std::pair<char *,unsigned int> > >' needs to have dll-interface to be used by clients of class 'boost::python::detail::shared_pod_manager' c:\libraries\include\boost\python\objects.hpp(32) : warning C4251: 'm_p' : class 'boost::python::reference<struct _object>' needs to have dll-interface to be used by clients of class 'boost::python::object' c:\libraries\include\boost\python\objects.hpp(270) : warning C4251: 'm_dict' : class 'boost::python::reference<struct _object>' needs to have dll-interface to be used by clients of struct 'boost::python::dictionary_proxy' c:\libraries\include\boost\python\objects.hpp(271) : warning C4251: 'm_key' : class 'boost::python::reference<struct _object>' needs to have dll-interface to be used by clients of struct 'boost::python::dictionary_proxy' c:\libraries\include\boost\python\objects.hpp(336) : warning C4251: 'm_list' : class 'boost::python::list' needs to have dll-interface to be used by clients of struct 'boost::python::list_proxy' c:\libraries\include\boost\python\objects.hpp(146) : see declaration of 'list' c:\libraries\include\boost\python\objects.hpp(351) : warning C4251: 'm_list' : class 'boost::python::reference<struct _object>' needs to have dll-interface to be used by clients of struct 'boost::python::list_slice_proxy' c:\libraries\include\boost\python\classes.hpp(25) : warning C4275: non dll-interface struct 'boost::python::detail::base_object<struct _object>' used as base for dll-interface class 'boost::python::instance' c:\libraries\include\boost\python\classes.hpp(24) : see declaration of 'instance' c:\libraries\include\boost\python\classes.hpp(102) : warning C4251: 'm_name_space' : class 'boost::python::dictionary' needs to have dll-interface to be used by clients of class 'boost::python::instance' c:\libraries\include\boost\python\objects.hpp(274) : see declaration of 'dictionary' c:\libraries\include\boost\python\classes.hpp(138) : warning C4251: 'm_bases' : class 'boost::python::tuple' needs to have dll-interface to be used by clients of class 'boost::python::detail::class_base' c:\libraries\include\boost\python\objects.hpp(56) : see declaration of 'tuple' c:\libraries\include\boost\python\classes.hpp(139) : warning C4251: 'm_name_space' : class 'boost::python::dictionary' needs to have dll-interface to be used by clients of class 'boost::python::detail::class_base' c:\libraries\include\boost\python\objects.hpp(274) : see declaration of 'dictionary' c:\libraries\include\boost\python\detail\functions.hpp(33) : warning C4275: non dll-interface struct 'boost::python::detail::base_object<struct _object>' used as base for dll-interface class 'boost::python::detail::function' c:\libraries\include\boost\python\detail\functions.hpp(32) : see declaration of 'function' c:\libraries\include\boost\python\detail\functions.hpp(49) : warning C4251: 'm_overloads' : class 'boost::python::reference<class boost::python::detail::function>' needs to have dll-interface to be used by clients of class 'boost::python::detail::fu nction' c:\libraries\include\boost\python\detail\functions.hpp(205) : warning C4275: non dll-interface struct 'boost::python::detail::base_object<struct _object>' used as base for dll-interface class 'boost::python::detail::bound_function' c:\libraries\include\boost\python\detail\functions.hpp(204) : see declaration of 'bound_function' c:\libraries\include\boost\python\detail\functions.hpp(217) : warning C4251: 'm_target' : class 'boost::python::reference<struct _object>' needs to have dll-interface to be used by clients of class 'boost::python::detail::bound_function' c:\libraries\include\boost\python\detail\functions.hpp(218) : warning C4251: 'm_unbound_function' : class 'boost::python::reference<struct _object>' needs to have dll-interface to be used by clients of class 'boost::python::detail::bound_function' c:\libraries\include\boost\python\detail\extension_class.hpp(68) : warning C4251: 'm_wrapped_objects' : class 'std::vector<class boost::python::detail::instance_holder_base *,class std::allocator<class boost::python::detail::instance_holder_base *> >' needs to have dll-interface to be used by clients of class 'boost::python::detail::extension_instance' c:\libraries\include\boost\python\detail\extension_class.hpp(73) : warning C4231: nonstandard extension used : 'extern' before template explicit instantiation c:\libraries\include\boost\python\detail\extension_class.hpp(74) : warning C4231: nonstandard extension used : 'extern' before template explicit instantiation c:\libraries\include\boost\python\classes.hpp(234) : warning C4275: non dll-interface class 'boost::python::detail::reprable<class boost::python::detail::callable<class boost::python::detail::getattrable<class boost::python::detail::setattrable<clas s boost::python::detail::type_object<class boost::python::class_t<class boost::python::detail::extension_instance> > > > > >' used as base for dll-interface class 'boost::python::meta_class<class boost::python::detail::extension_instance>' c:\libraries\include\boost\python\detail\extension_class.hpp(74) : see reference to class template instantiation 'boost::python::meta_class<class boost::python::detail::extension_instance>' being compiled c:\libraries\include\boost\python\classes.hpp(236) : warning C4275: non dll-interface class 'boost::noncopyable' used as base for dll-interface class 'boost::python::meta_class<class boost::python::detail::extension_instance>' c:\libraries\include\boost\utility.hpp(50) : see declaration of 'noncopyable' c:\libraries\include\boost\python\detail\extension_class.hpp(74) : see reference to class template instantiation 'boost::python::meta_class<class boost::python::detail::extension_instance>' being compiled c:\libraries\include\boost\python\detail\extension_class.hpp(937) : warning C4541: 'dynamic_cast' used on polymorphic type 'class boost::python::detail::instance_holder_base' with /GR-; unpredictable behavior may result c:\program files\microsoft visual studio 6.0\vc98\include\xmemory(59) : while compiling class-template member function 'void *__thiscall boost::python::detail::extension_class<class `anonymous namespace'::hello,class boost::python::detail::h eld_instance<class `anonymous namespace'::hello> >::extract_object_from_holder(class boost::python::detail::instance_holder_base *) const' c:\libraries\include\boost\python\detail\extension_class.hpp(248) : warning C4541: 'dynamic_cast' used on polymorphic type 'class boost::python::detail::instance_holder_base' with /GR-; unpredictable behavior may result c:\libraries\include\boost\python\detail\extension_class.hpp(241) : while compiling class-template member function 'class `anonymous-namespace'::hello *__cdecl boost::python::python_extension_class_converters<class `anonymous namespace'::hel lo,class boost::python::detail::held_instance<class `anonymous namespace'::hello> >::non_null_from_python(struct _object *,struct boost::python::type<class `anonymous namespace'::hello *>)' Linking... Creating library Debug/getting_started2.lib and object Debug/getting_started2.exp getting_started2.dll - 0 error(s), 23 warning(s) then when i run test_getting_started2.py , these are the errors i get : C:\Downloads\boost_1_28_0\libs\python\example>test_getting_started2.py ***************************************************************** Failure in example: hi.greet() from line #2 of test_getting_started2 Exception raised: Traceback (most recent call last): File "C:\Python22\lib\doctest.py", line 430, in _run_examples_inner compileflags, 1) in globs File "<string>", line 1, in ? RuntimeError: Access violation - no RTTI data! ***************************************************************** Failure in example: invite(hi) from line #4 of test_getting_started2 Exception raised: Traceback (most recent call last): File "C:\Python22\lib\doctest.py", line 430, in _run_examples_inner compileflags, 1) in globs File "<string>", line 1, in ? RuntimeError: Access violation - no RTTI data! ***************************************************************** Failure in example: hi.invite() from line #6 of test_getting_started2 Exception raised: Traceback (most recent call last): File "C:\Python22\lib\doctest.py", line 430, in _run_examples_inner compileflags, 1) in globs File "<string>", line 1, in ? RuntimeError: Access violation - no RTTI data! ***************************************************************** Failure in example: hi2.greet() from line #14 of test_getting_started2 Exception raised: Traceback (most recent call last): File "C:\Python22\lib\doctest.py", line 430, in _run_examples_inner compileflags, 1) in globs File "<string>", line 1, in ? File "<string>", line 3, in greet RuntimeError: Access violation - no RTTI data! ***************************************************************** Failure in example: invite(hi2) from line #16 of test_getting_started2 Exception raised: Traceback (most recent call last): File "C:\Python22\lib\doctest.py", line 430, in _run_examples_inner compileflags, 1) in globs File "<string>", line 1, in ? RuntimeError: Access violation - no RTTI data! C:\Downloads\boost_1_28_0\libs\python\example> --- as you can see, i'm using boost 1.28.0 can anyone tell me what i'm doing wrong? this has been driving me *INSANE* .. :/ __________________________________________________ Do You Yahoo!? Yahoo! Autos - Get free new car price quotes http://autos.yahoo.com

2 2

signals
by Angus Leeming 17 Jul '02

17 Jul '02

I currently have a class that exposes a signal but otherwise hides its internals behind a firewall using the Pimpl idiom: class Foo { public: boost::signal0<void> statusChanged; private: class Impl; boost::scoped_ptr<Impl> const pimpl_; }; Since all I want to do publicly is allow things to connect to this signal: Foo foo; foo.statusChanged.connect(boost::bind(&X::bar, this)); it'd be nice to hide the signal too and replace it with a connect() method: class Foo { public: boost::signals::connection connect(slot_type const &) const; private: class Impl; boost::scoped_ptr<Impl> const pimpl_; }; My problem is defining slot_type. If I have boost::signals::connection Foo::connect(boost::slot<void> const & slot) const { return statusChanged.connect(slot); } I get compiler warnings something like this (below). As you can see, I'm having trouble decyphering the magic that is the boost header files! can someone please help! Kind regards, Angus cxx: Error: ../../../devel/boost/boost/signals/slot.hpp, line 122: #250 reference to void is not allowed detected during instantiation of class "boost::slot<SlotFunction> [with SlotFunction=void]" at line 171 of "../../../devel/src/graphics/GraphicsCacheItem.C" const SlotFunction& get_slot_function() const { return slot_function; } ----------------------^ cxx: Error: ../../../devel/boost/boost/signals/slot.hpp, line 128: #70 incomplete type is not allowed detected during instantiation of class "boost::slot<SlotFunction> [with SlotFunction=void]" at line 171 of "../../../devel/src/graphics/GraphicsCacheItem.C" SlotFunction slot_function; -----------------^ cxx: Error: ../../../devel/src/graphics/GraphicsCacheItem.C, line 171: #304 no instance of overloaded function "boost::signal0<R, Combiner, Group, GroupCompare, SlotFunction>::connect [with R=void, Combiner=boost::last_value<void>, Group=int, GroupCompare=std::less<int>, SlotFunction=boost::function0<void, boost::empty_function_policy, boost::empty_function_mixin, std::allocator<boost::function_base>>]" matches the argument list argument types are: (const boost::slot<void>) return statusChanged.connect(slot); -----------------------------^

2 2

Problem with gcc-Option "-pedantic" on SPARC Solaris 2.7 w. gcc 2.95.2
by aegp2002 17 Jul '02

17 Jul '02

Hi there, I'm a new user of the boost library. I want to use the Boost Graph Library (BGL). For this I downloaded the complete boost package from www.boost.org (boost_all.tar.gz). It is Boost v. 1.28.0. I uncompressed and unpacked the stuff into a directory. Then I created a simple example program to play around with BGL. I ran into trouble when I tried to compile the code. I'm using gcc 2.95.2 on SPARC Sun Solaris 2.7. With the "-pedantic" option given I get this failure: In file included from ../../../boost_1_28_0/boost/detail/numeric_traits.hpp:69, from ../../../boost_1_28_0/boost/counting_iterator.hpp:57, from ../../../boost_1_28_0/boost/pending/integer_range.hpp:15, from ../../../boost_1_28_0/boost/graph/detail/adjacency_list.hpp:34, from ../../../boost_1_28_0/boost/graph/adjacency_list.hpp:293, from nd_patch.C:21: ../../../boost_1_28_0/boost/cstdint.hpp:202: too many `l's in integer constant ../../../boost_1_28_0/boost/cstdint.hpp:205: #error defaults not correct; you must hand modify boost/cstdint.hpp *** Error code 1 Without the -pedantic option everything works fine. As far as I understand I cannot use the option anymore for code that references BGL #includes. Is this a known problem and is there -- maybe -- a workaround? I'd like to use -pedantic because it helps me write standard conformant code. Regards, Adalbert

2 2

Re: [Boost-Users] Boost Sockets
by Beman Dawes 17 Jul '02

17 Jul '02

At 07:08 PM 7/15/2002, James Zappia wrote: >Is there a boost library for network sockets on the radar? Faintly. Several developers have done a certain amount of work, but I don't think the effort is very active at the moment. > Most of the C++ >socket libraries I've seen aren't very appealing. That's also my impression. > Just curious if boost >will be offering something. It is definitely on the wish list. --Beman

5 9

Compiling thread library w/ Borland 5.5.1 and STLPort 4.5.3
by adhalejr 17 Jul '02

17 Jul '02

I'm trying to compile the thread library using the Borland command line tools, version 5.5.1, and the STLPort version of STL, version 4.5.3. When the source files #include Borland's <process.h> file, the following errors occur: Error E2337 c:\borland\bcc55\include\process.h 74: Only one of a set of overloaded functions can be "C" Error E2337 c:\borland\bcc55\include\process.h 87: Only one of a set of overloaded functions can be "C" Error E2337 c:\borland\bcc55\include\process.h 99: Only one of a set of overloaded functions can be "C" Error E2337 c:\borland\bcc55\include\process.h 180: Only one of a set of overloaded functions can be "C" Error E2337 c:\borland\bcc55\include\process.h 191: Only one of a set of overloaded functions can be "C" Error E2337 c:\borland\bcc55\include\process.h 192: Only one of a set of overloaded functions can be "C" Error E2337 c:\borland\bcc55\include\process.h 201: Only one of a set of overloaded functions can be "C" Error E2337 c:\borland\bcc55\include\process.h 218: Only one of a set of overloaded functions can be "C" A number of the functions prototyped in there, though not all of them, are making the compiler choke. FWIW, the build did work if I just used the stock Borland STL. Any ideas on correcting this? Thanks, Donnie

1 1

boost.python and gcc 3.1
by Nikolay Mladenov 17 Jul '02

17 Jul '02

Hi, I am trying to use boost.python 1.28 with gcc 3.1 on cygwin, and I am getting an error that puzzles me: $ gcc -c -I/usr/src/boost_1_28_0 -I"/e/Program Files/Python/include" -I/home/nickm/sources/include -I/e/ug150/ugopen -mno-cygwin -shared /home/nickm/sources/src/ugx/py/styler_py.cpp -o styler_py.o /usr/src/boost_1_28_0/boost/python/cross_module.hpp: In instantiation of `boost::python::python_import_extension_class_converters<std::vector<tag_t, std::allocator<tag_t> > > boost::python::py_extension_class_converters(boost::python::type<std::vector<tag_t, std::allocator<tag_t> > >, bool)': /usr/src/boost_1_28_0/boost/python/detail/extension_class.hpp:388: instantiated from `PyObject* boost::python::to_python(const T&) [with T = std::vector<tag_t, std::allocator<tag_t> >]' /usr/src/boost_1_28_0/boost/python/callback.hpp:70: instantiated from `static R boost::python::callback<R>::call_method(PyObject*, const char*, const A1&, const A2&) [with A1 = std::vector<tag_t, std::allocator<tag_t> >, A2 = saUIStyler::DialogSelection, R = saUIStyler::CallbackResult]' /home/nickm/sources/src/ugx/py/styler_py.cpp:225: instantiated from here /usr/src/boost_1_28_0/boost/python/cross_module.hpp:71: default argument given for parameter 2 of ` boost::python::python_import_extension_class_converters<std::vector<tag_t, std::allocator<tag_t> > > boost::python::py_extension_class_converters(boost::python::type<std::vector<tag_t, std::allocator<tag_t> > >, bool = 0)' /usr/src/boost_1_28_0/boost/python/cross_module.hpp:71: after previous specification in ` boost::python::python_import_extension_class_converters<std::vector<tag_t, std::allocator<tag_t> > > boost::python::py_extension_class_converters(boost::python::type<std::vector<tag_t, std::allocator<tag_t> > >, bool = 0)' /usr/src/boost_1_28_0/boost/python/cross_module.hpp: In instantiation of `boost::python::python_import_extension_class_converters<DVect3D> boost::python::py_extension_class_converters(boost::python::type<DVect3D>, bool)': /usr/src/boost_1_28_0/boost/python/detail/extension_class.hpp:388: instantiated from `PyObject* boost::python::to_python(const T&) [with T = Vector3D<double>]' /usr/src/boost_1_28_0/boost/python/callback.hpp:125: instantiated from `static R boost::python::callback<R>::call_method(PyObject*, const char*, const A1&, const A2&, const A3&, const A4&) [with A1 = tag_t, A2 = Vector3D<double>, A3 = Vector3D<double>, A4 = saUIStyler::DialogSelection, R = saUIStyler::CallbackResult]' /home/nickm/sources/src/ugx/py/styler_py.cpp:265: instantiated from here /usr/src/boost_1_28_0/boost/python/cross_module.hpp:71: default argument given for parameter 2 of ` boost::python::python_import_extension_class_converters<DVect3D> boost::python::py_extension_class_converters(boost::python::type<DVect3D>, bool = 0)' /usr/src/boost_1_28_0/boost/python/cross_module.hpp:71: after previous specification in ` boost::python::python_import_extension_class_converters<DVect3D> boost::python::py_extension_class_converters(boost::python::type<DVect3D>, bool = 0)' Can somebody help me understand what the problem is? Thanks in advance Nikolay

1 0

boost::python and operator overloading
by srivatsan raghavan 16 Jul '02

16 Jul '02

hi all, i'm using boost::python to add acces to a C++ based network logging system from python and i'm running into a few snags wrt operator overloading .. specifically.. some of the classes support some operator signatures that i'm not sure how to export to python .. the python docs & boost::python discuss overloading operators, but only in the context of numeric extensions, and there is some things about a __coerce__ method .. but i'm not clear on how they should be used .. for example supports a stream-like interface: class LogStream { ILogStream& operator<<(long double ld); ILogStream& operator<<(std::string s); //for stream manipulators ILogStream& operator<<( ILogStream& (*pf)(ILogStream&)); } ; these are clearly not numeric operator overloads is there any way i can map these operators to their python equivalents ? --vat __________________________________________________ Do You Yahoo!? Yahoo! Autos - Get free new car price quotes http://autos.yahoo.com

1 0