- Boost - lists.preview.boost.org

[1.44] [filesystem] filesystem::path construction problems in version 3
by Adam Badura 24 Aug '10

24 Aug '10

It seems Boost.Filesystem v. 3 in Boost 1.44 has some problems in filesystem::path construction. Firstly it does not work well when a C array is given to the constructor. Problem is illustrated with following code: ---------------------------------------- #include <cstdio> #include <string> #define BOOST_FILESYSTEM_VERSION 3 #include <boost/filesystem.hpp> int main( int argc, char* argv[] ) { char big[100]; char* small = "d:/foo/"; boost::filesystem::path pathFromSmall( small ); pathFromSmall /= "bar.txt"; std::printf( "%s\n", pathFromSmall.string< std::string >().c_str() ); std::strcpy( big, small ); boost::filesystem::path pathFromBig( big ); pathFromBig /= "bar.txt"; std::printf( "%s\n", pathFromBig.string< std::string >().c_str() ); return 0; } ---------------------------------------- Secondly filesystem::path accepts to much in its constructors. Currently it accepts even shared_ptr. This is illustrated by following code which was fine in 1.43 while in 1.44 it results in compilation error (VS 2010) of ambiguous call to "fun". ---------------------------------------- #define BOOST_FILESYSTEM_VERSION 3 #include <boost/filesystem.hpp> #include <boost/smart_ptr.hpp> class Base { }; class Derived : public Base { }; void fun( const boost::filesystem::path& _path ) { } void fun( const boost::shared_ptr< Base >& _pBase ) { } int main( int argc, char* argv[] ) { boost::shared_ptr< Derived > pDerived( new Derived() ); fun( pDerived ); return 0; } ---------------------------------------- Adam Badura

2 2

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

24 Aug '10

> I can implement Boost.LocalFunction macros, which are > similar to your 'V3' macros, in pure C++ ISO standard (no __VA_ARGS__). I > will study your code more. __VA_ARGS__ is iso C99 (but ok not c++). The point is only that boost prefers iso C90, since it is much more widely supported. I have some implementation question on your proposition : how will you detect that 'this' exist, that you are not inside a static function ? If you can do such a thing I am interested to know how you do it (because I did not find out myself) ? My example is trickier than it looks, since it uses the defect 45 of the iso to allow private access for nested classes. This quite unfortunate since the defect 45 is only of statut DR instead of TC1 (which is required for being part of the standard). Best regards, Pierre Morcello

2 2

Re: [boost] [1.44] [filesystem] operator +
by Jochen Wilhelmy 24 Aug '10

24 Aug '10

> > 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" > > >What's the situation in which you'd like to use that operator? Sometimes I have file formats that have two parts, e.g. a description xml file and a data file. then I'd like to do name + ".xml" and name + ".dat" if name is a fs::path -Jochen

4 3

Re: [boost] [Boost.Locale] Upcoming Boost.Locale version
by Artyom 24 Aug '10

24 Aug '10

> I like to think in terms of [serialized] objects and not strings. > Besides having to internationalize images sometimes I need to do the > same to arrays of strings or any type of object. > In the use case of array of strings, I may in English > have a selection or radii > ["25 miles", "50 miles", "75 miles" "100 miles", "150 miles", "200 miles"]. > However in a different language I may have ["50km", "100km", "150km", >"250km"]. > Because the unit is different I may more or fewer items in the array. > The items in the array may not even be strings but a unit object that has both > >runtime scaler and runtime unit. > There is a general approach to solve such issues, even if this is not supported by the library. You use following: double factor = atof(dgettext("Distance conversion factor for km","1.0").c_str()); int local_distance = static_cast<int>(metric_distance * factor); std::cout <<format(translate("{1,num} kms","{1,num} kms",local_distance)) % local_distance That's it. You just define some translation string and use it as localization reasource. And tanslator translates this factor to ~1.6 and kms to miles according to locale. > So using ICU how would I store and retrieve an array of objects using boost >serialization into one field. For serialization you should always use locale insensitive data. For example metric system. As for time we alawys use POSIX time wich always relates to UTC. > Does ICU support any kind of contenttype, metadata or filename extension that >could identify such items > to tools? Will your Locale library have any add on or enhancement to simplify >this use-case; > > perhaps translate<object type> versus translate? This is done differently. Lets define following: class distance { int meters; }; std::ostream &operator<<(std::ostream &out,distance const &d) { // get stream specific locale std::locale l=out.getloc(); // get stream specific factor double factor = atof(dgettext("Distance conversion factor for km","1.0",l).c_str()); int local_distance = static_cast<int>(metric_distance * factor); // format the distance is stream specific units. out <<format(translate("{1,num} kms","{1,num} kms",local_distance)) % local_distance } Note: locaization is different for serialization and it is wrong way to look on them this way. Serialization is provided for computer-to-computer interface while localization is provided for computer-to-human interface and it is much more compilcated. For example, for serialization of time point it is enought to write it as number representing POSIX time to stream. time_t time_point=time(0); std::cout << time_point; // would be something like 32452345 For human you would write time_t time_point=time(0); std::cout << as::date_time << time_point; // may be something like 03/02/2010 12:30:02 Artyom

3 4

[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

Boost.Thread test results in Boost.Tokenizer
by Andrey Semashev 22 Aug '10

22 Aug '10

Hi, I'm looking at Boost.Tokenizer trunk test results. For some reason, Sandia-intel-10.1 column contains test "examples" which result refers to some Boost.Thread test: <http://www.boost.org/development/tests/trunk/developer/output/Sandia-intel-…> Does anyone know how that happened and how to fix it?

3 4

[thread] throw during new boost::thread() ??
by David M. Cotter 22 Aug '10

22 Aug '10

if i allocate more than 5501 threads, subsequent threads fail to run. these threads live a very short time and only maybe ten max are alive at any one time. for example if i'm iterating over every song in my music library and doing some quick process, after about 5500 songs, the program stops working. i'm exiting the threads normally, so housekeeping is performed (tho it would be performed anyway, right?) i checked and when it crashes there are indeed only about five threads running. so SOME resource is not getting released, it's not my resource, it's something to do with boost::threads. as a test, i created one thread, then on that thread i loop and create 30,000 threads. the only thing the thread does is increment a counter and exit, so no more than a couple threads are live at once. why is it throwing an exception?? call stack: #0 0x001cebaf in boost::detail::sp_counted_impl_p<boost::detail::thread_data<CFork_Preemptive> >::sp_counted_impl_p at sp_counted_impl.hpp:67 #1 0x001cec0f in boost::detail::shared_count::shared_count<boost::detail::thread_data<CFork_Preemptive> > at shared_count.hpp:87 #2 0x001d008a in boost::shared_ptr<boost::detail::thread_data_base>::shared_ptr<boost::detail::thread_data<CFork_Preemptive> > at shared_ptr.hpp:187 #3 0x001d0110 in boost::thread::make_thread_info<CFork_Preemptive> at thread.hpp:136 #4 0x001d0149 in boost::thread::thread<CFork_Preemptive> at thread.hpp:186 #5 0x001c6e92 in CThreads::Fork at CThreads.cpp:765 template<class X> class sp_counted_impl_p: public sp_counted_base { private: X * px_; sp_counted_impl_p( sp_counted_impl_p const & ); sp_counted_impl_p & operator= ( sp_counted_impl_p const & ); typedef sp_counted_impl_p<X> this_type; public: explicit sp_counted_impl_p( X * px ): px_( px ) { <<--- throw happens right here #if defined(BOOST_SP_ENABLE_DEBUG_HOOKS) boost::sp_scalar_constructor_hook( px, sizeof(X), this ); #endif } virtual void dispose() // nothrow { #if defined(BOOST_SP_ENABLE_DEBUG_HOOKS) boost::sp_scalar_destructor_hook( px_, sizeof(X), this ); #endif boost::checked_delete( px_ ); }

6 10

boost-owner@lists.boost.org
by Edward Diener 21 Aug '10

21 Aug '10

I would like write access to the Boost sandbox in order to post some code there for possible future inclusion in Boost. Edward Diener

1 1

Re: [boost] Book "The Boost C++ Libraries" now in Chinese
by Eric Niebler 21 Aug '10

21 Aug '10

On 8/19/2010 4:57 PM, Boris Schaeling wrote: > I'm pleased to announce that the book "The Boost C++ Libraries" is now > available in Chinese: <http://zh.highscore.de/cpp/boost/> > > A big thank you goes to Albert Lai and his team of translators! They > managed to translate the entire book in only four months and taught me > something about the Chinese language. :-) This is extremely cool. Congrats. Now if only there were some content about metaprogramming... ;-) -- Eric Niebler BoostPro Computing http://www.boostpro.com

2 1

[fusion] Any chance we can incorporate more folds?
by David Sankel 21 Aug '10

21 Aug '10

I've implemented, in particular, foldr1: template< typename Sequence, typename State, typename F > typename result_of::foldr1<Sequence, F>::type foldr1( Sequence& seq, F const& f); Semantics: Equivalent to f(....f(f(e1,e2),e3)...) where e1 ...eN are the elements of seq. It is very useful for fusion sequences of possibly distinct types that have identical concepts which can be merged in some way (like generators). I very much like the folds that are included in Haskell's prelude, namely foldl, foldl1, foldr (somewhat like boost's fold), and foldr1[1]. David [1] http://www.haskell.org/onlinereport/haskell2010/haskellch20.html#x28-231000… -- David Sankel Sankel Software www.sankelsoftware.com 585 617 4748 (Office)

6 9

McAfee warning
by Johan Råde 20 Aug '10

20 Aug '10

When downloading Boost, McAfee warns that "In our tests, this download contained programs some people would consider adware, spyware or potentially unwanted programs." See attached screen shot. --Johan

4 6

[tokenizer] 1.44 VS compiler warnings
by Okko Willeboordse 19 Aug '10

19 Aug '10

Hello, Running Boost 1.44, VS2008 SP1, W SDK 6.1, W Server 2003 When I compile; #include <boost/date_time.hpp> I get the following compiler warnings; ... c:\program files\microsoft visual studio 9.0\vc\include\iosfwd(589) : warning C4996: 'std::_Traits_helper::copy_s': ... ... c:\program files\microsoft visual studio 9.0\vc\include\iosfwd(616) : warning C4996: 'std::_Traits_helper::move_s': ... ... c:\program files\microsoft visual studio 9.0\vc\include\iosfwd(607) : warning C4996: 'std::char_traits<char>::copy': ... ... etc.. Above is caused by resent changes to tokenizer, more specific token_functions.hpp for ticket 1755, starting with revision 62706. When I revert token_functions.hpp to version of 1.43 warnings go away. When I compile (copied from boost/date_time/date_parsing.hpp); #include <boost/tokenizer.hpp> typedef std::basic_string<char>::traits_type traits_type; typedef boost::char_separator<char, traits_type> char_separator_type; void foo() { const char sep_char[] = {',','-','.',' ','/','\0'}; char_separator_type sep(sep_char); } I get identical warnings; Kind regards, Okko Willeboordse

5 5

[mpl] unexpected behaviour of mpl::add
by Thomas Heller 19 Aug '10

19 Aug '10

Hi, I just noticed something i find very odd. Considering this example: mpl::add<mpl::int_<1>, mpl::int_<1>::type So I was expecting that this metafunction returns a mpl::int<2> Unfortunately, this was not the case, instead a mpl::integral_c<int, 2> was returned. Is this a bug or a feature? Regards, Thomas

2 1

[serializatrion] problems with 1.44
by Dmitry Vinogradov 19 Aug '10

19 Aug '10

I think something was broken in Boost 1.44. This code fails to compile with 1.44, but compiles with 1.43 (MSVC 10.0): #include <boost/variant.hpp> #include <boost/serialization/variant.hpp> #include <boost/archive/binary_iarchive.hpp> #include <sstream> int main() { std::stringstream s; boost::archive::binary_iarchive ar(s); boost::variant<int, char> x; ar >> x; return 0; } e:\libraries\boost\boost\serialization\variant.hpp(139): error C3861: 'BOOST_SERIALIZATION_NVP': identifier not found Am I missing something or is it a bug?

3 2

Re: [boost] McAfee warning
by Wolfgang Forstmeier 19 Aug '10

19 Aug '10

Where do you download from? My download from http://www.sourceforge.net seems to be ok. Checked that with "Microsoft Security Essentitals". -- > On Wed, Aug 18, 2010 at 6:17 PM, Johan Råde <rade(a)maths.lth.se> wrote: >> When downloading Boost, McAfee warns that >> "In our tests, this download contained programs some people would >> consider adware, spyware or potentially unwanted programs." >> See attached screen shot. >> >> --Johan >> >> _______________________________________________ >> Unsubscribe & other changes: >> http://lists.boost.org/mailman/listinfo.cgi/boost >> > > > > -- > Mit freundlichen Grüßen, > With best regards, > > Wolfgang Forstmeier > > Homines sumus nun dei (Petronius) > ------------------------------------------- > mailto:wolfgang.forstmeier@gmail.com > -- Mit freundlichen Grüßen, With best regards, Wolfgang Forstmeier Homines sumus nun dei (Petronius) ------------------------------------------- mailto:wolfgang.forstmeier@gmail.com

2 1

boost internal compile problems after moving to 1.44 in VC10
by Christopher Lux 18 Aug '10

18 Aug '10

Hi, i am in the process of moving my projects to boost 1.44 on VC10 x64. These are the problems i have (seems like all are boost internal): The errors especially are show stoppers here, i am not that into rvalue references yet to see the problems with the templates in boost.interprocess. 1>E...\inc\boost\boost/interprocess/detail/move.hpp(342): error C2440: 'return' : cannot convert from 'boost::interprocess::file_mapping' to 'boost::interprocess::file_mapping &&' 1> You cannot bind an lvalue to an rvalue reference 1> E...inc\boost\boost/interprocess/file_mapping.hpp(62) : see reference to function template instantiation 'boost::interprocess::file_mapping &&boost::interprocess::move<boost::interprocess::file_mapping&>(T)' being compiled 1> with 1> [ 1> T=boost::interprocess::file_mapping & 1> ] 1>E...\inc\boost\boost/interprocess/detail/move.hpp(342): error C2440: 'return' : cannot convert from 'boost::interprocess::mapped_region' to 'boost::interprocess::mapped_region &&' 1> You cannot bind an lvalue to an rvalue reference 1> E...\inc\boost\boost/interprocess/mapped_region.hpp(159) : see reference to function template instantiation 'boost::interprocess::mapped_region &&boost::interprocess::move<boost::interprocess::mapped_region&>(T)' being compiled 1> with 1> [ 1> T=boost::interprocess::mapped_region & 1> ] 1>E...\inc\boost\boost/thread/win32/thread_data.hpp(171): warning C4244: 'argument' : conversion from '__int64' to 'long', possible loss of data 1> ..\..\..\..\..\xxx.cpp(366) : see reference to function template instantiation 'void boost::this_thread::sleep<boost::date_time::subsecond_duration<base_duration,frac_of_second>>(const TimeDuration &)' being compiled 1> with 1> [ 1> base_duration=boost::posix_time::time_duration, 1> frac_of_second=0x03e8, 1> TimeDuration=boost::date_time::subsecond_duration<boost::posix_time::time_duration,0x03e8> 1> ] 1>E...\inc\boost\boost/interprocess/detail/os_file_functions.hpp(124): warning C4018: '>' : signed/unsigned mismatch

3 4