- Boost-users - lists.boost.org

How to wrap a template function(not a member of a template class) into python?
by Qinfeng(Javen) Shi 28 Aug '06

28 Aug '06

Dear All, How can I wrap a c++ template function(not a member of any class) by pyste or manually? /**************************************/ for example : template<class T> void push(v_array<T>& v, const T &new_ele) { while(v.index >= v.length) { v.length = 2*v.length + 3; v.elements = (T *)realloc(v.elements,sizeof(T) * v.length); } v[v.index++] = new_ele; } /***************************************/ Here v_array is a class. I know how to wrap a c++ template class into python by pyste. But what should I do if the template function is not a member of a class. (I don't want to put the function"push()" into a class). Any suggestion will be appreciated. Thanks! Javen Research School of Information Sciences and Engineering Australian National University Locked Bag 8001 Canberra ACT 2601

2 1

Re: [Boost-users] boost program_options
by Vladimir Prus 28 Aug '06

28 Aug '06

On Monday 28 August 2006 15:49, you wrote: > Hello, Hi, please send all Boost questions to some mailing list, not in private. > > in your tutorial for program_options at the boost site you talk about > the method allow_unregistered() lite this: > > parsed_options parsed = > command_line_parser(argv, > argc).options(desc).allow_unregistered().run(); > > > However, I'm using boost 1.33 and the command_line_parser class uses > private inheritence from the detail::cmdline class, which makes the > allow_unregistered() method unavailable for public use. What is the > deal? That's a bug in 1.33. The operation of allow_unregistered was unit-tested, but since unit test used detail::cmdline directly, the fact that the method is not accessible in command_line_parser went undetected. I believe it's fixed in CVS. - Volodya

2 1

[interval]
by Andy Little 28 Aug '06

28 Aug '06

Shouldnt this work?: #include <boost/numeric/interval.hpp> int main() { boost::numeric::interval<double> v(.5); cos(v); } ------------------ I get this error in VC7.1: c:\boost\include\boost-1_33_1\boost\numeric\interval\transc.hpp(73) : error C2039: 'cos_down' : is not a member of 'boost::numeric::interval_lib::rounded_math<double>' c:\boost\include\boost-1_33_1\boost\numeric\interval\hw_rounding.hpp(53) : see declaration of 'boost::numeric::interval_lib::rounded_math<double>' e:\Projects\Test\test.cpp(6) : see reference to function template instantiation 'boost::numeric::interval<T> boost::numeric::cos<double,boost::numeric::interval_lib::default_policies<T>::type>(const boost::numeric::interval<T> &)' being compiled with [ T=double ] c:\boost\include\boost-1_33_1\boost\numeric\interval\transc.hpp(73) : error C2039: 'cos_up' : is not a member of 'boost::numeric::interval_lib::rounded_math<double>' c:\boost\include\boost-1_33_1\boost\numeric\interval\hw_rounding.hpp(53) : see declaration of 'boost::numeric::interval_lib::rounded_math<double>' c:\boost\include\boost-1_33_1\boost\numeric\interval\transc.hpp(75) : error C2039: 'cos_up' : is not a member of 'boost::numeric::interval_lib::rounded_math<double>' c:\boost\include\boost-1_33_1\boost\numeric\interval\hw_rounding.hpp(53) : see declaration of 'boost::numeric::interval_lib::rounded_math<double>' regards Andy Little

2 3

boost::condition
by Andrew Wingorodov 28 Aug '06

28 Aug '06

I wish to lock some threads up to the end of one of them, and after to start all of them without restrictions. show to me an example, plz the timedwait is necessary. -- andr.ru

1 0

[serialization] class versioning with template classes
by Oliver Mutz 28 Aug '06

28 Aug '06

Hi all, has anyone ever used the versioning mechanism of the serialization library together with template classes? What I want to do is something like: class TemplateA { public: TemplateA(); public: ... //Serialization stuff private: friend class boost::serialization::access; template<class Archive> void save(Archive & ar, const unsigned int /*version*/) const { ar & boost::serialization::make_nvp("HighValue",m_high) & boost::serialization::make_nvp("NewData",m_newData); } template<class Archive> void load(Archive & ar, const unsigned int version) { ar & boost::serialization::make_nvp("HighValue",m_high); if (version > 0) { ar & boost::serialization::make_nvp("NewData",m_newData); } } BOOST_SERIALIZATION_SPLIT_MEMBER(); private: T m_high; T m_newData; }; // class TemplateA BOOST_CLASS_VERSION(TemplateA, 1); The above won't compile for sure, but I'm looking for a way to use the versioning without having to specialize it for each type T which I'm going to use this class with. Best regards Oliver Mutz

1 0

Debian Sarge less-then-g++-4.0.x link-time issues
by Matt England 28 Aug '06

28 Aug '06

Our project is experiencing a lot of Debian link-time issues with Boost libraries, namely with g++ versions less then 4.0.x. Some bug listings: http://www.cleversafe.org/bugs/show_bug.cgi?id=260 http://www.cleversafe.org/bugs/show_bug.cgi?id=239 Does the boost-users community have any pointers/ideas/suggestions/references? Some of our devs think that these problems may be due to bugs in g++ 3.3.5 or less; we have unconfirmed reports that g++ 3.3.5 or less builds may have failed on other Linux platforms. -Matt Dispersed Storage: http://cleversafe.org

1 1

shared_ptr segfaults on 64bit AMD
by Paul Davis 27 Aug '06

27 Aug '06

Howdy, I've come across an odd segfault that originates in some of the boost code. (By originate, meaning thats where the stack trace points, I'm not sure if its me or boost thats wrong) Anyway, the weird part is that its only on my 64 bit machine. I took a look at where its segfaulting in boost::detail::atomic_exchange_and_add(). Its scary inline assembly stuff. Well, mostly I just don't know assembly so I haven't the slightest idea if its right or wrong. And obviously, its a platform specific header and what not so I imagine its limited to this area. I have had other weird segfaults that come and go from the atomic_* set of methods. I can't pin down exactly whats causing it. They mostly seem to be coming from storing shared_ptr's in STL containers. I've never had any problems with it before so I'm assuming its just a relatively untested section of code. And if its relevant, I also tried downloading CVS and running the shared_ptr_test. It ran without segfaulting just fine. Some relevant info: Segfaults on: 2.6.15-25-amd64-generic #1 SMP PREEMPT Wed Jun 14 11:28:03 UTC 2006 x86_64 GNU/Linux g++ (GCC) 4.0.3 (Ubuntu 4.0.3-1ubuntu5) boost/version.hpp #define BOOST_VERSION 103301 Does NOT segfault on: 2.6.15-1.1831_FC4smp #1 SMP Tue Feb 7 13:48:31 EST 2006 i686 i686 i386 GNU/Linux g++ (GCC) 4.0.2 20051125 (Red Hat 4.0.2-8) boost/version.hpp : #define BOOST_VERSION 103200 Stack trace: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 46912529528592 (LWP 27560)] 0x000000000040a2f8 in boost::detail::atomic_exchange_and_add (pw=0x98, dv=-1) at sp_counted_base_gcc_x86.hpp:50 50 ); (gdb) bt #0 0x000000000040a2f8 in boost::detail::atomic_exchange_and_add (pw=0x98, dv=-1) at sp_counted_base_gcc_x86.hpp:50 #1 0x000000000040a46c in boost::detail::sp_counted_base::release (this=0x90) at sp_counted_base_gcc_x86.hpp:143 #2 0x000000000040a4d0 in ~shared_count (this=0x2514218) at shared_count.hpp:159 #3 0x00002aaaaccb849b in ~shared_ptr (this=0x2514210) at shared_ptr.hpp:106 #4 0x00002aaaaccb88e1 in __gnu_cxx::new_allocator<boost::shared_ptr<min_heap> >::destroy (this=0x7fffffc2b410, __p=0x2514210) at new_allocator.h:107 #5 0x00002aaaaccb9f66 in std::vector<boost::shared_ptr<min_heap>, std::allocator<boost::shared_ptr<min_heap> > >::erase ( this=0x7fffffc2b410, __position={_M_current = 0x2514220}) at vector.tcc:115 #6 0x00002aaaaccb7add in label_map::CloseToAlive (this=0x7fffffc2b3e0, p=@0x7fffffc2b1a0) at build/Modules/Marching/label_map.cc:273 #7 0x00002aaaaccb326f in fast_march::march (this=0x7fffffc2b3c0, mask=@0x527d30, gradient=@0x527d10, labeled=@0x527d40) at build/Modules/Marching/fast_march.cc:76 #8 0x00002aaaaccbec64 in marching::run (this=0x527c50, cli=@0x7fffffc2b5e0, options=@0x7fffffc2b5d0, args=@0x7fffffc2b5c0) at build/Modules/Marching/marching.cc:110 #9 0x00000000004074bd in process (args=@0x7fffffc2c460) at build/DDS/dds.cc:259 #10 0x0000000000408ffd in main (argc=2, argv=0x7fffffc2c5a8) at build/DDS/dds.cc:531 Paul Davis

4 7

Re: [Boost-users] on-line documentation, boost 1.34, etc.
by JOAQUIN LOPEZ MU?Z 27 Aug '06

27 Aug '06

Andriy Tylychko ha escrito: > Hi. > > Several question, slightly unrelated: > > 1) To read the last version of documentation I go to > http://www.boost.org/doc/html/index.html. But this list > counts only 15 libraries. Next, going to > http://www.boost.org/doc/html/libraries.html, we see the > same list of 15 libraries with sub-links, but just after > that "Libraries Listed Alphabetically" contains already > much more libraries. Just a bug? The page http://www.boost.org/doc/html/index.html contains those Boost libs which are documented using a tool called BoostBook. Not all Boost libs are documented with BoostBook; the complete list can be obtained at: http://boost.org/libs/libraries.htm which is where you get to from the main Boost page link "Documentation". As to http://www.boost.org/doc/html/libraries.html, this BoostBook-produced page attempts to list every library in Boost, be it documented with BoostBook or not, but in fact it's missing some entries, so you better rely on the link I give above. I don't know if this lack of some entries must e categorized as a bug or as an unmaintained spot to be removed. > > 2) Where can I see documentation of "coming soon" boost > 1.34? Especially documentation for new libraries... I > tried to find it in CVS, but in > http://boost.cvs.sourceforge.net/boost/boost/doc/html/ I > didn't find even "index.html". Using the CVS web browser, go to libs/libraries.htm under the branch RC_1_34_0: http://boost.cvs.sourceforge.net/boost/boost/libs/libraries.htm? view=log&pathrev=RC_1_34_0 There you can find the complete list of all libraries coming into Boost 1.34. If you're interested in new libraries, go to the main index.htm under RC_1_34_0: http://boost.cvs.sourceforge.net/boost/boost/index.htm? view=log&pathrev=RC_1_34_0 Also, Boost Consulting kindly hosts the entire Boost site in its current CVS form at http://boost-consulting.com/boost/ It is the main trunk of the CVS that is published here, which strictly speaking does not have to be the same as RC_1_34_0 (for instance, it may contain material scheduled for 1.35) for in general differences are few. > Why some new libraries > already have nice documentation, but this documentation > cannot be found in logical (?) locations (ASIO e.g., > http://boost.cvs.sourceforge.net/boost/boost/libs/asio/doc/ > is empty)? ASIO has not yet been integrated into Boost. I guess it'll be by Boost 1.35. > > 3) What is the easiest way (better "what is the right > place") to investigate with libraries (and their docs) that > are planned for inclusion to boost 1.34? Hopefully answered above. > > Thank you in advance! > > Best regards, > Andriy Tylychko, > telia(a)vichnavich.com > www.vichnavich.com Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

on-line documentation, boost 1.34, etc.
by Andriy Tylychko (mail.ru) 27 Aug '06

27 Aug '06

Hi. Several question, slightly unrelated: 1) To read the last version of documentation I go to <http://www.boost.org/doc/html/index.html> http://www.boost.org/doc/html/index.html. But this list counts only 15 libraries. Next, going to <http://www.boost.org/doc/html/libraries.html> http://www.boost.org/doc/html/libraries.html, we see the same list of 15 libraries with sub-links, but just after that "Libraries Listed Alphabetically" contains already much more libraries. Just a bug? 2) Where can I see documentation of "coming soon" boost 1.34? Especially documentation for new libraries... I tried to find it in CVS, but in http://boost.cvs.sourceforge.net/boost/boost/doc/html/ I didn't find even "index.html". Why some new libraries already have nice documentation, but this documentation cannot be found in logical (?) locations (ASIO e.g., http://boost.cvs.sourceforge.net/boost/boost/libs/asio/doc/ is empty)? 3) What is the easiest way (better "what is the right place") to investigate with libraries (and their docs) that are planned for inclusion to boost 1.34? Thank you in advance! Best regards, Andriy Tylychko, telia(a)vichnavich.com www.vichnavich.com <http://www.vichnavich.com/>

1 0

Re: [Boost-users] [Boost.Test] How to handle std::valarray<>w/BOOST_CHECK or BOOST_CHECK_EQUAL
by Marc Viala 26 Aug '06

26 Aug '06

After few days of vacation, I've got your reply... Thanks for your response... Marc Viala ________________________________ De : boost-users-bounces(a)lists.boost.org [mailto:boost-users-bounces@lists.boost.org] De la part de Gennadiy Rozental Envoyé : vendredi 18 août 2006 06:17 À : boost-users(a)lists.boost.org Objet : Re: [Boost-users] [Boost.Test] How to handle std::valarray<>w/BOOST_CHECK or BOOST_CHECK_EQUAL operator==( std::valarray<double> const&, std::valarray<double> const& ) returns std::valarray<bool> which is not bool convertible value You will either have to use by element comparison or write your own predicate that compare the valarrays BOOS_CHECK_PREDICATE( my_valarray_comp, (v1)(v2) ); Gennadiy "Marc Viala" <mviala(a)acticm.com> wrote in message news:D0D608FD34E14C4BA93A30AC162651E11F3B97@SERVEUR2003.acticm.com... Hello, I am using the Boost.Test framework, but I not able to use std::valarray<> with BOOST_CHECK or BOOST_CHECK_EQUAL macro. For example: <\code> static void print_valarray(std::ostream& os, std::valarray<double> const& v) { // TODO } namespace std { std::ostream& operator<< (std::ostream& os, std::valarray<double> const& v) { print_valarray(os, v) ; return os ; } } ; std::valarray<double> v(10) ; BOOST_CHECK_EQUAL(v, v); <\code> Failed with the following compilation error: c:\Dev\MViala\ADV\Library\boost-1_33_1\boost\test\predicate_result.hpp(51): error C2664: 'boost::test_tools::predicate_result::readonly_property57::readonly_property57(const boost::test_tools::predicate_result::readonly_property57::write_param_t)' : impossible de convertir le paramètre 1 de 'std::_Boolarray' en 'const boost::test_tools::predicate_result::readonly_property57::write_param_t' Configuration: Platform: Win32 Compiler: Microsoft Visual C++ version 7.1 STL : Dinkumware standard library version 313 Boost : 1.33.1 Any help will be appreciated... Marc Viala ________________________________ _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0