May 2005 - Boost - lists.boost.org

octonion_test and quaternion_test failures on Intel 8.1/Windows
by Beman Dawes 31 May '05

31 May '05

Both octonion_test.cpp and quaternion_test.cpp, at about line 94, contain the following: // Provide standard floating point abs() overloads for MSVC //#if BOOST_WORKAROUND(BOOST_MSVC, < 1300) || (defined(_MSC_EXTENSIONS) && BOOST_MSVC < 1310) That looks like a workaround for the fact that prior to VC++ 7.1, the Microsoft C library did not define abs(float) etc. if _MSC_EXTENSIONS was defined. The Intel compiler uses the Microsoft libraries, and defines _MSC_EXTENSIONS, but of course BOOST_MSVC is not defined. That causes the workaround code to be included, resulting in multiple definitions, if the Microsoft library 1310 (7.1) or later is being used. I believe the corrected code should read: // Provide standard floating point abs() overloads if older Microsoft // library is used with _MSC_EXTENSIONS defined. This code also works // for the Intel compiler using the Microsoft library. #if defined(_MSC_EXTENSIONS) && defined(_MSC_VER) && _MSC_VER < 1310 I've committed this change to CVS for both source files on the assumption that this suits the library maintainer. If not, or there is something wrong with the fix, please feel free to revert the changes. --Beman

3 2

Problem with serialization mersenne_twister with cvs
by Neal Becker 31 May '05

31 May '05

This used to work with 1.32.0, but is failing with cvs. In mersenne_twister.hpp, I add template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & x; ar & i; } Now compile: g++4 -g -DNDEBUG -O3 -ftree-vectorize -msse2 -ffast-math -fstrict-aliasing -Wall -fPIC -I/usr/local/src/boost.cvs -I/usr/include/python2.4 -I/home/\ nbecker/shannon2.darcs/src -c -o boost_rand.os boost_rand.cc /usr/local/src/boost.cvs/boost/archive/detail/oserializer.hpp: In function 'void boost::archive::save(Archive&, T&) [with Archive = boost::archive:\ :binary_oarchive, T = boost::random::mersenne_twister<uint32_t, 32, 624, 397, 31, 2567483615u, 11, 7, 2636928640u, 15, 4022730752u, 18, 3346425566u\ >]': /usr/local/src/boost.cvs/boost/archive/basic_binary_oarchive.hpp:69: instantiated from 'void boost::archive::basic_binary_oarchive<Archive>::save\ _override(T&, int) [with T = boost::random::mersenne_twister<uint32_t, 32, 624, 397, 31, 2567483615u, 11, 7, 2636928640u, 15, 4022730752u, 18, 3346\ 425566u>, Archive = boost::archive::binary_oarchive]' /usr/local/src/boost.cvs/boost/archive/binary_oarchive.hpp:47: instantiated from 'void boost::archive::binary_oarchive_impl<Archive>::save_overri\ de(T&, int) [with T = boost::random::mersenne_twister<uint32_t, 32, 624, 397, 31, 2567483615u, 11, 7, 2636928640u, 15, 4022730752u, 18, 3346425566u\ >, Archive = boost::archive::binary_oarchive]' /usr/local/src/boost.cvs/boost/archive/detail/interface_oarchive.hpp:89: instantiated from 'Archive& boost::archive::detail::interface_oarchive<A\ rchive>::operator<<(T&) [with T = boost::random::mersenne_twister<uint32_t, 32, 624, 397, 31, 2567483615u, 11, 7, 2636928640u, 15, 4022730752u, 18,\ 3346425566u>, Archive = boost::archive::binary_oarchive]' boost_rand.cc:41: instantiated from here /usr/local/src/boost.cvs/boost/archive/detail/oserializer.hpp:557: error: invalid application of 'sizeof' to incomplete type 'boost::STATIC_ASSERTI\ ON_FAILURE<false>'

4 6

[iostream] Odd errors on build from BOOST_ROOT
by Jeff Garland 31 May '05

31 May '05

I got some weird errors out of iostreams that look like it's complaining about the serialization lib files? This only happened when I compiled from BOOST_ROOT -- everything was fine when I compile from iostreams/build. I'm assuming this is some sort of Jamfile issue... This was a fresh CVS checkout as of this morning -- built on Linux. Jeff ----- MkDir1 bin/boost/libs/iostreams/build/libboost_iostreams.so MkDir1 bin/boost/libs/iostreams/build/libboost_iostreams.so/gcc MkDir1 bin/boost/libs/iostreams/build/libboost_iostreams.so/gcc/release MkDir1 bin/boost/libs/iostreams/build/libboost_iostreams.so/gcc/release/shared-linkable-true ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>basic_archive.o for lack of <@boost!libs!iostreams!build>basic_archive. cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>basic_iarchive.o for lack of <@boost!libs!iostreams!build>basic_iarchiv e.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>basic_oarchive.o for lack of <@boost!libs!iostreams!build>basic_oarchiv e.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>basic_iserializer.o for lack of <@boost!libs!iostreams!build>basic_iser ializer.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>basic_oserializer.o for lack of <@boost!libs!iostreams!build>basic_oser ializer.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>basic_pointer_iserializer.o for lack of <@boost!libs!iostreams!build>ba sic_pointer_iserializer.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>basic_pointer_oserializer.o for lack of <@boost!libs!iostreams!build>ba sic_pointer_oserializer.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>basic_serializer_map.o for lack of <@boost!libs!iostreams!build>basic_s erializer_map.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>basic_text_iprimitive.o for lack of <@boost!libs!iostreams!build>basic_ text_iprimitive.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>basic_text_oprimitive.o for lack of <@boost!libs!iostreams!build>basic_ text_oprimitive.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>basic_xml_archive.o for lack of <@boost!libs!iostreams!build>basic_xml_ archive.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>binary_iarchive.o for lack of <@boost!libs!iostreams!build>binary_iarch ive.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>binary_oarchive.o for lack of <@boost!libs!iostreams!build>binary_oarch ive.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>extended_type_info.o for lack of <@boost!libs!iostreams!build>extended_ type_info.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>extended_type_info_no_rtti.o for lack of <@boost!libs!iostreams!build>e xtended_type_info_no_rtti.cpp...

3 5

Patch for BOOST_OLD_IOSTREAMS detection
by Matthias Troyer 31 May '05

31 May '05

Hi, Several places in Boost try to detect BOOST_OLD_IOSTREAMS using the following ifdefs: // support for pre 3.0 libstdc++ - thanks Phil Edwards! #if defined (__STL_CONFIG_H) && !defined (__STL_USE_NEW_IOSTREAMS) # define BOOST_OLD_IOSTREAMS #endif This incorrectly defines BOOST_OLD_IOSTREAMS for the Cray X1 C++ compiler. Could this be changed to include an && !defined(__crayx1) or something similar as in: #if defined (__STL_CONFIG_H) && !defined (__STL_USE_NEW_IOSTREAMS) && !defined(__crayx1) # define BOOST_OLD_IOSTREAMS #endif Three offending files are: boost/dynamic_bitset/config.hpp boost/range/iterator_range.hpp libs/dynamic_bitset/example/timing_tests.cpp Maybe it would be best to move this to the global config file? Best regards Matthias

3 4

[BGL] Comparison with LEDA
by Sylvain Pion 31 May '05

31 May '05

You may find this comparison with some LEDA graph algorithms interesting : http://www.algorithmic-solutions.com/leda-outperforms-boost.htm -- Sylvain

1 0

[gauging interest] Windows GUI - semi-installer
by Pablo Aguilar 30 May '05

30 May '05

Hi, After reading the "Customer Friendlier Boost Installation" thread, I've now enough motivation to get into this... I've been planning a boost GUI semi-installer, but hadn't gotten around to it due to lack of time. I call it "semi" in the sense that it wouldn't be the typical "wizard like" installer everyone's used to, but rather a configuring utility for (at least) the IDEs I'm familiar with. Here's what I thought it should do: 1) Register include/lib directories with VCx 2) Don't know how yet, but try the same with BCB (as I think it's on a per-project basis, rather than global settings like VC) 3) Allow building of libraries which require it, with the following options: - Which compiler(s) to use? - Which configuration (debug/threading/static/etc) for each compiler? I believe that detecting which libraries need building would just be a matter of searching for a "build" subdirectory within a given library's directory. Don't know about configurations, though, maybe some simple parsing of the jamfiles would do.. The reason I chose not to do it as an installer, is because I'm far more comfortable with developing GUIs with say, BCB, than I am with the installer programs I've tried. Comments, suggestions, requests are welcome. Pablo Aguilar

5 18

[range] Borland and GCC-2.95 workarounds for iostreams
by Jonathan Turkanis 30 May '05

30 May '05

Hi Thorsten, I made two changes to range, which should only affect gcc-2.95 and Borland: - in begin.hpp and end.hpp I applied some of the Borland workarounds to gcc-2.95 as well - in iterator_range.hpp, I removed some Borland workarounds which were causing iostreams to fail on Borland, and which did not seem to be necessary. The same tests passed with and without the workarounds. Jonathan

2 6

[Typeof] Formal Review in progress
by Andy Little 30 May '05

30 May '05

Hi All, A reminder that the Typeof Formal Review is currently in progress and runs until May 30th. So far there have been only two reviews, both in favour of the library. (Thanks again to both those reviewers for their time and energy). Nevertheless it would be nice to get some more opinion, affirmation , etc regarding this important library. One area in particular that has been cited as worthy of improvement is the documentation, so please download the library and take a look at it. (And then write a review ;-) ) Are there enough examples? Is there enough information regarding how to use the library. Is it workable in a large project?. is the effect on compile time a problem.? etc. I'm sure that Arkadiy and Peder would welcome feedback on the documentation in particular so that they can improve it. So please try to find time to write a review. The proposed Typeof library emulates the functionality of the non-standard 'typeof' operator, and incomplete implementations of decltype and the proposed 'auto' declarator , described in http://www.osl.iu.edu/~jajarvi/publications/papers/decltype_n1478.pdf. It is commonly acknowledged that this type of functionality is sorely needed and should be standardardised in the language. For compliant compilers the library requires some help in the form of registration macros but, because use of typeof is by its nature most likely in generic libraries, it is expected that this can often be done by the library author rather than the user. In some cases the compilers capabilities (by means of extensions and even compiler bugs) have been used to remove the need for registration. However, for portability and in order to test emulation mode on the compilers where it is available but not used by default (VC7.1, GCC etc), #define BOOST_TYPEOF_COMPLIANT [see note *1*]. Testing the emulation is useful, even on compilers that provide a better option, to get a rounded view of the library and its capabilities. I hope you will find time to write a review of the library, which is available at: http://boost-sandbox.sourceforge.net/vault/ , typeof.zip The system has been tested with the following compilers: MSVC 6.5/7.0/7.1/8.0; [see note *1* regarding VC7.0 and VC6.5] GCC 3.4.2 (The following is a quote from : http://www.boost.org/more/formal_review_process.htm ) Here are some questions you might want to answer in your review: What is your evaluation of the design? What is your evaluation of the implementation? What is your evaluation of the documentation? What is your evaluation of the potential usefulness of the library? Did you try to use the library? With what compiler? Did you have any problems? How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? Are you knowledgeable about the problem domain? And finally, every review should answer this question: Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. Andy Little Typeof review manager notes: *1* MSVC6.5 and VC7.0 are not supported by the BOOST_TYPEOF_COMPLIANT macro

6 34

Typeof: Formal Review period ended
by Andy Little 30 May '05

30 May '05

Hi, The Typeof formal review period is closed. Thanks to all those that participated in the review. Thanks also to Tom Brinkman, the review Wizard. I hope to provide a more detailed summary of the review shortly, meanwhile I am happy to say that the Typeof library has been accepted into boost. regards Andy Little

1 0

Yet another quickbook question
by Arkadiy Vertleyb 30 May '05

30 May '05

Hi all, How do I generate the document-level index in the quickbook? Right now it generates indexes for those sections that contain subsections, but not the top-level index. Regards, Arkadiy

3 4