- Boost-users - lists.boost.org

[Config] Reusing results of platform/compiler detection
by joel falcou 23 Aug '08

23 Aug '08

I've looked at the inner implementation of the config components but I didn't find any way to get a simple preprocessor indicating which compiler/platform have been detected. Basiaclly, my goal is to use boost comprehensive detection features to select my own platform/compiler code selection through #ifdef. I tried using Preprocessor magic over the BOOST_PLATFORM string but not to avail. Is there a way to do such a thing or can we request for a #define BOOST_DETECTED_XXX_PLATFORM/COMPILER definition ?

1 0

boost::serialization of a template class
by Takeo 23 Aug '08

23 Aug '08

Hello, I have a base class: class base {...}; and a derived class: class derived : public base {...}; and a template class: template <class T> class ElementList { vector<T*>* m_Elements; ... friend class boost::serialization::access; template<class Archive> inline void serialize(Archive & ar, const unsigned int version) { ar & BOOST_SERIALIZATION_NVP(m_Elements); } } Now i create a class: class myclass : public ElementList<base> { friend class boost::serialization::access; template<class Archive> inline void serialize(Archive & ar, const unsigned int version) { ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(ElementList); } } I want to use boost::serialization on myclass I create somwhere in my program several "derived" elements (which are serialized at this point) After, I put them in the m_Elements vector of myclass (hérited from ElementList<base>). So, the "derived" are stored as "base" elements and the problem is that they are serialized as "base" elements and not "derived" elements. Have you got an idea of how I can solve this issue? Thanks by Advance Emmanuel -- View this message in context: http://www.nabble.com/boost%3A%3Aserialization-of-a-template-class-tp191093… Sent from the Boost - Users mailing list archive at Nabble.com.

2 1

How to build specified type of library with bjam?
by Bill David 23 Aug '08

23 Aug '08

1.I have checked the Jamroot.jam file, it seems we can specify a build-type of minimal or complete. e.g. bjam --toolset=msvc-9.0 --with-regex --build-type=complete stage But it can not meet my requirement. For example, I just want to build debug release <threading>multi <link>static. How could I specify it? 2.it seems we can specify link/runtime-link options, what's the difference between link static and runtime-link static? Does libboost_regex-vc90-mt-gd-1_35.lib means it's a multi-threading debug version of static link edition of regex library? But how about libboost_date_time-vc90-mt-sgd-1_35.lib? What does the -sgd mean? What's the naming convention?

2 1

Does Program Options need pre-building?
by Scott Morgan 23 Aug '08

23 Aug '08

The Program Options lib is listed in the documentation as header only, but I'm getting error messages when attempting to build against it. In particular it's complaining about not having 'libboost_program_options-vc71-sgd-1_36.lib' Scott

3 3

Which library for saving numerical output?
by e r 23 Aug '08

23 Aug '08

Hi all, A while ago I thought I had seen a library whose purpose is to save numerical output (say for plotting graphs using a separate software). Unfortunately I didnt bookmark it and after browsing a few times the boost and vault contents can't find it. Anyone knows what I'm talking about? Thanks!.

1 0

dereference problems with iterator_facade
by e r 23 Aug '08

23 Aug '08

hello, i have a build error when i try to use an iterator derived from iterator_facade<Iter> with Iter an iterator over a const Range. It's the const that causes the error. See the *.hpp below and an example. any other suggestion to improve the *hpp also appreciated. thanks! /////////////////////////////////////////////////////////////////////////////// // boost::skip_one_step_iterator.hpp // // Copyright 2008 Erwann Rogard. Distributed under the Boost // Software License, Version 1.0. (See accompanying file // LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) #ifndef BOOST_ITERATOR_SKIP_ONE_STEP_ITERATOR_HPP_ER200808 #define BOOST_ITERATOR_SKIP_ONE_STEP_ITERATOR_HPP_ER200808 #include <iterator> #include <stdexcept> #include <boost/iterator/iterator_facade.hpp> #include <boost/iterator/iterator_traits.hpp> #include <boost/range.hpp> #include <boost/assert.hpp> #include <boost/type_traits.hpp> namespace boost{ namespace{ template<typename BaseIter,typename Derived> struct super{ typedef iterator_facade< Derived, typename iterator_value<BaseIter>::type, typename iterator_category<BaseIter>::type> type; }; } template<typename BaseIter> class skip_one_step_iterator : public super<BaseIter,skip_one_step_iterator<BaseIter> >::type { typedef iterator_range<BaseIter> iterator_range_type; typedef typename super<BaseIter,skip_one_step_iterator>::type super_type; public: typedef typename super_type::difference_type difference_type; typedef typename super_type::reference reference; skip_one_step_iterator(){} explicit skip_one_step_iterator( BaseIter i, BaseIter skip ) :base_iter(i),skip_(skip){ if(base_is_skip()){ throw std::runtime_error( "skip_one_step_iterator: base_is_skip at construction" ); } } private: friend class boost::iterator_core_access; void increment() { advance((difference_type)(1)); } difference_type distance_to(skip_one_step_iterator const& other) const{ difference_type d = std::distance(this->base_iter,other.base_iter); difference_type dist_this = std::distance(this->base_iter,skip_); difference_type dist_other = std::distance(other.base_iter,skip_); bool same_sign = ((dist_this<0) && (dist_other<0)) || ((dist_this>0) && (dist_other>0)); if(!same_sign){ if(d<(difference_type)(0)){ d+=(difference_type)(1); }else{ d-=(difference_type)(1); } } return d; } bool equal(skip_one_step_iterator const& other) const { return this->base_iter == other.base_iter; } reference dereference() const { return *base_iter; } void advance(difference_type n) { std::advance(this->base_iter,1); if(base_is_skip()){ std::advance(this->base_iter,1); } } bool base_is_skip()const{ return ((this->base_iter)==(this->skip_)); } BaseIter base_iter; BaseIter skip_; }; template<typename Iter> skip_one_step_iterator<Iter> make_skip_one_step_begin_iterator(Iter b,Iter skip){ Iter new_b = b; if(new_b == skip){ std::advance(new_b,1); } return skip_one_step_iterator<Iter>(new_b,skip); }; template<typename Iter> skip_one_step_iterator<Iter> make_skip_one_step_end_iterator(Iter e,Iter skip){ // constructor below will throw if skip == e return skip_one_step_iterator<Iter>(e,skip); }; } #endif #include <iostream> #include <vector> #include <iterator> #include <boost/range.hpp> #include <boost/assign/std/vector.hpp> #include <boost/iterator/skip_one_step_iterator.hpp> #include <libs/iterator/example/skip_one_step_iterator.h> template<typename R> void func(const R& range,std::size_t i){ //void func(R& range,std::size_t i)//works fine //typedef R range_type;//works fine typedef const R range_type; typedef typename boost::range_iterator<range_type>::type iter_type; typedef boost::skip_one_step_iterator<iter_type> skipr_iter_type; iter_type b = boost::begin(range); iter_type e = boost::end(range); iter_type skip = b; std::advance(skip,i); skipr_iter_type sb = boost::make_skip_one_step_begin_iterator(b,skip); skipr_iter_type se = boost::make_skip_one_step_end_iterator(e,skip); copy( sb, se, std::ostream_iterator<double>(std::cout<<" "," ") ); std::cout << std::endl; }; void example_skip_one_step_iterator(){ using namespace boost; typedef std::vector<double> vector_type; typedef vector_type::size_type size_type; typedef range_iterator<vector_type>::type iter_type; typedef skip_one_step_iterator<iter_type> skipr_iter_type; vector_type vec; { using namespace boost::assign; vec += 0.0, 1.0, 2.0, 3.0, 4.0, 5.0, 6.0, 7.0, 8.0, 9.0; } //invalid initialization of reference of type ‘double&’ from expression of type ‘const double’| //this error disappears if range_type replaced by R in definition of func for(size_type i = 1; i < size(vec); i++){ std::cout << "i=" << i << std::endl; func(vec,i); } };

2 2

serialization of bitsets
by McKay, Steve F. 23 Aug '08

23 Aug '08

I submitted code to serialize std::bitsets in 2006 (Boost version 1.33.1). The code enabled tight packing (1 true/false saved as 1 bit) not otherwise available in Boost.Serialization. Robert seemed to be busy at the time (isn't he always :) ), so my code did not get into Boost.Serialization. I have updated to Boost version 1.35.0, so I needed to update my add-on code. I am prepared to submit my revised code to serialize std::bitsets, if anyone is interested. Steve F. McKay Social Security Administration Room 760 Altmeyer 6401 Security Boulevard Baltimore, Maryland 21235 (410)965-3014

2 1

Re: [Boost-users] boost webclient
by Jim Bell 22 Aug '08

22 Aug '08

lakers fan wrote: > Hello, Does anyone know whether there is a class for webclient that > sends data to or receive data from a URL??. You may want to look into curl. http://curl.haxx.se

1 0

Re: [Boost-users] [function] [stlport] typeinfo in stlport 5.1.5
by Gulevich Vasili Victorovich 22 Aug '08

22 Aug '08

On Sat, Aug 23, 2008 at 1:46 AM, Peter Dimov <pdimov(a)pdimov.com> wrote: >> Is there an appropriate way to tell BOOST or stlport where type_info is? > The correct macro to test is BOOST_NO_STD_TYPEINFO: > I don't know whether it's defined properly on your configuration; can you > check? Modification: ---------function_base.hpp--------- #ifdef BOOST_NO_STD_TYPEINFO #warning BOOST_NO_STD_TYPEINFO defined #endif #ifdef _STLP_INTERNAL_TYPEINFO #warning _STLP_INTERNAL_TYPEINFO defined #endif ---------function_base.hpp--------- gives: function_base.hpp:48:2: warning: #warning _STLP_INTERNAL_TYPEINFO defined meaning BOOST_NO_STD_TYPEINFO is undefined there. _STLP_INTERNAL_TYPEINFO is used in file stlport/typeinfo and means that stlport don't override system (mingw's) typeinfo. Mingw defines typeinfo inside std namespace. Replacing BOOST_NO_EXCEPTION_STD_NAMESPACE check in function_base.hpp with BOOST_NO_STD_TYPEINFO one does the trick. BTW, the only files in boost distribution that contain BOOST_NO_STD_TYPEINFO substring are boost/detail/sp_typeinfo.hpp, docs and tests. Is that ok? -- Гулевич Василий

1 0

[function] [stlport] typeinfo in stlport 5.1.5
by Gulevich Vasili Victorovich 22 Aug '08

22 Aug '08

Hello. I'm using stlport-5.1.5 + mingw32 and trying to compile thread library from boost-1.36. The following error appears: --------Compiler output-------- ./boost/function/function_base.hpp:In static member function `static void boost::detail::function::reference_manager<F>::get(const boost::detail::function::function_buffer&, boost::detail::function::function_buffer&, boost::detail::function::functor_manager_operation_type)': ./boost/function/function_base.hpp:224: error: expected initializer before '&' token --------Compiler output-------- The context in function_base.hpp: 224: const BOOST_FUNCTION_STD_NS::type_info& check_type = 225: *static_cast<const BOOST_FUNCTION_STD_NS::type_info*>(out_buffer.const_obj_ptr); BOOST_FUNCTION_STD_NS is defined as empty because of BOOST_NO_EXCEPTION_STD_NAMESPACE in the same file: function_base.hpp on line 41. BOOST_NO_EXCEPTION_STD_NAMESPACE is found in: --------boost/config/stdlib/stlport.hpp-------- // If STLport is using it's own namespace, and the real names are in // the global namespace, then we duplicate STLport's using declarations // (by defining BOOST_NO_STDC_NAMESPACE), we do this because STLport doesn't // necessarily import all the names we need into namespace std:: // # if (defined(__STL_IMPORT_VENDOR_CSTD) \ || defined(__STL_USE_OWN_NAMESPACE) \ || defined(_STLP_IMPORT_VENDOR_CSTD) \ || defined(_STLP_USE_OWN_NAMESPACE)) \ && (defined(__STL_VENDOR_GLOBAL_CSTD) || defined (_STLP_VENDOR_GLOBAL_CSTD)) # define BOOST_NO_STDC_NAMESPACE # define BOOST_NO_EXCEPTION_STD_NAMESPACE # endif ------boost/config/stdlib/stlport.hpp------ (_STLP_USE_OWN_NAMESPACE and vendor flags is defined in this case) Replacing function_base.hpp:41 with: ----- #if defined(BOOST_NO_EXCEPTION_STD_NAMESPACE) && !defined(_STLP_USE_OWN_NAMESPACE) ----- allows compilation of thread library. Is there an appropriate way to tell BOOST or stlport where type_info is? -- Sincerely, Basilevs

2 1