- Boost-users - lists.boost.org

[tr1] tuple / autoconversion problem
by Markus Werle 20 Aug '08

20 Aug '08

> [ignore this line: it makes gmane stop complaining about top-posting] Hi! Trying to migrate existing code from boost::xxx to std::tr1::xxx using the boost::tr1 implementation for Visual Studio 2005 SP1 In the presence of some exotic autoconversion utility the the std::tr1::tuple version of my code fails on vc8. The error messages indicate that the conversion operator is not considered by the compiler. Below is code that fails to compile on vc8 if USE_TR1 is defined Do you have an idea how to fix this? Thanx, Markus ---snip--- #include <boost/tr1/memory.hpp> #ifdef USE_TR1 #include <boost/tr1/tuple.hpp> #else #include <boost/tuple/tuple.hpp> #endif #include <boost/any.hpp> #include <iostream> namespace Core { class AutoConverter { std::tr1::shared_ptr<boost::any> t_; public: AutoConverter(std::tr1::shared_ptr<boost::any> const & t) : t_(t) {} template <typename C> operator C () { try { boost::any & a = (*t_); return boost::any_cast<C>(a); } catch(boost::bad_any_cast & e) { std::cerr << "Internal conversion bug: " << "Failed to convert data holder to " << typeid(C).name() << "\n" << e.what() << std::endl; C c = C(); return c; } } }; inline AutoConverter Demo() { #ifdef USE_TR1 std::tr1::shared_ptr<boost::any> p_result (new boost::any(std::tr1::make_tuple(1, 2, 3, 4))); #else std::tr1::shared_ptr<boost::any> p_result (new boost::any(boost::make_tuple(1, 2, 3, 4))); #endif return p_result; } } // namespace Core int main(int argc, char* argv[]) { #ifdef USE_TR1 std::tr1::tuple<int, int, int, int> test = Core::Demo(); #else boost::tuple<int, int, int, int> test = Core::Demo(); #endif return 0; } ---snip--- Error message is: >------ Build started: Project: TR1TupleConversionProblem, Configuration: Debug Win32 ------ 1>Compiling... 1>stdafx.cpp 1>TR1TupleConversionProblem.cpp 1>[...]\boost_1_36_0\boost\fusion\sequence\intrinsic\begin.hpp(56) : error C2504: 'boost::fusion::extension::begin_impl<Tag>::apply<Sequence>' : base class undefined 1> with 1> [ 1> Tag=boost::fusion::non_fusion_tag 1> ] 1> and 1> [ 1> Sequence=const Core::AutoConverter 1> ] 1> [...]\boost_1_36_0\boost\fusion\container\vector\detail\vector_n.hpp (65) : see reference to class template instantiation 'boost::fusion::result_of::begin<Sequence>' being compiled 1> with 1> [ 1> Sequence=const Core::AutoConverter 1> ] 1> [...]\boost_1_36_0\boost\fusion\container\vector\detail\vector_n.hpp (105) : see reference to function template instantiation 'boost::fusion::vector_data4<Derived,T0,T1,T2,T3> boost::fusion::vector_data4<Derived,T0,T1,T2,T3>:: init_from_sequence<Sequence>(const Sequence &)' being compiled 1> with 1> [ 1> Derived=boost::fusion::vector4<int,int,int,int>, 1> T0=int, 1> T1=int, 1> T2=int, 1> T3=int, 1> Sequence=Core::AutoConverter 1> ] 1> [...]\boost_1_36_0\boost\fusion\container\vector\vector.hpp(58) : see reference to function template instantiation 'boost::fusion::vector4<T0,T1,T2,T3>::vector4<T>(const Sequence &)' being compiled 1> with 1> [ 1> T0=int, 1> T1=int, 1> T2=int, 1> T3=int, 1> T=Core::AutoConverter, 1> Sequence=Core::AutoConverter 1> ] 1> [...]\boost_1_36_0\boost\fusion\tuple\tuple.hpp(33) : see reference to function template instantiation 'boost::fusion::vector<T0,T1,T2,T3,T4,T5,T6,T7,T8,T9>:: vector<Sequence>(const Sequence &)' being compiled 1> with 1> [ 1> T0=int, 1> T1=int, 1> T2=int, 1> T3=int, 1> T4=boost::fusion::void_, 1> T5=boost::fusion::void_, 1> T6=boost::fusion::void_, 1> T7=boost::fusion::void_, 1> T8=boost::fusion::void_, 1> T9=boost::fusion::void_, 1> Sequence=Core::AutoConverter 1> ] 1> [MYPATH]\tr1tupleconversionproblem.cpp(69) : see reference to function template instantiation 'boost::fusion::tuple<T0,T1,T2,T3,T4,T5,T6,T7,T8,T9>:: tuple<Core::AutoConverter>(const Sequence &)' being compiled 1> with 1> [ 1> T0=int, 1> T1=int, 1> T2=int, 1> T3=int, 1> T4=boost::fusion::void_, 1> T5=boost::fusion::void_, 1> T6=boost::fusion::void_, 1> T7=boost::fusion::void_, 1> T8=boost::fusion::void_, 1> T9=boost::fusion::void_, 1> Sequence=Core::AutoConverter 1> ] 1>[...]\boost_1_36_0\boost\fusion\container\vector\detail\vector_n.hpp(65) : error C2039: 'type' : is not a member of 'boost::fusion::result_of::begin<Sequence>' 1> with 1> [ 1> Sequence=const Core::AutoConverter 1> ] 1>[...]\boost_1_36_0\boost\fusion\container\vector\detail\vector_n.hpp(65) : error C2146: syntax error : missing ';' before identifier 'I0' 1>[...]\boost_1_36_0\boost\fusion\container\vector\detail\vector_n.hpp(65) : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int 1>[...]\boost_1_36_0\boost\fusion\container\vector\detail\vector_n.hpp(65) : error C2065: 'I0' : undeclared identifier 1>[...]\boost_1_36_0\boost\fusion\container\vector\detail\vector_n.hpp(66) : error C2146: syntax error : missing ';' before identifier 'i0' 1>[...]\boost_1_36_0\boost\fusion\container\vector\detail\vector_n.hpp(66) : error C2065: 'i0' : undeclared identifier 1>[...]\boost_1_36_0\boost\fusion\container\vector\detail\vector_n.hpp(66) : error C2893: Failed to specialize function template 'const result_of::begin<const Sequence>::type boost::fusion::begin(const Sequence &)' 1> With the following template arguments: 1> 'Core::AutoConverter' 1>[...]\boost_1_36_0\boost\fusion\container\vector\detail\vector_n.hpp(66) : error C2893: Failed to specialize function template 'const result_of::begin<Sequence>::type boost::fusion::begin(Sequence &)' 1> With the following template arguments: 1> 'const Core::AutoConverter' 1>[...]\boost_1_36_0\boost\fusion\container\vector\detail\vector_n.hpp(67) : error C2955: 'boost::fusion::result_of::next' : use of class template requires template argument list 1> [...]\boost_1_36_0\boost\fusion\iterator\next.hpp(50) : see declaration of 'boost::fusion::result_of::next' 1>[...]\boost_1_36_0\boost\fusion\container\vector\detail\vector_n.hpp(67) : error C2039: 'type' : is not a member of 'boost::fusion::result_of::next' 1> [...]\boost_1_36_0\boost\fusion\iterator\next.hpp(50) : see declaration of 'boost::fusion::result_of::next' 1>[...]\boost_1_36_0\boost\fusion\container\vector\detail\vector_n.hpp(67) : error C2039: 'type' : is not a member of 'boost::fusion::result_of::next<Iterator>' 1> with 1> [ 1> Iterator=I1 1> ] 1>[...]\boost_1_36_0\boost\fusion\container\vector\detail\vector_n.hpp(67) : error C2893: Failed to specialize function template 'const result_of::next<Iterator>::type boost::fusion::next(const Iterator &)' 1> With the following template arguments: 1> 'I1' 1>[...]\boost_1_36_0\boost\fusion\container\vector\detail\vector_n.hpp(67) : error C2039: 'type' : is not a member of 'boost::fusion::result_of::next<Iterator>' 1> with 1> [ 1> Iterator=I1 1> ] 1>[...]\boost_1_36_0\boost\fusion\container\vector\detail\vector_n.hpp(67) : error C2893: Failed to specialize function template 'const result_of::next<Iterator>::type boost::fusion::next(const Iterator &)' 1> With the following template arguments: 1> 'I2' 1>[...]\boost_1_36_0\boost\fusion\container\vector\detail\vector_n.hpp(68) : error C2100: illegal indirection 1>[...]\boost_1_36_0\boost\fusion\container\vector\detail\vector_n.hpp(68) : error C2100: illegal indirection 1>[...]\boost_1_36_0\boost\fusion\container\vector\detail\vector_n.hpp(68) : error C2100: illegal indirection

3 13

[Boost.Test] Looking for Workaround: Subprocesses exiting with 0 reported as fatal error
by Florian Winter 20 Aug '08

20 Aug '08

Hi, Using Boost.Test version 1.35.0, we have run into the following bug http://svn.boost.org/trac/boost/ticket/1723 Is there an easy way to work around or fix this problem in Boost 1.35.0 (such as a patch), so we are not forced to upgrade to the SVN version of Boost.Test? Unfortunately, not starting a sub process is not an option, because it is not our software that starts the sub process but some additional library that we use. In case we have to upgrade to the SVN version of Boost, is there a recent SVN revision or tag that you would consider stable and recommend for use? Thanks in advance for any help. best regards, Florian

5 8

Building Boost Program Options
by Alex Adranghi 20 Aug '08

20 Aug '08

Hi, I've recently decided to build the latest boost version myself, but I'm wondering why there are only shared objects for program options. Ideally I want to build static libraries. Thanks Alex

2 2

Re: [Boost-users] HOWTO: Building Boost for Windows 64-bit
by Gevorg Voskanyan 20 Aug '08

20 Aug '08

[snip] > According to http://tinyurl.com/6zeyhu, cflags affects both the C and C++ > compilers, while cxxflags affects only the C++ compiler; I use cxxflags as a > matter of habit, but in the case of -arch, I suppose cflags would be more > appropriate (although I'm not aware of any C code inside of Boost anyway). Interesting, this caught me by surprise since I thought that cflags was only for C, cxxflags for C++ and compileflags for both. It is documented that way at http://tinyurl.com/63rjal at least. A small testing revealed that http://tinyurl.com/6zeyhu appears to be correct under my environment. cflags affected both C and C++ and compileflags was rejected as an unknown feature. The environment was as follows: Boost.Build V2 (Milestone 12) Boost.Jam 03.1.16 gcc 4.2.2 What would be the correct description of these features? I appreciate all your input. Thanks, Gevorg

1 0

[filesystem] Changes to filesystem_error
by Arno 20 Aug '08

20 Aug '08

Hi all, I moved now from 1.31 to 1.35 and have some problem to understand what I have to change in the area of filesystem_error. I applied all the changes belongs to the iterator stuff and the class itself, but in my special error handling I use the 'who', 'error' and 'native_error' methods which I can not find in the actual model. Can you give me a clue, how I can get this information in 1.35. regards Arno

2 2

[filesystem] temp filenames?
by Hajo Kirchhoff 20 Aug '08

20 Aug '08

Hi all, I found an old (year 2003) feature request for filesystem: create temporary files, but do not see any methods in the current (1.36) version. Can anyone tell me what is the status on this? Best regards Hajo

1 0

boost.asio async_write/read_until guarantee
by Daniel Mierswa 20 Aug '08

20 Aug '08

Hi, if i have a threadpool running an io_service and a read_until is invoked before async_write. Now i wonder what would happen if the string is written to the socket, will the write handler be called before the read_handler or is it undefined in which order they will be invoked? If it's not guaranteed can anyone think of a solution to create such a guarantee in my own program? (I posted the same question on the asio mailinglist but i assume there's more activity here) Thanks in advance -- Mierswa, Daniel If you still don't like it, that's ok: that's why I'm boss. I simply know better than you do. --- Linus Torvalds, comp.os.linux.advocacy, 1996/07/22

2 1

1.35/1.36 thread library and date_time dependency
by Ross Wightman 20 Aug '08

20 Aug '08

After looking through the new 1.35/1.36 threading library (with a lot of nice changes), I am wondering why the decision to tie it to boost::date_time was made? I love date_time as a library, but I believe it's is too large and cumbersome to be tied to a core threading library. It pulls in an excessively large include tree whenever I want to use a mutex or conditional variable. The call tree for doing simple comparisons and calculations at second to nanosecond scales is also excessive. There will always be unnecessary converting from seconds and nanoseconds, into the date_time's internal date + ticks format, and back to seconds and nanoseconds. A more fully realized 'xtime' with functions for easy conversion to/from date_time in an optional header would be a much better approach in my opinion. The C++0x draft standard looks like it uses a lean 'system_time' class which is a small subset of date_time. Regards, Ross

1 0

Bug in 1.35/1.36 thread absolute timed waits
by Ross Wightman 20 Aug '08

20 Aug '08

There is an integer arithmetic bug in get_due_time() used by conditional variables in the boost 1.35/1.36 threading library. On line 343 in thread/src/win32/thread.cpp, integer division is performed before multiplication leaving the possibility of an erroneous 0 result in the case where ticks_per_second is larger than hundred_nanoseconds_in_one_second. Moving the brackets around the multiply or removing them altogether will fix this problem. I think this may only show itself if boost::date_time is setup so that BOOST_DATE_TIME_HAS_NANOSECONDS is true (the way I need it).

1 0

total newbie with quickbook
by e r 20 Aug '08

20 Aug '08

Hi, posted in gclb.doc but no luck so far, so i figured i'd try here: --- Things I did a) sudo apt-get install xsltproc docbook-xsl docbook-xml b) updated user-config.jam file as required c) installed SciTE --- Things I'm unsure about: 1) don't understand this part in the section about SciTE: You can use the following settings (qbk = *.qbk etc) to highlight quickbook tags when editing quickbook files. where should these settings be set? SciTE?! 2) Suppose i have a .qbk file. Where do I go from here? how do i build the html file with it? probably very basic, but... Thanks!

2 2