- Boost - lists.boost.org

[exception] enable_error_info.hpp compile errors
by Beman Dawes 27 May '08

27 May '08

Boost.Filesystem's wide_test is failing on trunk due to enable_error_info.hpp compile errors. It's happening with many (or maybe all) compilers. See below for typical error messages. --Beman ..\boost/exception/enable_error_info.hpp(23): error: not a class or struct name public T, ^ detected during: instantiation of class "boost::exception_detail::error_info_injector<T> [with T=char [29]]" at line 90 instantiation of "boost::exception_detail::enable_error_info_return_type<T>::type boost::enable_error_info(const T &) [with T=char [29]]" at line 58 of "..\boost/throw_exception.hpp" instantiation of "void boost::throw_exception(const E &) [with E=char [29]]" at line 114 of "..\libs\filesystem\test\wide_test.cpp" ..\boost/exception/enable_error_info.hpp(28): error: "T" is not a nonstatic data member or base class of class "boost::exception_detail::error_info_injector<char [29]>" T(x) ^ detected during: instantiation of "boost::exception_detail::error_info_injector<T>::error_info_injector(const T &) [with T=char [29]]" at line 95 instantiation of "boost::exception_detail::enable_error_info_return_type<T>::type boost::enable_error_info(const T &) [with T=char [29]]" at line 58 of "..\boost/throw_exception.hpp" instantiation of "void boost::throw_exception(const E &) [with E=char [29]]" at line 114 of "..\libs\filesystem\test\wide_test.cpp"

2 2

Re: [boost] Question regarding logging, persistence, threadcommunication, network messaging and async frameworks
by brass goowy 27 May '08

27 May '08

Scott Woods writes: >Hi, >Is there a place in Boost for a library that tackles all of the above? I >believe the realistic >answer is no but I would be happy to be proven wrong. >Work in the different areas mentioned in the subject line recently collapsed >into a single >underlying technique. Given the example UDT below; >struct person >{ >std::string name; >std::vector<unsigned> score; >std::set<string> team; >}; >persistence is achieved using; >person new_member; >codec_object<person> configuration( "profile" ) >configuration << new_member; // Save in a disk file name >"profile" >configuration >> new_member; // Load from the same disk file >transmitting the same object between threads looks like; >send( new_member, other_thread ); >while receiving that transmission occurs in code that looks like; >my_thread::received( person &new_member ) >{ >.. >} >Transmission of messages across networks looks like; >send( new_member, socket_proxy ); >Yes, its the same as for inter-thread communications. The "socket_proxy" >just >happens to be a variation on "my_thread" that forwards materials it receives >onto a socket connection. >Logging looks like; >WINSOCK( socket, AF_INET << SOCK_STREAM << 0 ); >COMMENTARY( "connection to " << address_entered << " failed (" << >failure << ")" ); >Logging messages can be routed anywhere based on the type and unique >identity of >the originating party. >The fragments of code provided above hide a lot. While that's technically >desirable >I can appreciate that it might not flesh out my question at all (i.e. >...room in Boost). But >actually this is precisely the most compelling thing about the library - it >reduces code >that traditionally can be quite difficult into fragments such as those >shown. Shalom From what you've shown it looks like the duplication of data members in serialization methods is not needed. Some have been struggling to eliminate the need for that duplication -- http://preview.tinyurl.com/6kpx8t . Maybe more details about codec_object<> would be helpful. Brian Wood Ebenezer Enterprises www.webEbenezer.net

3 4

promote "unwrap" to ref.hpp
by Ronald Garcia 27 May '08

27 May '08

Hi all, boost::reference_wrapper exists at the top-level of boost (in boost/ ref.hpp), but that header provides no way to unwrap a reference_wrapper. There are two implementations floating around of "unwrap", one in boost.bind's implementation details, and one in boost.mpl's implementation details. Is there any problem with providing a version of unwrap in ref.hpp? ron

4 8

[test] Documentation confusion
by Maik Beckmann 27 May '08

27 May '08

Hello, I am confused about the boost.test documentation. There are docs in trunk and after some hours of digging via gmane if found this one http://www.patmedia.net/~rogeeff/html/index.html index.html in trunk : ... Revised: 28 February, 2006 index.html external link: Copyright © 2001-2007 Gennadiy Rozental ... My impression is that the 2007 version is much more comprehensive. Why isn't the most recent one in trunk? Do the trunk docs got a link the the external docs? -- Maik

1 0

[Parameter] template return type
by brook＠biology.nmsu.edu 27 May '08

27 May '08

I am trying to use Boost.Parameter to construct some objects, much like make_tuple(A,B) does except with some of the arguments being optional and replaced by defaults (which may depend on the other arguments). The return type, however, must be a template class with the template arguments dependent on the arguments supplied. Is this possible? How can the return type for a Boost.Parameter frunction be specified as a template type? Thanks for your help. Cheers, Brook

2 1

[MPI] Compile problem while building Boost 1.35.0
by Adam Stephens 27 May '08

27 May '08

Hi, all, I'm trying to build Boost on linux using bjam. Everything seems to compile smoothly except one file in Boost.MPI. The error is lengthy, but the first part reads: intel-linux.compile.c++ bin.v2/libs/mpi/build/intel-linux/release/threading-multi/datatypes.o ./boost/mpi/python/serialize.hpp(321): error: no operator "<<" matches these operands operand types are: boost::mpi::packed_oarchive << boost::mpl::if_<boost::is_fundamental<long>, long, long &>::type ar << extract<Type>(obj)(); ^ detected during: instantiation of "void boost::python::detail::direct_serialization_table<IArchiver, OArchiver>::default_saver<T>::operator()(OArchiver &, const boost::python::api::object &, unsigned int) [with IArchiver=boost::mpi::packed_iarchive, OArchiver=boost::mpi::packed_oarchive, T=long]" at line 158 of "./boost/function/function_template.hpp" My compiler is Intel/9.1 and the implementation of MPI is openmpi 1.2.4. I've also tried to build using intel/10.1, and I got the same error. My user-config.jam, the first several lines of output from bjam --debug-configuration, and the section of the bjam output with all the errors is posted at http://utilitybase.com/paste/6780 Thanks

2 1

[test] SIGPOLL not defined on FreeBSD?
by John Maddock 27 May '08

27 May '08

If possible I'd like to see a fix for: http://tinyurl.com/3uz5xg Looks like we just need to add FreeBSD to the list of OS's that don't define SIGPOLL at the start of execution_monitor.ipp. The strange thing is, the other FreeBSD tester doesn't fail here... anyone know what the difference is between them? Both define XOPEN_UNIX to be -1 so they're both advertising that they *don't* support this XSI-specific feature. Come to that are these symbols all macros? Could we just check for defined(SIGPOLL) ? Cheers, John.

3 3

Re: [boost] Question regarding logging, persistence,threadcommunication, network messaging and async frameworks
by brass goowy 27 May '08

27 May '08

Scott Woods writes: >I looked through the thread at "for each member of a sturcture/class ?" and >not >sure how to respond; the issue being dealt with in that thread (while >interesting) is >subordinate to my goals. >I do not have any magic technique for avoiding duplication of member >information. Any C++ type that wishes to play within my library >must define the following two global operators; >inline network_variant & >operator<<( network_variant &nv, const person &p ) >{ >network_memory::iterator i = network_output<3>()( nv ); >*i++ << p.name; >*i++ << p.score; >*i++ << p.team; >return nv; >} >inline person & >operator>>( network_variant &nv, person &p ) >{ >network_memory::iterator i = network_input<3>()( nv ); >*i++ >> p.name; >*i++ >> p.score; >*i++ >> p.team; >return p; >} >My library for persistence, thread communication and network messaging >deals with the movement and representation of "network_variants", i.e. >by providing transform functions as above, the type acquires persistence, >transfer-between-threads and transfer-across-networks capabilities, in >one hit. It would have been good to include those in your original post. When you said, "But actually this is precisely the most compelling thing about the library - it reduces code that traditionally can be quite difficult into fragments such as those shown," I wondered if that meant you had developed an alternative approach. It isn't clear to me how what you have is better than what is already in Boost. From what you've said I guess it is more flexible, but it isn't obvious to me how. You could also consider integration with http://s11n.net. Regards, Brian Wood Ebenezer Enterprises www.webEbenezer.net

2 1

[filesystem] Make basic_path more generic?
by Alexei Alexandrov 26 May '08

26 May '08

Hi, in several places I need to have code which works both with char and wchar_t. Those are template functions. I also work with paths there so I wanted to actually write something like template <typename CharType> void foo(const std::basic_string<CharType>& s) { typedef fs::basic_path<std::basic_string<CharType> > path_type; ... } but it turned out that I can't do it because 1) basic_path has the second Traits template parameter mandatory and 2) this Traits parameter has actually different type for path and wpath: struct path_traits; typedef basic_path< std::string, path_traits > path; // ... struct BOOST_FILESYSTEM_DECL wpath_traits; typedef basic_path< std::wstring, wpath_traits > wpath; Of course, I can easily workaround it with my own traits, but I wonder could it be in the first place like: template<class String> class basic_path_traits; template<class String, class Traits = basic_path_traits<String> > class basic_path; with basic_path_traits being specialized for std::string and std::wstring and fs::path and fs::wpath being just typedef basic_path< std::string > path; typedef basic_path< std::wstring > wpath; ? Thanks. -- Alexei Alexandrov

3 3

Re: [boost] Building Boost.Coroutine [vault]
by Thomas Karolski 26 May '08

26 May '08

> If you can find out about any compilation error on VC++9 > I can try a blind fix. <http://lists.boost.org/mailman/listinfo.cgi/boost>Hmm. It seems the msvc compiler & linker (cl.exe) does not want to do *anything* at all when executed outside of the Visual Studio 2008 Command Prompt. It does not even respond to /HELP or /VERSION. Anyway, compiling the coroutine library from inside the VS08 Command Prompt worked fine just now. There should be no need to fix anything. Regards, Thomas K.

3 2