July 2009 - Boost - lists.preview.boost.org

FW: [uuid] changes to fix warnings from the linker
by christian.leutloff＠web.de 22 Jul '09

22 Jul '09

Hi, thank you for the boost.uuid lib! Could you please add some more "inline"s to some of the methods to avoid warnings from the VS2008 compiler? I'm using the uuid implementation from uuid_alt_v13_pod.zip downloaded from http://www.boostpro.com/vault/index.php. This is one of the warnings: warning LNK4006: "bool __cdecl boost::uuids::operator<(class boost::uuids::uuid const &,class boost::uuids::uuid const &)" (??Muuids@boost@@YA_NABVuuid@01@0@Z) already defined in xxx.obj; second definition Here is the patch to fix the warnings: Index: boost/uuid/uuid.hpp =================================================================== --- boost/uuid/uuid.hpp (revision 65) +++ boost/uuid/uuid.hpp (working copy) @@ -152,28 +152,28 @@ x.swap(y); } -bool operator==(uuid const& lhs, uuid const& rhs) /* throw() */ +inline bool operator==(uuid const& lhs, uuid const& rhs) /* throw() */ { return (lhs.data_ == rhs.data_); } -bool operator!=(uuid const& lhs, uuid const& rhs) /* throw() */ +inline bool operator!=(uuid const& lhs, uuid const& rhs) /* throw() */ { return !(lhs == rhs); } -bool operator<(uuid const& lhs, uuid const& rhs) /* throw() */ +inline bool operator<(uuid const& lhs, uuid const& rhs) /* throw() */ { return (lhs.data_ < rhs.data_); } -bool operator>(uuid const& lhs, uuid const& rhs) /* throw() */ +inline bool operator>(uuid const& lhs, uuid const& rhs) /* throw() */ { return rhs < lhs; } -bool operator<=(uuid const& lhs, uuid const& rhs) /* throw() */ +inline bool operator<=(uuid const& lhs, uuid const& rhs) /* throw() */ { return !(lhs > rhs); } -bool operator>=(uuid const& lhs, uuid const& rhs) /* throw() */ +inline bool operator>=(uuid const& lhs, uuid const& rhs) /* throw() */ { return !(lhs < rhs); } @@ -191,7 +191,7 @@ } // As named in RFC 4122, 4.1.7 -uuid nil() { +inline uuid nil() { uuid u = uuid(); return u; } Index: boost/uuid/uuid_io.hpp =================================================================== --- boost/uuid/uuid_io.hpp (revision 65) +++ boost/uuid/uuid_io.hpp (working copy) @@ -22,7 +22,7 @@ namespace detail { -int get_showbraces_index() +static int get_showbraces_index() { static int index = std::ios_base::xalloc(); return index; Index: boost/uuid/uuid_namespaces.hpp =================================================================== --- boost/uuid/uuid_namespaces.hpp (revision 65) +++ boost/uuid/uuid_namespaces.hpp (working copy) @@ -42,7 +42,7 @@ namespace namespaces { /* Name string is a fully-qualified domain name */ -uuid dns() { +inline uuid dns() { uuid u = { /* 6ba7b810-9dad-11d1-80b4-00c04fd430c8 */ 0x6b, 0xa7, 0xb8, 0x10, 0x9d, 0xad, @@ -53,7 +53,7 @@ } /* Name string is a URL */ -uuid url() { +inline uuid url() { uuid u = { /* 6ba7b811-9dad-11d1-80b4-00c04fd430c8 */ 0x6b, 0xa7, 0xb8, 0x11, 0x9d, 0xad, @@ -64,7 +64,7 @@ } /* Name string is an ISO OID */ -uuid oid() { +inline uuid oid() { uuid u = { /* 6ba7b812-9dad-11d1-80b4-00c04fd430c8 */ 0x6b, 0xa7, 0xb8, 0x12, 0x9d, 0xad, @@ -75,7 +75,7 @@ } /* Name string is an X.500 DN (in DER or a text output format) */ -uuid x500() { +inline uuid x500() { uuid u = { /* 6ba7b814-9dad-11d1-80b4-00c04fd430c8 */ 0x6b, 0xa7, 0xb8, 0x14, 0x9d, 0xad, Bye Christian -- Christian Leutloff, Aachen, Germany ______________________________________________________ GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT! Jetzt freischalten unter http://movieflat.web.de

1 0

[1.40] release schedule?
by joaquin＠tid.es 22 Jul '09

22 Jul '09

Hi, The Google Calendar schedule for Boost 1.40 (http://www.boost.org/development/index.html ) says we're one day past the beta delivery date. How does this schedule still apply? Is it OK to make doc changes to the release branch? Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

[Date_Time] -proposal to overload tz_database::load_from_file method
by Slawomir Dors 21 Jul '09

21 Jul '09

Hi ! I'm using the Date_Time library on Windows. The "tz_database" has only one method to populate it with the data from "date_time_zonespec.csv" file. It is "load_from_file" method which takes a filename in std::string. I wonder if it's possible to overload that method so it could be more generic (and much more useful). It could take for example a reference to std::istream object. The idea is to avoid to save the data in a .csv file on a disk. I could then put the data in the resources of an .exe or .dll file, create some stream object derived from std::istream and load into the "tz_database" object. The second limitation of the existing version of "load_from_file" is that I can't use unicode string to provide the filename. What the Developers think about such small addition ? Cheers, Slawomir Dors

1 0

_WIN32_WINNT in thread\src\win32\thread.cpp and filesystem\src\operations.cpp
by James Mansion 21 Jul '09

21 Jul '09

Why does win32\thread.cpp unconditionally define _WIN32_WINNT and WINVER? That's a bit rude, especially when I go to lengths to set them properly in a file I pass as BOOST_USER_CONFIG. :-( This also applies in filesystem\src\operations.cpp: in that case it does check that _WIN32_WINNT isn't defined already, but there has been no inclusion of config.h so BOOST_USER+CONFIG has not been processed yet. I would have though that in both cases the correct response is to remove these explicit settings and just: #include <boost/config.h> James (Using 1.39.0 on Vista, BTW - and setting _WIN32_WINNT by detection in my waf script)

2 1

[smart_ptr] shared_ptr template type
by Frank Mori Hess 21 Jul '09

21 Jul '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I wonder if it might be better/possible to have a shared_ptr<T> that didn't assume its corresponding "raw" pointer type was T* but rather T. For example, what is now a shared_ptr<int> would be specified as a shared_ptr<int*>. The motivation would be to allow support for other classes as the "raw" pointer type. For example, I might want to have a shared_ptr<monitor<T*> > where the monitor<T*> has an operator->() which does automatic locking/unlocking of a mutex before/after forwarding the operator->() to the plain T pointer. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkpWA5YACgkQ5vihyNWuA4UQOwCeI7sjr4/pByXIqRtactVfi8fk MUgAoLmstL+7V5NW+yYNXyDPlVog7VAI =JE48 -----END PGP SIGNATURE-----

8 29

[TypeTraits] Type traits for member pointers?
by Celtic Minstrel 20 Jul '09

20 Jul '09

I recently noticed that the Boost Type Traits library does not include any traits for member pointers apart from identification. For example, there are no "add member pointer" or "remove member pointer" traits, nor a trait to extract the containing type from a member pointer (ie extract Q from T Q::*). And there is no trait for decomposing member function pointers. It would appear that these traits could be added fairly easily; I was able to create them within a few minutes, and verify that they worked (with g++). Is there sufficient reason to add them to the library? For me, completeness seems like reason enough (unless it would be a lot of work). On the other hand, member pointers are, as far as I know, rarely used. So, um... thoughts? Is it a good idea? Should I post my code? --SPCD "Celtic Minstrel"

4 7

Re: [boost] Boost::Serialization Combined XML- and Binary-Serialization
by Daniel Kunz 20 Jul '09

20 Jul '09

Hallo, I found my failure with xml serialization. It works now! Thanks Robert Ramey! Now I just have my problems with binary serialization. Can somebody help me with this? Best regards. Daniel Robert Ramey wrote: >Try replacing >> boost::serialization::binary_object bo = >> boost::serialization::make_binary_object(minute, >with > boost::serialization::binary_object bo = > boost::serialization::make_binary_object(& minute, >Robert Ramey >Daniel Kunz wrote: >> Hello, >> I try to write an function, which can convert data via the >> serialization interface >> XML --> class --> binary AND >> binary --> class --> XML >> I read the documentation and in the mailing lists but I could not >> finish my functions. >> >> I have 2 problems: >> 1) the xml function delivers no xml data in my testfile output >> 2) I cannot add the binary structure to the existing xml-working >> classes >> With the binary serialization I didn't find many informations, but >> that informations I found I can't use with the classes I prepared for >> xml serialization >> Is it possible to combine that 2 serializations >> >> Here is my testing code I worked with so far. The finish >coding is >> similar with that class structure. >> >> The class structure: >> >> -------------------------------------------------------- >> goal.cpp >> -------------------------------------------------------- >> #include <string> >> #include <iostream> >> >> using namespace std; >> >> #include <boost/serialization/base_object.hpp> >> #include <boost/serialization/list.hpp> >> #include <boost/serialization/is_abstract.hpp> >> >> #include <boost/archive/xml_iarchive.hpp> >> #include <boost/archive/xml_oarchive.hpp> >> #include <boost/archive/binary_iarchive.hpp> >> #include <boost/archive/binary_oarchive.hpp> >> #include <boost/serialization/binary_object.hpp> >> namespace serialization >> { >> >> class Goal >> { >> public: >> enum Scored{home=0, visitors=1}; >> Goal(){}; >> Goal(const string _name, int &_minute, bool &_shootout, Scored >> &_scored, bool &_penality); >> ~Goal(){}; >> friend ostream & operator<<(ostream &os, const Goal &_goal); >> private: >> friend class boost::serialization::access; >> template<class Archive> >> void serialize(Archive & ar, const unsigned int version) >> { >> using boost::serialization::make_nvp; >> ar & make_nvp("Name", name); >> ar & make_nvp("Minute", minute); >> ar & make_nvp("Shootout", shootout); >> ar & make_nvp("Scored", scored); >> ar & make_nvp("Penality", penality); >> >> boost::serialization::binary_object bo = >> boost::serialization::make_binary_object(minute, >> sizeof(minute)); >> ar & bo; >> } >> string name; >> int minute; >> bool shootout; >> Scored scored; >> bool penality; >> }; >> } >> >> -------------------------------------------------------- >> stadium.h >> -------------------------------------------------------- >> #include <string> >> #include <iostream> >> >> using namespace std; >> #include <boost/serialization/base_object.hpp> >> #include <boost/serialization/list.hpp> >> #include <boost/serialization/is_abstract.hpp> >> >> #include <boost/archive/xml_iarchive.hpp> >> #include <boost/archive/xml_oarchive.hpp> >> #include <boost/archive/binary_iarchive.hpp> >> #include <boost/archive/binary_oarchive.hpp> >> >> namespace serialization >> { >> >> class Stadium >> { >> private: >> friend class boost::serialization::access; >> template<class Archive> >> void serialize(Archive & ar, const unsigned int version) >> { >> using boost::serialization::make_nvp; >> ar & make_nvp("Name", name); >> ar & make_nvp("City", city); >> ar & make_nvp("Spectators", spectators); >> } >> string name; >> string city; >> int spectators; >> public: >> Stadium(){}; >> Stadium(const string _name, const string _city, int >> &_spectators); friend ostream & operator<<(ostream &os, >> Stadium &_stadium); }; >> } >> >> -------------------------------------------------------- >> match.h >> -------------------------------------------------------- >> #include <list> >> #include <time.h> >> #include <string> >> #include <iostream> >> #include <cstdio> >> >> using namespace std; >> >> #include <boost/serialization/base_object.hpp> >> #include <boost/serialization/list.hpp> >> #include <boost/serialization/is_abstract.hpp> >> >> #include <boost/archive/xml_iarchive.hpp> >> #include <boost/archive/xml_oarchive.hpp> >> #include <boost/archive/binary_iarchive.hpp> >> #include <boost/archive/binary_oarchive.hpp> >> #include <boost/serialization/serialization.hpp> >> >> #include "goal.h" >> #include "stadium.h" >> >> namespace serialization >> { >> >> class Match >> { >> private: >> friend class boost::serialization::access; >> template<class Archive> >> >> void serialize(Archive & ar, const unsigned int version) >> { >> using boost::serialization::make_nvp; >> ar & make_nvp("Home", home); >> ar & make_nvp("Visitors", visitors); >> ar & make_nvp("Kickoff", kickoff); >> ar & make_nvp("Goals", goals); >> ar & make_nvp("Stadium", stadium); >> } >> string home; >> string visitors; >> time_t kickoff; >> typedef list<Goal> lGoals; >> lGoals goals; >> Stadium stadium; >> public: >> Match(){}; >> Match(const string _home, const string _visitors, time_t >> &_kickoff, Goal *_goals, int size, Stadium &_stadium); >> Match& operator = (Match &_match); >> friend ostream & operator<<(ostream &out, Match &_match); >> }; >> } >> >> -------------------------------------------------------- >> xml.cpp >> -------------------------------------------------------- >> #include <boost/archive/xml_iarchive.hpp> >> #include <boost/archive/xml_oarchive.hpp> >> >> #include <iomanip> >> #include <iostream> >> #include <fstream> >> #include <string> >> >> #include "goal.h" >> #include "stadium.h" >> #include "match.h" >> >> #include <boost/serialization/base_object.hpp> >> #include <boost/serialization/utility.hpp> >> #include <boost/serialization/list.hpp> >> #include <boost/serialization/is_abstract.hpp> >> >> using namespace std; >> >> void save_xml(const serialization::Match &m, const string &filename) >> { >> try >> { >> ofstream ofs(filename.c_str()); >> assert(ofs.good()); >> boost::archive::xml_oarchive oa(ofs); >> oa << boost::serialization::make_nvp("Match", m); >> } >> catch(exception &e) >> { >> cout << e.what() << endl; >> } >> } >> >> void restore_xml(serialization::Match &m, const string &filename) >> { >> try >> { >> ifstream ifs(filename.c_str()); >> boost::archive::xml_iarchive ia(ifs); >> ia >> boost::serialization::make_nvp("Match", m); >> } >> catch(exception &e) >> { >> cout << e.what() << endl; >> } >> } >> >> -------------------------------------------------------- >> binary.cpp >> -------------------------------------------------------- >> void save_bin(const serialization::Match &m, const string &filename) >> { >> try >> { >> std::ofstream ofs(filename.c_str()); >> boost::archive::binary_oarchive oa(ofs); >> //oa << m; >> } >> catch(exception &e) >> { >> cout << e.what() << endl; >> } >> } >> >> void restore_bin(serialization::Match &m, const string &filename) >> { >> try >> { >> std::ifstream ifs(filename.c_str()); >> boost::archive::binary_iarchive ia(ifs); >> //ia >> m; >> } >> catch(exception &e) >> { >> cout << e.what() << endl; >> } >> } >> >> >> I hope somone can help me. I don't know what I can do to complete that >> functions. >> >> Best regards >> Daniel

2 2

RFC - MapReduce library is now available in the Vault
by Craig Henderson 19 Jul '09

19 Jul '09

I have uploaded the first public release of my MapReduce library to the Boost Vault (I don't yet have write access to the sandbox). The ZIP file is very small, 38Kb, and can be downloaded here: http://tinyurl.com/boost-mapreduce-zip More general discussion about my implementation of MapReduce and associated Distributed File System is on my blog at http://craighenderson.co.uk/blog/ The library is fully functional on Windows with MSVC8, and compiles cleanly with GCC 3.4.4 on Cygwin (but not tested). I'd appreciate comments from anyone with other platforms/compilers on whether it builds & runs. I'll get the code into the sandbox asap, and would welcome patches to support other platforms. Documentation is included in the zip and provides a tutorial and example application. A full reference document of the classes in the library is not yet included, but I'm working on it. I would very much welcome all comments on the library and suggestions on its design and style. I am keen to progress this to submit for a formal review to become a part of Boost in the near future. Many thanks -- Craig Craig Henderson <http://craighenderson.co.uk/> http://www.craighenderson.co.uk http://www.siteupdatenotification.com

1 0

[array] Custom constructr/destructor
by Kasra 18 Jul '09

18 Jul '09

Hello, I have found an interesting problem regardin using custom allocators/deallocators for an array object. Say for example you want to initialise the array to some values and on destruction you want to do something with these values. This at the memoment is not possible. The solution is to create a new class which inherits from array. template<class T, std::size_t N> class array; template<class T, std::size_t N> class my_array: public array<T,N> { my_array() { ... } ~my_array() { ... } }; Which is not an ideal solution and results in code bloat. However a defenition like bellow: template<class T, std::size_t N, class PredCtor, class PredDtor> class array; Means the same code could be used for custom operations during construction and destruction. Is there any interest in such a change? If so maybe we could propose this for the standard. Yours truly, -- Kasra

2 1

program_options easy_init
by Zachary Turner 18 Jul '09

18 Jul '09

I'm just wondering if there's a specific reason why boost::program_options::options_description_easy_init::operator() takes arguments (const char*, value_semantic, const char*) instead of (const std::string&, value_semantic, const std::string&)? Nothing major, but it's annoying when you want to pass something like str1+str2 as one of the string arguments.

2 1