- Boost-users - lists.boost.org

Re: [Boost-users] numeric/interval overflow & test_float
by Steven Solie 12 Aug '05

12 Aug '05

=?iso-8859-1?Q??= MIME-Version: 1.0 Content-Type: text/plain Guillaume Melquiond wrote: > Unfortunately the output of these tests is a bit poor, since it doesn't > display the parameters causing the failure. I suppose that, since the > overflow test fails on non-double floating-point formats, the same > problem must happen for the test_float test. > > Is there any difference in the way AmigaOS deals with floating-point > computations with respect to other PowerPC operating systems like Darwin > or OSX? I don't have a machine that can run Darwin and I haven't used OSX. However, I do know a couple of things about AmigaOS math support: 1. math exceptions such as divide by zero are simply ignored 2. the underlying C library is custom made 3. the C++ library is the one that comes with GCC 3.4.4 I'm suspecting there may be a bug in the C99 library at this point. Since the C library is open source, you can look for yourself at http://sourceforge.net/projects/clib2/ What I'm wondering now is what math functions the failed tests are executing from the C library? Perhaps there is a boundary condition that a math function is not handling correctly or something. Since these tests don't fail on another PowerPC based system I think the problem lies with my platform but I need help narrowing it down a bit more. Thanks! --Steven

2 1

[serialization][1.33.0?] xml_archive_exception
by Jeff Flinn 12 Aug '05

12 Aug '05

Robert, In using xml_archive_exception, I find that I need to #include <boost/archive/basic_xml_archive.hpp>. This required searching through the boost directory since the documentation does not mention this requirement. The only mention in the docs is to #include <boost/archive/archive_exception.hpp>, which is insufficient. I would have expected that xml_archive_exception is part of the interface for an xml_(i|o)archive and would be included when #include-ing <boost/archive/xml_(i|o)archive.hpp>. Alternatively, perhaps this class should be placed in <boost/archive/xml_archive_exception.hpp> and documented as such, to be consistent with <boost/archive/archive_exception.hpp>. Additionally, I find the overlap of exception_code misleading when debugging. I caught an archive_exception& and and code returns 0 - 'no_exception'( within the context of an archive_exception ). At this point what() returns null also. Of course, catching an xml_archive_exception helps because what() returns a reasonable description. I run into the above, when loading a file, but that file was generated by a legacy product(not xml or an archive). I had (erroneously)expected that xml_archive would throw an xml_archive_exception equivalent to exception_code==invalid_signature. It would be nice to have a some better granularity on archive_parsing_error, that would tell me that the input does not start with an xml header, or it's xml but not an xml_archive, or it passed those two, and some other error occurs. Thanks, Jeff Flinn

2 1

[Serialization] 1.33 RC1 nvp.hpp gotcha
by Richard Jennings 12 Aug '05

12 Aug '05

I have found that the requirement that no serialization headers can be included before any archive headers means that you have to be careful which serialization headers you include in your class headers and indeed in what order you include them. In particular if you include serialization/nvp.hpp before serialization/vector.hpp and you use that class in another module that does not use archiving at all then that module will hit the error directive, example below. A solution would seem to be that serialization/nvp.hpp should only be included in the module that includes archive headers. I guess what I would like is some guidance on using serialization as it's become a bit more tricky in my experience. At least you can't willy-nilly include serialization headers in any order in any headers and expect the application to compile. Perhaps it only worked by luck before! For example, given class A below: class A { private: friend class boost::serialization::access; template <class ArchiveT> void serialize(ArchiveT &ar, unsigned int) { ar & BOOST_SERIALIZATION_NVP(m_Vector); } std::vector<int> m_Vector; }; What serialization headers should be included in A's header? What should be included in the header of the class that serializes A? My inclination would be to include serialization/nvp.hpp and serialization/vector.hpp since these are needed if (but only if) the template is instantiated. This is on the idea that a class should (generally) compile on it's own and you should not have to look to see what it is composed of to be able to get it to compile. Here's the example that does not work: B fails to compile with [C++ Fatal Error] basic_archive.hpp(21): F1003 Error directive: "no serialization headers my precede any archive headers" If you include nvp after vector, then it's ok too! A.h: ======= #include <vector> #include <boost/serialization/nvp.hpp> #include <boost/serialization/access.hpp> #include <boost/serialization/vector.hpp> class A { private: friend class boost::serialization::access; template <class ArchiveT> void serialize(ArchiveT &ar, unsigned int) { ar & BOOST_SERIALIZATION_NVP(m_Vector); } std::vector<int> m_Vector; }; ======= B.h: class B { public: B(); }; ======= B.cpp: #include "B.h" #include "A.h" B::B() { A InstanceOfA; } ======= Main.cpp #include <sstream> #include <boost/archive/text_oarchive.hpp> #include "A.h" #include "B.h" int main(int argc, char* argv[]) { A InstanceOfA; B InstanceOfB; std::stringstream ss; boost::archive::text_oarchive oa(ss); oa & InstanceOfA; return 0; }

4 10

Vector of string pb
by Lana Abadie 12 Aug '05

12 Aug '05

Hello, I am using boost for the first time. I have the following boost.cpp file: #include "../confDBAPIpython/test1.h" #include <boost/python.hpp> #include <boost/python/suite/indexing/vector_indexing_suite.hpp> #include <boost/python/module.hpp> #include <boost/python/def.hpp> #include <boost/python/implicit.hpp> using namespace boost::python; BOOST_PYTHON_MODULE(confDBAPIpython) { // Compile check only... class_<std::vector<int> >("IntVec") .def(vector_indexing_suite<std::vector<int> >()); class_<std::vector<std::string> >("StringVec") .def(vector_indexing_suite<std::vector<std::string> >()); def("DBConnexion",PyDBConnexion); def("DBDeconnexion",PyDBDeconnexion); def("GetDeviceTypeRow",PyGetDeviceTypeRow); def("GetDeviceRow_devicename",PyGetDeviceRow_devicename); def("GetDeviceRow_deviceid",PyGetDeviceRow_deviceid); def("GetDetailedConnectivityBetweenDevices",PyGetDetailedConnectivityBet weenDevices); def("GetConnectivityBetweenDevices",PyGetConnectivityBetweenDevices); } The two last fct returns vector<std::string>. When I try to use them in python, I have the following error message: list_str=libconfDBAPIpython.GetConnectivityBetweenDevices("TFC","THOR_00 ","ECAL_L1FE06_02_00"); print list_str[0]; Traceback (most recent call last): File "<stdin>", line 1, in ? TypeError: No Python class registered for C++ class std::string I don't understand why. I thought it will be handled by the vector_indexing_suite. I have no problem when a fcuntion returns a string or a vector<int> Thanks for helping Lana

1 0

string_algo does not have is_iless???
by gast128 12 Aug '05

12 Aug '05

Dear all, Just ran into a request for a case insensitive std::map. Unfortunately the string_algo did not have something like is_iless, while boost bind does not help me here. Is it possible to add this to the string_algo library? Wkr, me

2 1

New web site
by Foster Gareth 12 Aug '05

12 Aug '05

I just visited boost.org for the first time in a while, and I just thought I'd email in to say the new site looks fantasic, congratulations to the site designer on a job well done! Cheers, Gaz

3 2

.Net equalent Options in regex
by Kiran Reddy 12 Aug '05

12 Aug '05

Hi, I would like to know the regex options equalent to the following .Net Reqular Expressions Options: ** *Multiline* ** Specifies multiline mode. Changes the meaning of *^* and *$* so that they match at the beginning and end, respectively, of any line, not just the beginning and end of the whole string. *ExplicitCapture* ** Specifies that the only valid captures are explicitly named or numbered groups of the form (?<*name*>…). This allows parentheses to act as noncapturing groups without the syntactic clumsiness of (?:…). ** *Singleline* ** Specifies single-line mode. Changes the meaning of the period character (.) so that it matches every character (instead of every character except *\n*). *IgnorePatternWhitespace* ** Specifies that unescaped white space is excluded from the pattern and enables comments following a number sign (#). (For a list of escaped white-space characters, see Character Escapes<ms-help://MS.MSDNQTR.2005JUL.1033/cpgenref/html/cpconcharacterescapes.htm>.) Note that white space is never eliminated from within a character class. Thanks in Advance. Regards Kiran

2 1

building an inofficial boost library
by martin f krafft 12 Aug '05

12 Aug '05

Hi boosters, I am trying to put John Torjo's wonderful logging library[0] to use. Unfortunately, it's not in boost yet, but I need it now already. How do I build it? Can I build it separately from an existing boost? 0. http://www.torjo.com/code/logging.zip I found that I can unzip the file over boost 1.33 and bjam will automatically build it. However, there are a couple of problems with it, specifically with the generated library files: - the SONAME of the libraries will be 1.33.0. I don't think this is appropriate since the library is not in 1.33.0. I'd rather use an SONAME of 0.0.20050801. How can I tell bjam to use this as an SONAME for just libs/log ? - The filename includes 1.33.0 as well: libboost_log-gcc-mt-1_33_0.so How can I change this to 0_0_22050801 ? - The static libraries include a "s" in the name to indicate they are static: libboost_log-gcc-mt-s-0_0_20050801.a None of the other boost libraries on my Debian system include this 's', and the Debian package build script just does not deal well (I'd like to make a package since I need it on multiple machines). How can I prevent the 's' from being put in there? I appreciate any help! And thanks to John for this nice library! -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck invalid/expired pgp (sub)keys? use subkeys.pgp.net as keyserver! spamtraps: madduck.bogus(a)madduck.net "zwei monologe, die sich gegenseitig immer und immer wieder störend unterbrechen, nennt man eine diskussion." -- charles tschopp

1 0

Boost 1.33.0 released
by Doug Gregor 12 Aug '05

12 Aug '05

Boost 1.33.0 ------------ New Libraries * Iostreams Library: Framework for defining streams, stream buffers and i/o filters, from Jonathan Turkanis. * Functional/Hash Library: A TR1 hash function object that can be extended to hash user defined types, from Daniel James. * Parameter Library: Write functions that accept arguments by name: especially useful when a function has more than one argument with a useful default value, since named arguments can be passed in any order. * Pointer Container Library: Containers for storing heap-allocated polymorphic objects to ease OO-programming, from Thorsten Ottosen. * Wave: Standards conformant implementation of the mandated C99/C++ preprocessor functionality packed behind an easy to use iterator interface, from Hartmut Kaiser. Updated Libraries * Assignment Library: Support for Pointer Container Library and new efficient functions ref_list_of() and cref_list_of() for generating anonymous ranges. * Bind Library: Bind expressions now support comparisons and negation. Example: bind(&X::name, _1) < bind(&X::name, _2). * Date-Time Library: o Added local time and time zone classes. o Added format-based Input/Output facets. o For a complete list of changes, see the library change history. * Graph Library: Introduced several new algorithms and improved existing algorithms: o Experimental Python bindings, from Doug Gregor and Indiana University. o floyd_warshall_all_pairs_shortest_paths, from Lauren Foutz and Scott Hill. o astar_search, from Kristopher Beevers and Jufeng Peng. o fruchterman_reingold_force_directed_layout, from Doug Gregor and Indiana University. o biconnected_components and articulation_points, from Jeremy Siek, Janusz Piwowarski, and Doug Gregor. o sequential_vertex_coloring has been updated, tested, and documented. o gursoy_atun_layout, from Jeremiah Willcock and Doug Gregor of Indiana University. o king_ordering, from D. Kevin McGrath of Indiana University. o cuthill_mckee ordering has been recast as an invocation of breadth_first_search and now supports graphs with multiple components. o dijkstra_shortest_paths now uses a relaxed heap as its priority queue, improving its complexity to O(V log V) and improving real-world performance for larger graphs. o read_graphviz now has a new, Spirit-based parser that works for all graph types and supports arbitrary properties on the graph, from Ron Garcia. The old, Bison-based GraphViz reader has been deprecated and will be removed in a future Boost release. write_graphviz also supports dynamic properties. o subgraph: get_property now refers to the subgraph property, not the root graph's property. o See the history for additional changes and bug fixes. * Multi-index Containers Library: o New hashed indices. o Added serialization support. o For a complete list of changes, see the library release notes. * Program Options Library: o Option descriptions are now printed with word wrapping. o Command line parser can bypass unregistered options, instead of throwing. o Removed support for "implicit" (optional) values. o New customization method 'command_line_parser::extra_style_parser'. Unlike 'additional_parser', allows the user to parse several tokens and return a vector of options, not just a single option. o Work with disabled exceptions. * Property Map Library: Introduced the dynamic properties class, which provides dynamically-typed access to a set of property maps. * Random Number Library: improved initialization for mersenne_twister, algorithm by Makoto Matsumoto and Takuji Nishimura, implemented for Boost by Jens Maurer. Note: All test vectors for mersenne_twisters constructed or seeded without parameters or with a single unsigned int parameter become invalid. * Range Library: Minor addition of convenience functions to iterator range like front(), back() and operator[](). * Regex Library: o Rewritten front end parser now supports (?imsx-imsx) constructs, plus lookbehind assertions and conditional expressions. o Thin wrapper classes improve integration with MFC/ATL code. o Full (optional) Unicode support via the ICU library. Refer to the regex history page for more information on these and other small changes. * Serialization Library: o DLL version. o Auto-linking. o Serialization of variants. o Improved seialization of shared pointers. * Signals Library: added slot blocking/unblocking, from Frantz Maerten. Huge improvements to signal invocation performance from Robert Zeh. Supported Compilers Boost is tested on a wide range of compilers and platforms. Since Boost libraries rely on modern C++ features not available in all compilers, not all Boost libraries will work with every compiler. The following compilers and platforms have been extensively tested with Boost, although many other compilers and platforms will work as well. For more information, see the regression test results. * Apple GCC 3.x on Mac OS X. * Borland C++ 5.6.4 on Windows. * GNU C++ 2.95.3 (with and without STLport), 3.2.x., 3.3.x, 3.4.x, 4.0.x on Windows, Linux and Solaris. * Intel C++ 8.1, 9.0 on Windows, Linux. * Metrowerks CodeWarrior 8.3, 9.4, 9.5 on Mac OS X and Windows. * Microsoft Visual C++ 6.0 (sp5, with and without STLport), 7.0, 7.1, 8.0 beta. Note: due to intermittent problems with Visual C++ 8.0 beta, and the presence of a variety of pre-release compiler builds, we are unable to guarantee compatibility until the final compiler is released. Acknowledgements Douglas Gregor managed this release. A great number of people contributed their time and expertise to make this release possible. Special thanks go to Aleksey Gurtovoy and Misha Bergal, who managed to keep the regression testing system working throughout the release process; David Abrahams, Beman Dawes, Aleksey Gurtovoy, Rene Rivera and Jonathan Turkanis for greatly improving the quality of this release; Rene Rivera for the new Boost web page design; and Zoltan "cad" Juhasz for the new Boost logo.

1 0

Auto unit test suite hangs due to locked mutex
by Richard Newman 12 Aug '05

12 Aug '05

I have searched the net for some indication of what I might be dealing with but have come up empty. This is on a Fedora Core 2 system running GCC 3.3.3. Boost was installed via RPM: # rpm -q boost boost-1.32.0-3.1.2 # I have a reasonably small auto unit test suite via Boost with 48 small discrete tests. It has been running fine previously. There are no tests that are known to invoke mutexes, Boost or otherwise. When we previously built Boost manually, this was not an issue; we're now trying to use the standard RPMs to make distribution/release building simpler. There is possibly an issue in how we're linking to libraries in our automake since those had to be changed to use the RPM installed libraries rather than our previously home-built ones. However, the make (compile, link, etc.) throws no errors, etc., and so we have no indication other than this hang that this is indeed where the problem lies. I had these make files, etc. working fine on a similarily installed system that instead ran FC4 with gcc 4.0.1 and Boost was installed as an RPM but at boost-1.32.0-6. When I copied to the FC2 system and set it up, I now see the issue. The lone symptom is that the test suite seems to complete but then hangs afterwards, apparently deadlocked on a mutex. When I run the test program under --log_level=all, I get the following output: ------------ $ mytestsuite --log_level=all Running 48 test cases... Entering test suite "Auto Unit Test" Entering test case "CounterConstruction" [...specific test output...] Leaving test case "CounterConstruction" [...more test cases...] Entering test case "DataNodeEqualityTest" [...specific test output...] Leaving test case "DataNodeEqualityTest" Leaving test suite "Auto Unit Test" *** No errors detected -------------- ...and then it just hangs without returning to the command line until I ctrl-C. When I run it under gdb to get a stack trace, I get the following session: -------------- $ libtool gdb mytestsuite *** Warning: inferring the mode of operation is deprecated. *** Future versions of Libtool will require -mode=MODE be specified. GNU gdb Red Hat Linux (6.0post-0.20040223.19rh) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db library "/lib/tls/libthread_db.so.1". (gdb) run Starting program: /home/build/<ourpath>/.libs/lt-mytestsuite Error while mapping shared library sections: : Success. Error while reading shared library symbols: : No such file or directory. [Thread debugging using libthread_db enabled] [New Thread -150709728 (LWP 13105)] Error while reading shared library symbols: : No such file or directory. Error while reading shared library symbols: : No such file or directory. Running 48 test cases... *** No errors detected Program received signal SIGINT, Interrupt. [Switching to Thread -150709728 (LWP 13105)] 0x00272402 in ?? () (gdb) backtrace #0 0x00272402 in ?? () #1 0x0064dcbe in __lll_mutex_lock_wait () from /lib/tls/libpthread.so.0 #2 0x0064ac84 in _L_mutex_lock_29 () from /lib/tls/libpthread.so.0 #3 0x00000000 in ?? () (gdb) quit The program is running. Exit anyway? (y or n) y $ -------------- Finally, a library listing for the test suite executable gives the following: -------------- $ ldd ./.libs/mytestsuite linux-gate.so.1 => (0x001fb000) mylibrary.0 => not found [...related to libtool use?] libxslt.so.1 => /usr/lib/libxslt.so.1 (0x03ec2000) libxml2.so.2 => /usr/lib/libxml2.so.2 (0x03a8c000) libpthread.so.0 => /lib/tls/libpthread.so.0 (0x00644000) libz.so.1 => /usr/lib/libz.so.1 (0x00557000) libxmlwrapp.so.5 => /home/build/<somepath>/dep/lib/libxmlwrapp.so.5 (0x00dcc000) libboost_unit_test_framework.so.1 => /usr/lib/libboost_unit_test_framework.so.1 (0x003bf000) libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x0080c000) libm.so.6 => /lib/tls/libm.so.6 (0x0052c000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00763000) libc.so.6 => /lib/tls/libc.so.6 (0x0040f000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x003f2000) $ -------------- Any advice to proceed and repair? We'd like very much to be able to use these RPMs than reverting back to our previous homegrown approach. Thank you and kind regards, Richard Newman Crowley Davis Research, Inc.

2 5