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

Re: [Boost-users] [Serialization / 1.58] wrong number of entries in std::vector<boost::tuple<double, double, double> >
by Rüdiger Berlich 21 Apr '15

21 Apr '15

Hi Robert, I have submitted trac item 11214 and attached the test case. The trac web interface somehow froze for me upon submission (Safari / MacOS), and I apparently have pressed the submit button more than once, trying to submit the track item. So it appears as if more than one ticket has been created (11215 - 11218), which I do not seem to be able to delete. Please ignore these -- apologies. Best Regards, Beet > > ouch! - make a trac item for this! > > Robert Ramey > > > > -- > View this message in context: http://boost.2283326.n4.nabble.com/Serialization-1-58-wrong-number-of-entri… > Sent from the Boost - Users mailing list archive at Nabble.com. > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users >

1 0

Web doc 1.58 Categorized error
by Larry 20 Apr '15

20 Apr '15

I tried to look at the 1.58 doc on the website and clicking on Categorized gave me under the headings By Category Unknown category: Data structures Apparently missing something. “All”, “Standard Proposals” etc seem to work. Larry

2 1

[Serialization / 1.58] wrong number of entries in std::vector<boost::tuple<double, double, double> >
by Rüdiger Berlich 20 Apr '15

20 Apr '15

Hi, I’ve just installed Boost 1.58 and ran into the following problem: I have a class with a std::vector<boost::tuple<double, double, double> >, that is supposed to always have at least one entry, but may have more. Hence, in the default constructor, I initialize the std::vector with one entry. The class is also serializable. Up until Boost 1.57, a de-serialized object always had the correct number of entries in the vector. As of 1.58, I am getting one entry too much, which probably means that Boost.Serialization simply attaches entries to the vector of a default-constructed class, but doesn’t clear it first. This happens in C++11-Mode, both on Ubuntu 14.10 (gcc 4.9.1) as well as on MacOS X Yosemite . It DOES NOT happen with a std::vector<double> . Below is a full test case that replicates the problem in a simplified environment. For Boost 1.57 the program returns: t_vec.size() = 1 t_vec2.size() = 1 For Boost 1.58 the answer is t_vec.size() = 1 t_vec2.size() = 2 Best Regards, Beet /******************************************************/ #include <boost/archive/xml_oarchive.hpp> #include <boost/archive/xml_iarchive.hpp> #include <boost/serialization/nvp.hpp> #include <boost/serialization/vector.hpp> #include <boost/tuple/tuple.hpp> #include <iostream> #include <vector> #include <sstream> namespace boost { namespace serialization { template<typename archive, typename T0, typename T1, typename T2> void serialize(archive & ar, boost::tuple<T0, T1, T2> & tpl, unsigned int) { using namespace boost; using boost::serialization::make_nvp; ar & make_nvp("tpl_0", boost::get<0>(tpl)) & make_nvp("tpl_1", boost::get<1>(tpl)) & make_nvp("tpl_2", boost::get<2>(tpl)); } } /* namespace serialization */ } /* namespace boost */ int main() { std::vector<boost::tuple<double, double, double> > t_vec, t_vec2(1); std::ostringstream oss; t_vec.push_back(boost::tuple<double, double, double>(1.,2.,3.)); std::cout << "t_vec.size() = " << t_vec.size() << std::endl; // save data to archive { boost::archive::xml_oarchive oa(oss); // write class instance to archive oa & BOOST_SERIALIZATION_NVP(t_vec); // archive and stream closed when destructors are called // Data is now in oss } // load data from archive { std::istringstream iss(oss.str()); boost::archive::xml_iarchive ia(iss); // read class state from archive ia & BOOST_SERIALIZATION_NVP(t_vec2); // archive and stream closed when destructors are called } std::cout << "t_vec2.size() = " << t_vec2.size() << std::endl; }

2 1

Compile errors in pointer_traits.hpp after upgrade to 1_58_0
by James Walker 20 Apr '15

20 Apr '15

After switching from Boost 1_57_0 to 1_58_0, I get various compile errors in pointer_traits.hpp, where it uses the macro BOOST_INTRUSIVE_HAS_STATIC_MEMBER_FUNC_SIGNATURE: warning: declaration does not declare anything error: use of undeclared identifier 'check' error: 'U' does not refer to a value This is with Xcode 4.6.3 and the Apple LLVM 4.2 compiler.

2 2

Boost Spirit Karma - convert character to hex representation
by Ernest Zaslavsky 20 Apr '15

20 Apr '15

There is karma::hex formatter and I need somehow to add zero padding to get “0a” instead of just “a”. in addition it would be lovely to have some king of control over hex letter case. It sounds like a policies for real or Boolean formatters but I didn’t find one for hex. Is it possible to achieve the above without policy? [Read More]<http://feeds.feedburner.com/~r/sizmek-blog/~6/1> [http://www.sizmek.com/Sizmek.png]<http://www.sizmek.com/>

2 4

Re: [Boost-users] Boost 1.58.0 has been released
by Florent Guiliani 20 Apr '15

20 Apr '15

On 4/18/15 6:00 PM, boost-users-request(a)lists.boost.org wrote: > On Fri, Apr 17, 2015 at 8:59 PM, Tom Kent<lists(a)teeks99.com> wrote: >> > >> >On Fri, Apr 17, 2015 at 3:58 PM, Marshall Clow<mclow.lists(a)gmail.com> >> >wrote: >>> >> >>> >>Release 1.58.0 of the Boost C++ Libraries is now available. > You sure about that? > Did you forget to push the release tag on Github? https://github.com/boostorg/boost/releases The release tag boost-1.58.0 is missing on Github. -- Florent

1 0

Compile error with boost::factory after upgrade to 1.58.0
by Bitar Fadi 18 Apr '15

18 Apr '15

Hi, I installed Boost 1.58.0 today, having been using 1.57.0 previously, and noticed that a part of my code that uses boost::factory doesn't compile anymore. Here's briefly what I'm doing, followed by the error message I'm getting: typedef boost::function<Apollo::ReportGenerator*(Apollo::ApolloBaseModel*)> reportFactory; struct reportListing { std::string displayName; reportFactory factory; reportListing(std::string name, reportFactory f) : displayName(name), factory(f) { } }; std::vector<reportListing> reportFactories; reportFactories.push_back(reportListing("Scenario Analyzer", boost::factory<Apollo::ScenarioAnalyzer*>())); // Apollo::ReportGenerator being the base class from which Apollo::ScenarioAnalyzer is derived ... The constructor for ScenarioAnalyzer is: ScenarioAnalyzer(Apollo::ApolloBaseModel* model) This fails to compile with the following error (on Windows 7 using Visual C++ 12): error C2664: 'Apollo::ScenarioAnalyzer *boost::factory<Pointer,void,factory_alloc_for_pointee_and_deleter>::operator ()(void) const' : cannot convert argument 1 from 'Apollo::ApolloBaseModel *' to 'Apollo::ApolloBaseModel *&' I'm just wondering if that is caused by an intentional change or not, because according to the change log to boost::factory no significant changes with implications to backward compatibility have been made. Also, I'm not sure I know how to get rid of this error. Thanks for the help! /Fadi ________________________________ Fadi Bitar Modeling and simulation specialist Energy Markets Telephone direct +46 (0)8 695 64 05 Mobile +46 725 40 64 05 fadi.bitar(a)sweco.se<mailto:fadi.bitar@sweco.se> Sweco Energuide AB Gjörwellsgatan 22 P.O. Box 34044 SE-100 26 Stockholm Telephone +46 8 695 60 00 www.sweco.se<http://www.sweco.se/> [cid:image001.jpg@01CECF3E.855DC4C0] Please consider the environment before printing this e-mail.

1 0

Boost 1.58.0 has been released
by Marshall Clow 18 Apr '15

18 Apr '15

Release 1.58.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. This release contains two new libraries and numerous enhancements and bug fixes for existing libraries. New Libraries * Endian: Types and conversion functions for correct byte ordering and more regardless of processor endianness. * Sort: Includes spreadsort, a general-case hybrid radix sort that is faster than O(n*log(n)) For details, including download links, see http://www.boost.org/users/news/version_1.58.0 You can also download directly from SourceForge: http://sourceforge.net/projects/boost/files/boost/1.58.0/ To install this release on your system, see http://www.boost.org/doc/libs/release/more/getting_started/index.html Thanks, --The Boost release team Vladimir Prus Rene Rivera Marshall Clow Eric Niebler Daniel James Beman Dawes

3 2

How to suppress warnings from boost headers
by avib369 . 17 Apr '15

17 Apr '15

Is there any way using boost to suppress warning messages issued from the boost headers ? Is there a way to replace -I with -isystem ? Ta, Avi

1 0

multiprecision -- eigen matrices using dynamically allocated variable-precision mpfr_float
by Daniel Brake 17 Apr '15

17 Apr '15

I'd like to use the variable-precision mpfr_float type offered by the Boost.Multiprecision library, with the templated Eigen linear algebra library. I observe that if I make an identity matrix created with dynamically-allocated variable-precision mpfr_floats, and multiply it against itself, every other row is populated with nan's. Here is some code: int main(){ int size = 9; typedef boost::multiprecision::mpfr_float_backend<0, boost::multiprecision::allocate_dynamic> mybackend; typedef boost::multiprecision::number<mybackend, boost::multiprecision::et_on> mynumtype; typedef Eigen::Matrix<mynumtype, Eigen::Dynamic, Eigen::Dynamic> mp_matrix; mp_matrix A = mp_matrix::Identity(size, size); mp_matrix B = A*A; std::cout << B << std::endl; return 0; } output: 1 0 0 0 0 0 0 0 0 nan nan nan nan nan nan nan nan nan 0 0 1 0 0 0 0 0 0 nan nan nan nan nan nan nan nan nan 0 0 0 0 1 0 0 0 0 nan nan nan nan nan nan nan nan nan 0 0 0 0 0 0 1 0 0 nan nan nan nan nan nan nan nan nan nan nan nan nan nan nan nan nan nan I have been able to pin it down to the allocate_dynamic switch; if I select allocate_stack, the product computes correctly; allocate_dynamic reliably generates nans. Fixed-precision numbers work just fine, and expression templates on/off make no difference. I'd like to use the dynamic allocation, as I expect to use thousands of digits at times. I am using clang++, with c++11, on OSX, Boost 1.57.0, Eigen 3.2.4. Same behaviour in 1.56 / 3.2.3. It seems like maybe an offset issue, but I just can't get there by myself. I've also played with defining the NumTraits in Eigen various ways, but nothing affects the nan behaviour. Does anyone have any ideas? Daniel Brake Postdoctoral Research Scholar University of Notre Dame

2 5