March 2007 - Boost - lists.preview.boost.org

[Report] 35 regressions on RC_1_34_0 (2007-03-12)
by Douglas Gregor 14 Mar '07

14 Mar '07

Boost Regression test failures Report time: 2007-03-12T05:48:13Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/i… 35 failures in 7 libraries graph (4) iostreams (7) numeric/interval (1) optional (6) parameter (1) python (15) test (1) |graph| dijkstra_heap_performance: msvc-7.0 graphviz_test: msvc-7.1_stlport4 layout_test: msvc-7.0 relaxed_heap_test: msvc-7.0 |iostreams| bzip2_test: msvc-7.1 msvc-8.0 file_descriptor_test: gcc-cygwin-3.4.4 gzip_test: msvc-7.1 msvc-8.0 zlib_test: msvc-7.1 msvc-8.0 |numeric/interval| test_float: msvc-7.1_stlport4 |optional| optional_test: msvc-6.5 msvc-6.5 msvc-6.5_stlport4 msvc-7.0 optional_test_ref_fail2: msvc-7.1 msvc-8.0 |parameter| python_test: gcc-cygwin-3.4.4 |python| import_: cw-9.4 gcc-mingw-3.4.2 gcc-mingw-3.4.5 intel-vc71-win-9.1 msvc-6.5 msvc-6.5 msvc-6.5_stlport4 msvc-7.0 msvc-7.1 msvc-7.1 msvc-7.1 msvc-7.1_stlport4 msvc-8.0 msvc-8.0 msvc-8.0 |test| prg_exec_fail3: cw-9.4

3 5

[1.34.0] RC_1_34_0_freeze Tag
by Thomas Witt 14 Mar '07

14 Mar '07

Hi, I just added a tag to RC_1_34_0. We will begin marking up the remaining failures. Python being the only exception for now. Thomas -- Thomas Witt witt(a)acm.org

2 2

Can my mails be read now?
by Sam Schetterer 14 Mar '07

14 Mar '07

Okay, I'm using gmail now. It should work. If it does not, then please post saying that it doesn't work

2 1

Blank emails? I'm not sending blank emails
by Sam Schetterer 14 Mar '07

14 Mar '07

3 2

Re: [boost] [asio].[aix].[1_33_1] Update regarding test cases compilation
by Gaurav.Jain＠iflexsolutions.com 14 Mar '07

14 Mar '07

Hi Chris, > > Hi Gaurav, > > On Wed, 7 Mar 2007 18:20:48 +0530, Gaurav.Jain <at> iflexsolutions.com said: > > Hi, > > > > Am compiling & running the BOOST ASIO test case on IBM AIX machine. The > > detail of this activity is as follow: > [...] > > "/1.33.1/include/boost-1_33_1/boost/asio/ip/basic_endpoint.hpp", line > > 176.14: 1540-0217 (S) "ss_family" is not a member of "struct > > socbkaddr_storage". > > These error messages don't correspond to the asio 0.3.8 release > candidate 2. Can confirm if you are using that version? Thanks. > I am afraid to say that you are right in your observation. I am now using asio 0.3.8rc2 to compile and run the asio test cases. I am able to run the following test cases successfully: basic_datagram_socket.cpp basic_deadline_timer.cpp basic_socket_acceptor.cpp basic_stream_socket.cpp buffer.cpp buffered_read_stream.cpp buffered_stream.cpp buffered_write_stream.cpp completion_condition.cpp datagram_socket_service.cpp deadline_timer.cpp deadline_timer_service.cpp error.cpp io_service.cpp is_read_buffered.cpp is_write_buffered.cpp placeholders.cpp read.cpp read_until.cpp socket_acceptor_service.cpp socket_base.cpp strand.cpp stream_socket_service.cpp time_traits.cpp write.cpp address.cpp address_v4.cpp address_v6.cpp basic_endpoint.cpp basic_resolver.cpp basic_resolver_entry.cpp basic_resolver_iterator.cpp basic_resolver_query.cpp host_name.cpp resolver_query_base.cpp resolver_service.cpp tcp.cpp udp.cpp unicast.cpp v6_only.cpp Following test cases are throwing ambiguous reference to "ip" error during compilation: "socket_base.cpp", line 38.5: 1540-0600 (S) The reference to "ip" is ambiguous. "/usr/include/netinet/ip.h", line 141.8: 1540-0425 (I) "ip" is defined on line 141 of "/usr/include/netinet/ip.h". "/1.33.1/include/boost/asio/ip/basic_resolver.hpp", line 27.11: 1540-0425 (I) "boost::asio::ip" is defined on line 27 of "/1.33.1/include/boost/as io/ip/basic_resolver.hpp". "/1.33.1/include/boost/asio/ip/resolver_service.hpp", line 27.11: 1540-04 25 (I) "boost::asio::ip" is defined on line 27 of "/1.33.1/include/boost/ asio/ip/resolver_service.hpp". "/1.33.1/include/boost/asio/ip/basic_endpoint.hpp", line 36.11: 1540-0425 (I) "boost::asio::ip" is defined on line 36 of "/1.33.1/include/boost/as io/ip/basic_endpoint.hpp". "/1.33.1/include/boost/asio/ip/address.hpp", line 33.11: 1540-0425 (I) "b oost::asio::ip" is defined on line 33 of "/1.33.1/include/boost/asio/ip/address.hpp". socket_base.cpp address_v4.cpp address_v6.cpp host_name.cpp tcp.cpp udp.cpp unicast.cpp v6_only.cpp After qualifying boost::asio:: to all the ip in the above mentioned test cases, I am able to compile & execute them. > > multicast.cpp > > > > > > > > command line : /asio_test/ip>CC -I$HOME/1.33.1/64/include -xtarget=ultra > > -xarch=v > > > > 9 -D_XOPEN_SOURCE=500 -D__EXTENSIONS__ -library=stlport4 > > -features=tmplife -features=t > > > > mplrefstatic multicast.cpp -L$HOME/1.33.1/64/lib -lboost_system-sw > > -lxnet -lsocket -l > > > > nsl > > > > > > > > /asio_test/ip>./a.out > > > > Running 2 test cases... > > > > multicast.cpp(241): error in "ip_multicast_runtime::test": check !ec > > failed > > > > unknown location(0): fatal error in "ip_multicast_runtime::test": > > std::length_error: b > > > > oolean socket option resize > > Any chance you can run this test in the debugger and find out: > > - The value of ec at line 241 > > - The call stack for where the exception is thrown. I have not run multicast.cpp. Once I run it, will tell you the results. Regards, Gaurav Jain DISCLAIMER: This message contains privileged and confidential information and is intended only for an individual named. If you are not the intended recipient, you should not disseminate, distribute, store, print, copy or deliver this message. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. The sender, therefore, does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required, please request a hard-copy version.

2 1

[Boost-bugs] [ boost-Bugs-1681011 ] multi_index, multi_array collision
by SourceForge.net 14 Mar '07

14 Mar '07

Bugs item #1681011, was opened at 2007-03-14 14:01 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1681011&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: multi_index Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Joaqu�n M L�pez Mu�oz (joaquintides) Summary: multi_index, multi_array collision Initial Comment: I'm not the most experienced user, so pl. excuse me if I'm just missing something. venkyn(a)gmail.com -------test.cc-------- /* simply including this causes the following errors on compilation */ #include <boost/multi_index_container.hpp> #include <boost/multi_array.hpp> int main() { /* this is one of the examples in the Boost multiarray documentation */ typedef boost::multi_array<double, 3> array_type; array_type A( boost::extents[3][4][2] ); A[0][0][0] = 3.14; } ---------- Trying to compile this: $> /home/sapo/software/compilers/gcc/gcc-3.2.3-install/bin/g++ -I/home/sapo/software/compilers/gcc/gcc-3.2.3-install/include -I/home/sapo/software/boost//include/boost-1_33_1 -L/home/sapo/software/compilers/gcc/gcc-3.2.3-install/lib -lm -o test src/test.cc /home/sapo/software/boost/include/boost-1_33_1/boost/multi_array/multi_array_ref.hpp: In member function `boost::const_multi_array_ref<T, NumDims, T*>::reference boost::multi_array_ref<T, NumDims>::operator[](boost::const_multi_array_ref<T, NumDims, T*>::index) [with T = double, unsigned int NumDims = 3]': src/test.cc:12: instantiated from here /home/sapo/software/boost/include/boost-1_33_1/boost/multi_array/multi_array_ref.hpp:515: no matching function for call to `boost::const_multi_array_ref<double, 3, double*>::access(boost::type<boost::detail::multi_array::sub_array<double, 2> >, index&, double*, const size_type*, const index*, const index*)' /home/sapo/software/boost/include/boost-1_33_1/boost/multi_array/subarray.hpp: In member function `boost::detail::multi_array::const_sub_array<T, NumDims, T*>::reference boost::detail::multi_array::sub_array<T, NumDims>::operator[](boost::detail::multi_array::const_sub_array<T, NumDims, T*>::index) [with T = double, unsigned int NumDims = 2]': src/test.cc:12: instantiated from here /home/sapo/software/boost/include/boost-1_33_1/boost/multi_array/subarray.hpp:261: no matching function for call to ` boost::detail::multi_array::const_sub_array<double, 2, double*>::access( boost::type<boost::detail::multi_array::sub_array<double, 1> >, index&, double*&, const size_type*, const index*, const index*)' /home/sapo/software/boost/include/boost-1_33_1/boost/multi_array/subarray.hpp: In member function `boost::detail::multi_array::const_sub_array<T, NumDims, T*>::reference boost::detail::multi_array::sub_array<T, NumDims>::operator[](boost::detail::multi_array::const_sub_array<T, NumDims, T*>::index) [with T = double, unsigned int NumDims = 1]': src/test.cc:12: instantiated from here /home/sapo/software/boost/include/boost-1_33_1/boost/multi_array/subarray.hpp:261: no matching function for call to ` boost::detail::multi_array::const_sub_array<double, 1, double*>::access( boost::type<double&>, index&, double*&, const size_type*, const index*, const index*)' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1681011&group_… ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Re: [boost] [XML] Searching for an XML parsing library in boost
by Marc Salaun 14 Mar '07

14 Mar '07

All, I have written an 'extensible' xml serialisation library (xxs) that may be of interest to some people who contributed to this thread. It tries to get as close as possible to python's 'batteries included' philosophy, while still being as easy to extend as possible. For a start, here is a full mutli-threaded xml-rpc server, with 10 worker threads: #include "xxs/xxs.h" #include <list> #include <numeric> int sum(const std::list<int>& values) { return std::accumulate(values.begin(), values.end(), 0); } void main() { xxs::server server("ldn013850", "8081", 10); server.implement_xmlrpc_function("sum", &sum); server.run(); } You extend xxs to support a new STL-like container this way: template<typename T, typename Format> struct xxs::is_container<std::set<T, Format> : boost::true_type { typedef T element_type; static const bool ordered = true; }; Containers, maps, smart pointers, basic types and classes can be combined recursively Here is how you add support for a struct or class: a. In an intrusive manner, by adding a static xxs method class circle { point _center; double _radius; public: ../.. double get_radius() const { return _radius; } void set_radius(double value) { _radius = value; } template <typename Format, class T> static void xxs(T& t) { t.add("center", &circle::_center); t.add("radius", &circle::get_radius, &circle::set_radius); } }; b. In a non intrusive manner, for std::pair<> in this case template<typename KEY, typename VALUE, typename Format> struct xxs::is_object<std::pair<KEY, VALUE>, typename Format> : boost::true_type { template <typename Format, class M> static void introspect(M& m) { m.add("first", &std::pair<KEY, VALUE>::first); m.add("second", &std::pair<KEY, VALUE>::second); } }; You serialize/deserialize 'data' this way: std::cout << xxs::xml<>(data) << std::endl; std::cout << xxs::xml<xxs::xmlrpc>(data) << std::endl; std::cin >> xxs::xml<>(data); You can specify xml-rpc or 'normal' xml formats with or without attributes. A simplified soap format is also supported (see http://www.soapware.org/bdg specs, interop untested). You can extend the library to support additional smart pointers, basic types, make certain C++ classes or enums to be processed as strings or integers, etc.. Finally you have the option to serialize/deserialize arbitrary structures using the xxs::is_generic_object trait class, for instance to serialize/deserialize boost::python::object. It works very well with python's xmlrpclib module :-) So far the library compiles on VC7.1 and VC8. I don't think there is anything groundbreaking there (it mimics and uses other boost libraries - mainly traits and asio for the client/server bits), but i believe the end result is very useful: - It is very reliable, thread-safe, memory leak free and the code generated is particularly efficient - The omnipresent 'Format' template parameter allows for interesting strategies for xml versioning and gives extra flexibility - You can reuse the xxs template method for many other purposes Now for the bad news: - I will probably not have the time to push this library up to boost standards all by myself - although i can spend some reasonable amount of time on it - The library uses expat - but plugging it in a Spirit equivalent wouldn't be hard to do The way i see this library going forward is to have to have some of its parts rewritten using Spirit or Spirit techniques - not necessarily to replace expat but to allow more user control over the XML structure being generated, potentially covering the full SOAP specs this way. I have the following questions for the boost community: - Is there any room for such a library in boost ? - Is there anyone out there with a similar project/interest who would like to join forces ? thanks for your feedback marc

2 1