August 2010 - Boost - lists.preview.boost.org

[1.44] [filesystem] operator +
by Jochen Wilhelmy 23 Aug '10

23 Aug '10

Hi! for boost::filesystem::path I would suggest an operator + that works like the following fs::path("foo") + "bar" -> "foobar" fs::path("foo") + "/bar" -> "foo/bar" fs::path("foo") / "bar" -> "foo/bar" -Jochen

3 2

Re: [boost] [serialization][mpi] mpi library doesn't compile due to serialization problems with 1.44
by Denis Arnaud 23 Aug '10

23 Aug '10

Hello Simon, 2010/8/23 <boost-request(a)lists.boost.org> > I'm trying to build 1.44 on Fedora 13 (gcc 4.4.4) Well, Boost-1.44.0 is available on Fedora 14 RC4 and Rawhide (e.g., http://mirror.fdcservers.net/fedora/development/14/i386/os/Packages/boost-d… ). Nevertheless, thnaks for having reported that compilation issue! Regards Denis

1 0

Bug in boost.atomic (review requested)
by Jorge Lodos Vigil 23 Aug '10

23 Aug '10

Hi The boost.atomic library is a header only library waiting for review (http://lists.boost.org/Archives/boost/2009/12/160195.php) There is a bug in the implementations of platform_atomic_thread_fence (all platforms) where it is not declared inline. This causes linker error when the library is used in different compilation units. Boost.atomic is being used in other libraries waiting for review such as boost.task which do not link for the same reason. Thank you. Best regards Jorge

1 0

[exception] ostringstream like
by fabien 23 Aug '10

23 Aug '10

Hi, I would like to propose an "error_info_sstream" class, allowing to do: Point3D p; int id; boost::filesystem::path path; ... BOOST_THROW_EXCEPTION( exception::Logic() << exception::user( "Foo failed." ) << exception::dev() + "Foo failed at index " + id + " at position " + p + "." << exception::filename( path->filename() ) ); With a declaration, like that: namespace MyProject { namespace exception { typedef ::boost::error_info<struct tag_userMessage,::boost::error_info_sstream> user; typedef ::boost::error_info<struct tag_devMessage,::boost::error_info_sstream> dev; typedef ::boost::errinfo_file_name filename; struct Logic : virtual public ::std::exception, virtual public ::boost::exception {}; } } The idea is to remove such things: BOOST_THROW_EXCEPTION( exception::Logic() << exception::user( "Foo failed." ) << exception::dev( std::string("Foo failed at index ") + boost::lexical_cast<std::string>(id) + " at position [x:" + boost::lexical_cast<std::string>(p.x) + ",y:" + boost::lexical_cast<std::string>(p.y) + ",z:" + boost::lexical_cast<std::string>(p.z) + "]." ) << exception::filename( path->filename() ) ); or std::ostringstream msg; msg << "Foo failed at index " << id << " at position " << p << "."; BOOST_THROW_EXCEPTION( exception::Logic() << exception::user( "Foo failed." ) << exception::dev(msg) << exception::filename( path->filename() ) ); The proposed solution is to have an error_info with an operator+, doing the same thing as an operator<< on an ostringstream. 1) Are you agree with this idea ? 2) Are you agree with this implementation ? I write this without understanding all internal things inside boost::exception. 3) Are you interested to add something like that in boost::exception ? Best regards, Fabien Castan namespace boost { struct error_info_sstream { typedef std::ostringstream value_type; value_type _v; }; inline std::string to_string( const error_info_sstream& x ) { return x._v.str(); } template<class Tag> class error_info<Tag, error_info_sstream>: public exception_detail::error_info_base { public: typedef error_info_sstream T; typedef error_info<Tag,T> This; typedef T value_type; error_info(){} error_info( const This& v ) { _value._v << v._value._v.str(); } template<typename V> error_info( const V& value ) { _value._v << value; } ~error_info() throw() {} template<typename V> This& operator+( const V& v ) { _value._v << v; return *this; } const value_type& value() const { return _value; } value_type& value() { return _value; } private: std::string tag_typeid_name() const { return tag_type_name<Tag>(); } std::string value_as_string() const { return _value._v.str(); } value_type _value; }; }

5 9

[1.44][Serialization] fails to compile on OSX universal
by Jeff Flinn 23 Aug '10

23 Aug '10

Building boost 1.44 on Mac OSX generating universal binaries fails to compile serialization lib, due to static asserts in basic_binary_?archive.hpp's at: BOOST_STATIC_ASSERT(sizeof(tracking_type) == sizeof(char)); It appears that this fails for the ppc architecture. Robert, Any ideas on fixing this? Thanks, Jeff

8 24

[1.44] [filesystem] how to imbue utf-8
by Jochen Wilhelmy 23 Aug '10

23 Aug '10

Hi! With boost::filesystem I'd like to do the following: - use std::string (i.e. 8 bit) with utf-8 - call native functions such as CreateFileW(), or open() on windows, linux and macos the v3 version handles this differently than v2 and maybe the new approach of v3 is indeed better since I can imbue utf-8 and all other libs that I use that use boost::filesystem will magically also use utf-8 which was not possible with the v2 version. But now my questions: How do I imbue utf-8? Maybe a newbee-question but would be nice if it would appear in a tutorial. How do I get a wchar_t* for CreateFileW()? How to I get a utf-8 encodec char* for open() for macos? How to I get a locale-encoded char* for open() for linux? (the locale may be utf-8 but if it is latin-1 then a transcoding has to take place). The generic constructor of fs::path should be made explicit since it makes overloading difficult. Of course constructors for std::basic_string, char*, wchar_t* etc. can be implicit. -Jochen

1 0

[Boost.Locale] Upcoming Boost.Locale version
by Artyom 23 Aug '10

23 Aug '10

Hello, I'd like to tell about some Boost.Locale updates. I did some deep reworking on Boost.Locale internals that made this library more modular and powerful: Localization backends interface: -------------------------------- I had build localization backends interface that allows using non-ICU based localization sources. It it becomes possible to use absolutely same API with different backends. Standard library based localization: ------------------------------------ I created simple localization backend based on standard C++ library localization support that enhances it in many ways and actually allows to use this library without ICU at all makeing it much smaller for cases where no advanced features are required. Of course you do not get advanced ICU features like boundary analysis, non-gregorian calendar support. But still have full support of message formatting and depending on your compiler's standard library you get localized numbers, currency, date-time formatting and parsing, basic collation etc. What is also important you get it in uniform way so you can create "he_IL.UTF-8" locale even using MSVC standard library that does not support UTF-8 and does not support POSIX locale names, this backend knows to translate POSIX locale names to Windows ones and use wide character facets for providing UTF-8 locales that are not given. Good standard library localization support is provided by GCC and Intel compilers under Linux and MSVC under Windows. Meanwhile this version exists in svn under: <https://cppcms.svn.sourceforge.net/svnroot/cppcms/boost_locale/branches/rew…> Other enhancements: ------------------- - Cleanup and simpilification of the locales generation interface - Support of ICU-less builds Hopefully it will be ready for review soon and would repace current version scheduled for review. BTW: Is there anybody who wants to mange the review process. Artyom

2 1

Re : [local_function] any interest in a LocalFunction library?
by Pierre Morcello 23 Aug '10

23 Aug '10

Lorenzo Caminiti wrote : > > Is there interest in a library that implement local > functions for C++? > One year ago, I made a proposition for a boost.breakable. Some people were interested in the library, if I could widen it a little. David Abraham & Vicente Botet expressed interest in a macro local function that would work like scope exist. So I wrote a first implementation. But I have not posted back on this subject, because I was unsure about the macro interface, since a few variations on its interface (ex: passing this or not) could be done. Here I send 2 little examples of my tests. The 'V3' is almost the same as the one you posted. The 'V4' is a try wich uses only 1 macro call. Unfortunately, these 2 use currently __VA_ARGS__, and were only tested on visual 2008. But yes, there is an interest in a local function. Best, Pierre Morcello

3 2

[serialization][mpi] mpi library doesn't compile due to serialization problems with 1.44
by Number Cruncher 23 Aug '10

23 Aug '10

I'm trying to build 1.44 on Fedora 13 (gcc 4.4.4), and get the following compiler error: gcc.compile.c++ bin.v2/libs/mpi/build/gcc-4.4.4/release/link-static/threading-multi/broadcast.o In file included from ./boost/mpi/packed_iarchive.hpp:27, from ./boost/mpi/communicator.hpp:28, from ./boost/mpi/collectives.hpp:22, from ./boost/mpi/collectives_fwd.hpp:20, from ./boost/mpi/collectives/broadcast.hpp:12, from libs/mpi/src/broadcast.cpp:10: ./boost/mpi/detail/binary_buffer_iprimitive.hpp: In member function 'void boost::mpi::binary_buffer_iprimitive::load(T&) [with T = boost::archive::version_type]': ./boost/archive/detail/iserializer.hpp:107: instantiated from 'static void boost::archive::load_access::load_primitive(Archive&, T&) [with Archive = boost::mpi::packed_iarchive, T = boost::archive::version_type]' ./boost/archive/detail/iserializer.hpp:356: instantiated from 'static void boost::archive::detail::load_non_pointer_type<Archive>::load_primitive::invoke(Archive&, T&) [with T = boost::archive::version_type, Archive = boost::mpi::packed_iarchive]' ./boost/archive/detail/iserializer.hpp:433: instantiated from 'static void boost::archive::detail::load_non_pointer_type<Archive>::invoke(Archive&, T&) [with T = boost::archive::version_type, Archive = boost::mpi::packed_iarchive]' ./boost/archive/detail/iserializer.hpp:586: instantiated from 'void boost::archive::load(Archive&, T&) [with Archive = boost::mpi::packed_iarchive, T = boost::archive::version_type]' ./boost/archive/detail/common_iarchive.hpp:66: instantiated from 'void boost::archive::detail::common_iarchive<Archive>::load_override(T&, int) [with T = boost::archive::version_type, Archive = boost::mpi::packed_iarchive]' ./boost/mpi/packed_iarchive.hpp:101: instantiated from 'void boost::mpi::packed_iarchive::load_override(T&, int, mpl_::false_) [with T = boost::archive::version_type]' ./boost/mpi/packed_iarchive.hpp:118: instantiated from 'void boost::mpi::packed_iarchive::load_override(T&, int) [with T = boost::archive::version_type]' ./boost/archive/detail/interface_iarchive.hpp:60: instantiated from 'Archive& boost::archive::detail::interface_iarchive<Archive>::operator>>(T&) [with T = boost::archive::version_type, Archive = boost::mpi::packed_iarchive]' ./boost/archive/detail/common_iarchive.hpp:45: instantiated from 'void boost::archive::detail::common_iarchive<Archive>::vload(boost::archive::version_type&) [with Archive = boost::mpi::packed_iarchive]' libs/mpi/src/broadcast.cpp:151: instantiated from here ./boost/mpi/detail/binary_buffer_iprimitive.hpp:87: error: no matching function for call to 'assertion_failed(mpl_::failed************ boost::serialization::is_bitwise_serializable<boost::archive::version_type>::************)' ./boost/mpi/detail/ The assertion also trips on: boost::serialization::is_bitwise_serializable<boost::archive::object_id_type> boost::serialization::is_bitwise_serializable<boost::archive::class_id_type> boost::serialization::is_bitwise_serializable<boost::archive::class_id_optional_type> boost::serialization::is_bitwise_serializable<boost::archive::tracking_type> Having looked at the source, I see that these types are indeed non-POD classes and I can't find the is_bitwise_serializable trait applied anywhere. Am I missing something? Thanks, Simon H.

2 1

AUTO: Ingo Loehken is out of the office (returning 27.08.2010)
by Ingo Loehken 23 Aug '10

23 Aug '10

I am out of the office until 27.08.2010. Note: This is an automated response to your message "Re: [boost] [local_function] any interest in a LocalFunction library?" sent on 8/23/10 3:01:49 AM. This is the only notification you will receive while this person is away.

1 0