June 2004 - Boost - lists.preview.boost.org

Borland settings different between Boost and IDE ?
by Nicola Musatti 03 Jun '04

03 Jun '04

Hallo, is it possible that Boost libraries use a different setting for enum handling than the BCB IDE default one? I'm having problems which seem related to enums and the inclusion of some Boost headers in precompiled headers. Cheers, Nicola Musatti

2 2

[program_options] Darwin failure help?
by Vladimir Prus 03 Jun '04

03 Jun '04

The program options library now fails a single test on Darwin, with this output: ../libs/program_options/test/parsers_test.cpp(205): fatal error in "call_test_main": test p.options.size() == 1 failed *** 1 failure detected in test case "call_test_main" The code in question is: putenv("PO_TEST_FOO=1"); parsed_options p = parse_environment(desc, "PO_TEST_"); BOOST_REQUIRE(p.options.size() == 1); So, it seems that after "putenv", the string is is not available in the 'environ' variable. The variable is declared like this: #if defined(__APPLE__) && defined(__DYNAMIC__) #include <crt_externs.h> static char** environ = *_NSGetEnviron(); #else extern char** environ; #endif The Darwin-specific conditinal was sent by Michael LaSpina, so I don't know what it really does, and so don't know why the test fails. I'd appreciate any suggestions. Thanks in advance, Volodya

2 2

RE: [boost] Proposed Boost Library for Data Series Analysis
by Hurd, Matthew 02 Jun '04

02 Jun '04

> -----Original Message----- > Behalf Of Tom Brinkman > Subject: [boost] Proposed Boost Library for Data Series Analysis > > I placed a small tutorial and motivating example for > the proposed boost::data_series library. > > http://groups.yahoo.com/group/boost/files/data_series/ > > Working examples for you to criticize will be added > within the week. Cute code. Nice job. Efficiency is often paramount with these types of apps. Being able to do finite difference approaches, backwards and forwards, and in absolute terms is important (often you only want the latest data point). You have the incremental case covered in your notes. Being able to calculate it at a point in an absolute sense, optional caching of results, working with series of unknown lengths and accuracy / validity enabling would be nice too. By accuracy / validity enabling I mean, for say, your example of a 5 step moving average, it is not valid for the first four points as these are not an accurate average, so there is a length modification for the result. Another simple example would be an exponential moving average where the number of significant digits required will determine how far back you need to go in the series. At another level, quality of service for some functors, the fast or accurate spectrum, is often appropriate. Perhaps expression templates might help here. Compile time results for validity calcs for series of known lengths would be helpful where possible. It would be nice if the algorithms could be simply specified, similar to your approach, and then "mounted" into the appropriate framework. Perhaps SFINAE or another technique could be used to determine an algorithm's capabilities. That is, the framework could juggle the most appropriate methods to use based on the results required. E.g. use incremental if you can otherwise absolute. Based on what I've done the past you also end up wanting arbitrary n-dimensional structures with other data types flowing through as well. Being able to associate ids/names with data items and keeping them associated through sorting/ranking. E.g. tag the series with data codes, rank them, and you can get the code for the best. You also want grouping n dimensional constructs and splitting dimensions and "slicing" operators that operate across the current dimension, which, with the appropriate framework, are one in the same. E.g. choose the minimum or sum the results of a bunch of functions. Then soon you want to split the computation amongst processors and machines and you want treat the computation as a dataflow graph and parallelise it some way, which I did a few years ago with BGL's precursor the GGCL. A topological sort gets you most of the way there... Also, you can then use things like Metis to partition your computation graph in nice ways. I think a way approach it would be an expression template approach with some adaptability in terms of absolute and incremental analytics with some accuracy (at least something like the number of points being chewed up and not valid or some such). Everything else could come on top of this. You need to ensure that you can easily reuse code out there. No one wants to spend their life writing the zillions of numerical algorithms already out there. If you want a vector ARMA model, there are only a couple out there I think, and they are in FORTRAN, for example, wrap it, don't write it, I'd hope. You end up with run time versus compile time issues. People want to interact with this kind of stuff. However, my take on that now is do it at compile time and include the compiler as part of your interactive tools set if need be :-) Anyhow, it is nice to see a start on this. Good luck. $0.005, Matt Hurd. _______________ Matt Hurd +61.2.8226.5029 hurdm(a)sig.com Susquehanna _______________ IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.

1 0

Re:[boost] Re: Re: iostreams library review
by Robert Ramey 02 Jun '04

02 Jun '04

>> Question, have you tried to combine the streaming with boost >> serialization? > I think Robert Ramey has already done the work to combine serialization > with iostreams, since his archive types are constructible from arbitrary > streams -- that means it's already possible to create archives based on > streams from the iostreams library, e.g. memory-mapped file streams. > There may be other interactions I haven't considered. I've only read the > documentation; I haven't actually tried to use the serialization library > yet. The serialization library archives use streams and make no special assumptions regarding them. It works with all the streams I've happened to try. I will be taking a close look at the iostreams library proposal. In the course of implementing the serialization library I've had to become much more familiar with locales, facets, codecvt, element types, EOF, etc than I wanted to. Oh - and that fact that different versions of the standard library have myriad minor quirks that have to be considered. This was necessary in order to avoid dependence on the stream in the wrong way. I'm very interested in this but have come to the conclusion that there might be more here than meets the eye. - Of course that's why we have the review process. Robert Ramey

2 1

boost::optional - Include none.hpp instead of none_t.hpp?
by Schalk_Cronje＠NAI.com 02 Jun '04

02 Jun '04

Was it intentional to include none_t.hpp instead of none.hpp in boost/optional.hpp? Otherwise it seems that the user must resort to including boost/detail/none.hpp

3 3

thread, line endings
by Janusz Piwowarski 02 Jun '04

02 Jun '04

Hello In files: libs/thread/src/mutex.cpp libs/thread/src/recursive_mutex.cpp libs/thread/src/mutex.inl boost/thread/mutex.hpp boost/thread/recursive_mutex.hpp there is CR+CR+LF used as line separator. Also, in recursive_mutex constructor if defined(BOOST_HAS_WINTHREADS) m_critical_section should be initialized before m_count (it's compiler warning) Regards, Janusz

3 4

New utility at boost/detail/allocator.hpp
by Joaquín Mª López Muñoz 02 Jun '04

02 Jun '04

Hi all, As requested by some at the mailing list, I've migrated allocator.hpp from boost/multi_index/detail/ to boost/detail/ (with some obvious namespace changes.) I'd like to remark the following: * This allocator.hpp has nothing to do with a header of the same name who was sitting there and John Maddock kindly removed a few days ago. * The header provides some utilities to do rebinding of allocators even in MSVC++ 6.0 (where the std syntax for rebind does not work), and also exposes a tiny wrapper over defective std::allocators, providing some missing template members to make them std compliant. * I'd appreciate if those of you who were originally interested in using this header can do some sanity checks to make sure everything works for you (it does for Boost.MultiIndex). We have some room for improvements and fixes until Boost 1.32 is branched for release. Best, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

3 3

RE: [boost] Re: Re: BOOST_READONLY_PROPERTY macro
by Rozental, Gennadiy 02 Jun '04

02 Jun '04

> Can you just please tell me what BOOST_READONLY_PROPERTY ( > bool, (epv) ) > will become once it is preprocessed ? Something like this: class readonly_property123 : public boost::unit_test::readonly_property<bool> { typedef boost::unit_test::readonly_property<bool> base; friend class epv; // <-- here BOOST_PP is used typedef base::write_param_t write_param_t; public: readonly_property123() {} explicit readonly_property123( write_param_t init_v ) : base( init_v ) {} } > > P.S. Paul should know the answer > I don't think Paul knows about _all_ libraries that _use_ the > PP library. This has something to do with specific compiler bug in regards of PP.

1 0

Test failure for basic_cstring_test
by Martin Wille 02 Jun '04

02 Jun '04

Hello, basic_cstring_test fails on gcc-3.2.3 in a way that causes the test post processing to fail, too. The basic_cstring_test related lines from the log file are appended to this message. The full log for gcc-3.2.3-linux can be found at http://tinyurl.com/34ltq Regression log post processing fails with this message: **** exception(205): std::exception: boost::filesystem::path: invalid name "basic_cstring_test.o(.gnu.linkonce.t._Z17constructors_testIhEvPT_+0x757):.." in path: "bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._Z17constructors_testIhEvPT_+0x757):../libs/test/test" ******** errors detected; see standard output for details ******** Regards, m gcc-C++-action ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o /boost/head-regression/boost/boost/test/test_tools.hpp: In function `bool boost::test_tools::detail::equal_and_continue_impl(const Left&, const Right&, boost::wrap_stringstream&, boost::unit_test::basic_cstring<const char>, unsigned int, boost::unit_test::log_level, unsigned int) [with Left = size_t, Right = int]': ../libs/test/test/basic_cstring_test.cpp:82: instantiated from `void constructors_test(CharT*) [with CharT = wchar_t]' ../libs/test/test/basic_cstring_test.cpp:124: instantiated from `static void meta_constructors_test::execute(T*) [with T = wchar_t]' /boost/head-regression/boost/boost/test/test_case_template.hpp:60: instantiated from `void boost::unit_test::detail::test_case_template_instance<TestCaseTemplate, TestType>::do_run() [with TestCaseTemplate = meta_constructors_test, TestType = wchar_t]' /boost/head-regression/boost/boost/utility/value_init.hpp:49: instantiated from here /boost/head-regression/boost/boost/test/test_tools.hpp:430: warning: comparison between signed and unsigned integer expressions gcc-Link-action ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._Z17constructors_testIhEvPT_+0x657): In function `void find_test<char const>(char const*)': ../libs/test/test/basic_cstring_test.cpp:470: undefined reference to `std::char_traits<unsigned char>::compare(unsigned char const*, unsigned char const*, unsigned)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._Z17constructors_testIhEvPT_+0x757):../libs/test/test/basic_cstring_test.cpp:368: undefined reference to `std::char_traits<unsigned char>::length(unsigned char const*)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._Z17constructors_testIhEvPT_+0x8ac):../libs/test/test/basic_cstring_test.cpp:432: undefined reference to `std::char_traits<unsigned char>::compare(unsigned char const*, unsigned char const*, unsigned)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._Z17constructors_testIhEvPT_+0xa1a):../libs/test/test/basic_cstring_test.cpp:433: undefined reference to `std::char_traits<unsigned char>::compare(unsigned char const*, unsigned char const*, unsigned)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._Z17constructors_testIhEvPT_+0xb93):../libs/test/test/basic_cstring_test.cpp:480: undefined reference to `std::char_traits<unsigned char>::compare(unsigned char const*, unsigned char const*, unsigned)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._Z16data_access_testIhEvPT_+0xb8): In function `void data_access_test<unsigned char>(unsigned char*)': /boost/head-regression/boost/boost/test/detail/basic_cstring/basic_cstring.hpp:539: undefined reference to `std::char_traits<unsigned char>::compare(unsigned char const*, unsigned char const*, unsigned)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._Z16data_access_testIhEvPT_+0x1e7): In function `void data_access_test<unsigned char>(unsigned char*)': /boost/head-regression/boost/boost/test/test_tools.hpp:446: undefined reference to `std::char_traits<unsigned char>::compare(unsigned char const*, unsigned char const*, unsigned)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._Z14asignment_testIhEvPT_+0xea):/usr/local/gcc-3.2.3/include/c++/3.2.3/bits/basic_string.tcc:155: more undefined references to `std::char_traits<unsigned char>::compare(unsigned char const*, unsigned char const*, unsigned)' follow ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._Z17constructors_testIKhEvPT_+0x757): In function `void find_test<char const>(char const*)': ../libs/test/test/basic_cstring_test.cpp:368: undefined reference to `std::char_traits<unsigned char>::length(unsigned char const*)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._Z17constructors_testIKhEvPT_+0x8ac):../libs/test/test/basic_cstring_test.cpp:432: undefined reference to `std::char_traits<unsigned char>::compare(unsigned char const*, unsigned char const*, unsigned)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._Z17constructors_testIKhEvPT_+0xa1a):../libs/test/test/basic_cstring_test.cpp:433: undefined reference to `std::char_traits<unsigned char>::compare(unsigned char const*, unsigned char const*, unsigned)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._Z17constructors_testIKhEvPT_+0xb93):../libs/test/test/basic_cstring_test.cpp:480: undefined reference to `std::char_traits<unsigned char>::compare(unsigned char const*, unsigned char const*, unsigned)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._Z23constructors_const_testIKhEvPT_+0x114): In function `void constructors_const_test<unsigned char const>(unsigned char const*)': ../libs/test/test/basic_cstring_test.cpp:195: undefined reference to `std::char_traits<unsigned char>::compare(unsigned char const*, unsigned char const*, unsigned)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._Z20asignment_const_testIKhEvPT_+0x11f): In function `void asignment_const_test<unsigned char const>(unsigned char const*)': /usr/local/gcc-3.2.3/include/c++/3.2.3/bits/basic_string.tcc:160: undefined reference to `std::char_traits<unsigned char>::compare(unsigned char const*, unsigned char const*, unsigned)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._Z20asignment_const_testIKhEvPT_+0x258):../libs/test/test/basic_cstring_test.cpp:353: more undefined references to `std::char_traits<unsigned char>::compare(unsigned char const*, unsigned char const*, unsigned)' follow ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._ZN5boost9unit_test13basic_cstringIhEC1EPh+0x37): In function `boost::unit_test::basic_cstring<unsigned char>::basic_cstring[in-charge](unsigned char*)': /boost/head-regression/boost/boost/detail/shared_count.hpp:150: undefined reference to `std::char_traits<unsigned char>::length(unsigned char const*)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._ZN5boost9unit_testltIhEEbRKNS0_13basic_cstringIT_EES6_+0x7c): In function `bool boost::unit_test::operator< <unsigned char>(boost::unit_test::basic_cstring<unsigned char> const&, boost::unit_test::basic_cstring<unsigned char> const&)': /boost/head-regression/boost/boost/test/detail/basic_cstring/compare.hpp:51: undefined reference to `std::char_traits<unsigned char>::compare(unsigned char const*, unsigned char const*, unsigned)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._ZNK5boost9unit_test13basic_cstringIhE4findES2_+0xab): In function `boost::unit_test::basic_cstring<unsigned char>::find(boost::unit_test::basic_cstring<unsigned char>) const': ../libs/test/test/basic_cstring_test.cpp:329: undefined reference to `std::char_traits<unsigned char>::compare(unsigned char const*, unsigned char const*, unsigned)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._ZN5boost9unit_test13basic_cstringIhE10trim_rightES2_+0x8d): In function `boost::unit_test::basic_cstring<unsigned char>::trim_right(boost::unit_test::basic_cstring<unsigned char>)': ../libs/test/test/basic_cstring_test.cpp:260: undefined reference to `std::char_traits<unsigned char>::find(unsigned char const*, unsigned, unsigned char const&)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._ZN5boost9unit_test13basic_cstringIhE9trim_leftES2_+0x8b): In function `boost::unit_test::basic_cstring<unsigned char>::trim_left(boost::unit_test::basic_cstring<unsigned char>)': /boost/head-regression/boost/boost/detail/shared_count.hpp:345: undefined reference to `std::char_traits<unsigned char>::find(unsigned char const*, unsigned, unsigned char const&)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._ZNK5boost9unit_test13basic_cstringIhE5rfindES2_+0xab): In function `boost::unit_test::basic_cstring<unsigned char>::rfind(boost::unit_test::basic_cstring<unsigned char>) const': ../libs/test/test/basic_cstring_test.cpp:329: undefined reference to `std::char_traits<unsigned char>::compare(unsigned char const*, unsigned char const*, unsigned)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._ZN5boost9unit_test13basic_cstringIKhEC1EPS2_+0x37): In function `boost::unit_test::basic_cstring<unsigned char const>::basic_cstring[in-charge](unsigned char const*)': /boost/head-regression/boost/boost/detail/shared_count.hpp:150: undefined reference to `std::char_traits<unsigned char>::length(unsigned char const*)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._ZNSbIhSt11char_traitsIhESaIhEEC1EPKhRKS1_+0x13): In function `std::basic_string<unsigned char, std::char_traits<unsigned char>, std::allocator<unsigned char> >::basic_string[in-charge](unsigned char const*, std::allocator<unsigned char> const&)': /boost/head-regression/boost/boost/test/detail/basic_cstring/basic_cstring.hpp:531: undefined reference to `std::char_traits<unsigned char>::length(unsigned char const*)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._ZN5boost9unit_testltIKhEEbRKNS0_13basic_cstringIT_EES7_+0x7c): In function `bool boost::unit_test::operator< <unsigned char const>(boost::unit_test::basic_cstring<unsigned char const> const&, boost::unit_test::basic_cstring<unsigned char const> const&)': /boost/head-regression/boost/boost/test/detail/basic_cstring/compare.hpp:51: undefined reference to `std::char_traits<unsigned char>::compare(unsigned char const*, unsigned char const*, unsigned)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._ZNK5boost9unit_test13basic_cstringIKhE4findES3_+0xab): In function `boost::unit_test::basic_cstring<unsigned char const>::find(boost::unit_test::basic_cstring<unsigned char const>) const': ../libs/test/test/basic_cstring_test.cpp:329: undefined reference to `std::char_traits<unsigned char>::compare(unsigned char const*, unsigned char const*, unsigned)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._ZN5boost9unit_test13basic_cstringIKhE10trim_rightES3_+0x8d): In function `boost::unit_test::basic_cstring<unsigned char const>::trim_right(boost::unit_test::basic_cstring<unsigned char const>)': ../libs/test/test/basic_cstring_test.cpp:260: undefined reference to `std::char_traits<unsigned char>::find(unsigned char const*, unsigned, unsigned char const&)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._ZN5boost9unit_test13basic_cstringIKhE9trim_leftES3_+0x8b): In function `boost::unit_test::basic_cstring<unsigned char const>::trim_left(boost::unit_test::basic_cstring<unsigned char const>)': /boost/head-regression/boost/boost/detail/shared_count.hpp:345: undefined reference to `std::char_traits<unsigned char>::find(unsigned char const*, unsigned, unsigned char const&)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._ZNK5boost9unit_test13basic_cstringIKhE5rfindES3_+0xab): In function `boost::unit_test::basic_cstring<unsigned char const>::rfind(boost::unit_test::basic_cstring<unsigned char const>) const': ../libs/test/test/basic_cstring_test.cpp:329: undefined reference to `std::char_traits<unsigned char>::compare(unsigned char const*, unsigned char const*, unsigned)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._ZN5boost9unit_testeqIhhEEbRKNS0_13basic_cstringIT_EERKNS2_IT0_EE+0x5c): In function `bool boost::unit_test::operator==<unsigned char, unsigned char>(boost::unit_test::basic_cstring<unsigned char> const&, boost::unit_test::basic_cstring<unsigned char> const&)': /boost/head-regression/boost/boost/test/test_tools.hpp:434: undefined reference to `std::char_traits<unsigned char>::compare(unsigned char const*, unsigned char const*, unsigned)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._ZNKSbIhSt11char_traitsIhESaIhEE5c_strEv+0x2e): In function `std::basic_string<unsigned char, std::char_traits<unsigned char>, std::allocator<unsigned char> >::c_str() const': /usr/local/gcc-3.2.3/include/c++/3.2.3/bits/stl_algobase.h:240: undefined reference to `std::char_traits<unsigned char>::assign(unsigned char&, unsigned char const&)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._ZN5boost9unit_testeqIKhS2_EEbRKNS0_13basic_cstringIT_EERKNS3_IT0_EE+0x5c): In function `bool boost::unit_test::operator==<unsigned char const, unsigned char const>(boost::unit_test::basic_cstring<unsigned char const> const&, boost::unit_test::basic_cstring<unsigned char const> const&)': /boost/head-regression/boost/boost/test/test_tools.hpp:434: undefined reference to `std::char_traits<unsigned char>::compare(unsigned char const*, unsigned char const*, unsigned)' ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o(.gnu.linkonce.t._ZNSbIhSt11char_traitsIhESaIhEE13_S_copy_charsEPhPKhS5_+0x20): In function `std::basic_string<unsigned char, std::char_traits<unsigned char>, std::allocator<unsigned char> >::_S_copy_chars(unsigned char*, unsigned char const*, unsigned char const*)': /boost/head-regression/boost/boost/detail/shared_count.hpp:100: undefined reference to `std::char_traits<unsigned char>::copy(unsigned char*, unsigned char const*, unsigned)' collect2: ld returned 1 exit status set -e LD_LIBRARY_PATH=/usr/local/gcc-3.2.3/lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH "/usr/local/gcc-3.2.3/bin/g++wrap" --limit-memory=600 --limit-cpu=1800 -g -o "../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test" -L"../bin/boost/libs/test/build/libboost_unit_test_framework.a/gcc-3.2.3-linux/debug" -L"/usr/local/gcc-3.2.3/lib" "../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test.o" "../bin/boost/libs/test/build/libboost_unit_test_framework.a/gcc-3.2.3-linux/debug/libboost_unit_test_framework.a" "../bin/boost/libs/test/build/libboost_unit_test_framework.a/gcc-3.2.3-linux/debug/libboost_unit_test_framework.a" -Wl,-rpath-link,. ...failed gcc-Link-action ../bin/boost/libs/test/test/basic_cstring_test.test/gcc-3.2.3-linux/debug/basic_cstring_test... ...skipped <@boost!libs!test!test/basic_cstring_test.test/gcc-3.2.3-linux/debug>basic_cstring_test.run for lack of <@boost!libs!test!test/basic_cstring_test.test/gcc-3.2.3-linux/debug>basic_cstring_test...

4 6

port of library to vacpp (item 2)
by Toon Knapen 02 Jun '04

02 Jun '04

I stumble on another problem when trying to compile the test library with IBM/VisualAge (vacpp). Apparantly vacpp has a problem on lines 97,98 and 99 of boost/test/detail/basic_cstring/basic_cstring.hpp. Basically the problem is this: this file declares a class template < class CharT > class basic_string { public: typedef basic_string<CharT> self_type ; self_type& trim_left(self_type exclusions = self_type() ) ; // line 97 } ; If I now remove the default initializer, vacpp does not choke anymore (same situation on lines 98 and 99). I tried to isolate this problem in small test but in a small test vacpp seems to deal with the situation just fine. Thus AFAICT this is a compiler-bug but would anyone mind if I remove the default initializers or just remove them in the vacpp compilation to get one step closer to running the regression tests on vacpp again.

5 8

Proposed Boost Library for Data Series Analysis
by Tom Brinkman 02 Jun '04

02 Jun '04

I placed a small tutorial and motivating example for the proposed boost::data_series library. http://groups.yahoo.com/group/boost/files/data_series/ Working examples for you to criticize will be added within the week. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

3 2

RE: [boost] Re: BOOST_READONLY_PROPERTY macro
by Rozental, Gennadiy 02 Jun '04

02 Jun '04

> > BOOST_CLASS_PROPERTY is used like this: > > > > BOOST_CLASS_PROPERTY( int, (class1)(class2)...(classN) ) property; > > How is that relevant? Sorry supposed to be BOOST_READONLY_PROPERTY in both places. Gennadiy.

3 3

RE: [boost] Re: iostreams library review
by Brian Braatz 02 Jun '04

02 Jun '04

"""""""" > what is the fate of this library? Thanks for your interest! The previous version available at http://www.xmission.com/~turkanis/iostreams/. """""""""" I downloaded the library from the yahoo link you mentioned in the review request. When trying to use 'filtered_stream' I ran into some compilation issues (RedHat 9, g++ 3.3) and before looking into it I wanted to know the review status. Knowing that the library is in the review pipeline I will give it another try. Some time ago I developed simple iostream adapter 'library' that allows to wrap IO device (sockets, pipes, etc) in std::[i,o,io]stream that is very similar to your sink/source technique. One difference is that the adapter is a template class parameterized by the source/sink types. Since your library offers this functionality (plus much more) I am very pleased it will become part of boost soon. """""""""" A quick look your page is very interesting. (looks very cool) I was thinking (also) along the same lines for some work I am currently doing, but you beat me to it. Question, have you tried to combine the streaming with boost serialization?

2 1

Re: [boost] Re: static sized strings
by Reece Dunn 01 Jun '04

01 Jun '04

Rob Stewart wrote: >Subject: Re: [boost] Re: static sized strings >Date: Tue, 1 Jun 2004 17:13:38 -0400 (EDT) > >From: "Reece Dunn" <msclrhd(a)hotmail.com> > > John Nagle wrote: > > > I've done some cleanup on my version of fixed_string at > > > http://www.animats.com/source > > >[snip] > > > We're approaching convergence on this. > > > > We are both working on variations of the same idea. As such, I have >fixed > > several errors in my code making it operate better as a basic_string > > interface and have seperated the safe_string.hpp file into the >appropriate > > headers (fsstring.hpp for string.h, fsstdio.hpp for stdio.h and >fswchar.hpp > > for wchar.h). I have also posted BoostBook format documentation to the >libs > > section. > > > > However, we are still no closer to deciding which implementation to >choose. > > We can either: > > [1] Choose one implementation and drop the other (possibly collaborate); > > [2] Continue both and put them against each other to see which is >better; > > [3] Drop both and develop one together from scratch. > > > > Option [3] is not viable, since a lot of the hard work has already been >done > > (size issues, etc.). I would like the implementation we use to be mine >and > > I'm sure John feels the same way about his. I am also getting to the >stage > > where I am considering putting mine up for review (once I get the tests > > written). > >John hasn't fleshed out his design quite as completely as you >have yours, but he's close. John just raised a new point: >accessing the N + 1'st element. That may not have been apparent >had he not been working on his own version -- or have you already >dealt with that? -- so both implementations remain useful. My s[ i ] throws if i > capacity() which shouldn't cause a problem. s.at( i ) throws if i > length(). >I laid out a plan previously for how to judge between the >implementations. I suggest waiting to have either reviewed until >you can both run your code through the same tests -- with and >without errors -- to see if there is a clear winner. Sure. I have been writing tests for my library (boost-sandbox/fixed_string/test/*.cpp) with a BBv2 file to do the testing. I have the C-style functions test cases posted and have made a start with the basic_string cases [21.3.1-4]. There still need to be tests for when the operations will cause buffer overflow on unprotected code, and generate exceptions for functions like s.at( i ), but I am waiting until I have written the basic test cases. The tests currently use my naming conventions, but I am sure they can be adapted for John's versions as well for comparisons. I could also implement bench marcking tests for performance analysis. >Another possible means to judge between the two is to find >real-world C code using strings, that compiles with a C++ >compiler. Then, each library author can translate the code >according to the needs of the libraries. Diffs will reveal the >extent of the changes needed, and copious notes could illustrate >common mistakes made and error messages encountered during the >translation. That information can clarify which design makes the >translation of C string code into fixed_string code easiest >(performance will have already been ascertained, so needn't be >reassessed). That would be a good idea. >If that doesn't reveal a clear winner, I've a suggestion for >breaking the tie: I can pass the options through a coworker of >mine. He was a C programmer for a very long time and has been >writing C++ code for less time. He still thinks like a C >programmer in a lot of ways, so he might have insights we're >missing. Also a good idea. Regards, Reece _________________________________________________________________ Is your PC infected? Get a FREE online computer virus scan from McAfee® Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

1 0

RE: [boost] Re: static sized strings
by Reece Dunn 01 Jun '04

01 Jun '04

John Nagle wrote: > I've done some cleanup on my version of fixed_string at > http://www.animats.com/source >[snip] > We're approaching convergence on this. We are both working on variations of the same idea. As such, I have fixed several errors in my code making it operate better as a basic_string interface and have seperated the safe_string.hpp file into the appropriate headers (fsstring.hpp for string.h, fsstdio.hpp for stdio.h and fswchar.hpp for wchar.h). I have also posted BoostBook format documentation to the libs section. However, we are still no closer to deciding which implementation to choose. We can either: [1] Choose one implementation and drop the other (possibly collaborate); [2] Continue both and put them against each other to see which is better; [3] Drop both and develop one together from scratch. Option [3] is not viable, since a lot of the hard work has already been done (size issues, etc.). I would like the implementation we use to be mine and I'm sure John feels the same way about his. I am also getting to the stage where I am considering putting mine up for review (once I get the tests written). What do other people think? Regards, Reece _________________________________________________________________ It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger

2 1

Re: [boost] Re: [prereview request][fsm]
by eegg＠comcast.net 01 Jun '04

01 Jun '04

--- Rob Stewart <stewart(a)sig.com> wrote: > From: "E. Gladyshev" <eegg(a)comcast.net> > > From: "Rob Stewart" <stewart(a)sig.com> > > > From: "E. Gladyshev" <eegg(a)comcast.net> > > > > From: "Rob Stewart" <stewart(a)sig.com> > > [...] > > 1. Some platforms pose non-C++ exceptions as normal C++ exception. > > You don't always want those platfrom specific exceptions trigger > > a whole bunch of stuff in your program. > > The only platform I know of that does that is Windows/MSVC It makes it pretty common, doesn't it. :) > you can handle structured exceptions specially. Perhaps it > means that boost::fsm needs to provide a means to install an > exception handler for those exceptions not already recognized by > the library: > > try { throw; } > catch (...) { boost::fsm::detail::handle_exception(); } > > void boost::fsm::detail::handle_exception() > { > try { throw; } > catch (type1 const &) { ... }; > catch (type2 const &) { ... }; > catch (type3 const &) { ... }; > catch (...) { user_handler(); } > } > where user_handler is a pointer to function that's initialized to > std::unexpected() and can be overridden by the library user. Adding user_handler() doesn't stop stack unwinding. I think you are missing the point. The issue is not in how to process SEH exceptions (or any other unhandled exception) the issue is in how not to trigger stack unwinding (for all exceptions) and still be able discriminate user exception types generically in FSM. Your solution doesn't solve this problem. > > It may also be that SEH can be configured to intervene before a > C++ exception is generated by the RTL so those never become C++ > exceptions that can muck up the works. It is not trivial... but it is out of the FSM topic. > > 2. Your design assumes that all possible exceptions are known > > and you handle them. So any unhandled exception is a bug. > > Not quite. What I was showing would rethrow any unknown > exception, leaving to clients to determine how to handle it. > > > It is not safe to trigger stack unwinding in a buggy environment. > > If you say so. Every application and platform with which I work > is buggy and yet I manage to use exceptions and stack unwinding > works. What do you mean by "stack unwinding works". Do you mean that even if the exception is caused by a bug, stack unwinding didn't make things worse or less safer? Well, it's a long shot... [...] > This is just another case of things not being as pretty > as one might like but that doesn't mean stack unwinding is > faulty. Sorry, who said that stack unwinding is faulty? Eugene

5 8

Re: [boost] [Serialization] Errors when compiling using GCC 3.4
by Robert Ramey 01 Jun '04

01 Jun '04

Allen Yao wrote: > I just updated my gcc from 3.3.3 to 3.4, and found that the > serialization17 and serialization18 cannot compile. There are many error > messages, some of them seem to caused by lack of "typename", others are > very strange, for example, about using boost::noncopyable. > Does someone try serialization library on GCC 3.4? Can it be compiled? > I suspect I am missing something. Otherwise, I would like to try to "fix" > the "bugs" myself. Hmmm, I just checked. I'm currently using gcc 3.3.1 ? Should I upgrade to gcc 3.4.? I seem to recall information on the list that suggested it would be better to wait a little bit. If upgrading is a good thing - now is a good time for me to do it as I'm just finalizing all the changes for next version and just starting the "torture test torture" procedure of reconciliation of compiler quirks. Robert Ramey

4 5

BOOST_READONLY_PROPERTY macro
by Toon Knapen 01 Jun '04

01 Jun '04

This is the next item in the continuing sage about porting the test-library to IBM/VisualAge. The use of the BOOST_READONLY_PROPERTY macro results in error messages (see attached file) when compiling the test library with vacpp. I tried to have a look at this macro but it is not documented anywhere (neither in the source files where the macro is defined) and thus I would appreciate help from someone more knowledgeable about the test and preprocessor library. Additionally I would like to remark again that the test tools should not have too many dependencies. If the test tools depend on almost all boost libraries, there's no use in having test tools that verify if all libraries compile, is there ? toon ...found 838 targets... ...updating 273 targets... xlc-C++-action /home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/debug/test_tools.o "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/test_tools.hpp", line 188.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/test_tools.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/test_tools.hpp", line 188.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/test_tools.cpp". xlC -c -I/home/tk/ext_projects/boost/boost_tknapen/boost -DBOOST_TEST_NO_AUTO_LINK=1 -qNOOPTimize -qnoinline -g -qfullpath -qnotempinc -qfuncsect -qeh -qrtti -I"/home/tk/cvstop/DO/bin/boost/libs/test/build" -I"/home/tk/ext_projects/boost/boost_tknapen/boost" -o "/home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/debug/test_tools.o" "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/test_tools.cpp" ...failed xlc-C++-action /home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/debug/test_tools.o... xlc-C++-action /home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/debug/unit_test_log.o xlc-C++-action /home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/debug/unit_test_monitor.o "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/test_tools.hpp", line 188.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/unit_test_monitor.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/test_tools.hpp", line 188.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/unit_test_monitor.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 72.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/unit_test_monitor.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 72.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/unit_test_monitor.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 74.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/unit_test_monitor.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 74.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/unit_test_monitor.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 84.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/unit_test_monitor.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 84.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/unit_test_monitor.cpp". xlC -c -I/home/tk/ext_projects/boost/boost_tknapen/boost -DBOOST_TEST_NO_AUTO_LINK=1 -qNOOPTimize -qnoinline -g -qfullpath -qnotempinc -qfuncsect -qeh -qrtti -I"/home/tk/cvstop/DO/bin/boost/libs/test/build" -I"/home/tk/ext_projects/boost/boost_tknapen/boost" -o "/home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/debug/unit_test_monitor.o" "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/unit_test_monitor.cpp" ...failed xlc-C++-action /home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/debug/unit_test_monitor.o... xlc-C++-action /home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/debug/unit_test_result.o "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 72.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/unit_test_result.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 72.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/unit_test_result.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 74.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/unit_test_result.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 74.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/unit_test_result.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 84.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/unit_test_result.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 84.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/unit_test_result.cpp". xlC -c -I/home/tk/ext_projects/boost/boost_tknapen/boost -DBOOST_TEST_NO_AUTO_LINK=1 -qNOOPTimize -qnoinline -g -qfullpath -qnotempinc -qfuncsect -qeh -qrtti -I"/home/tk/cvstop/DO/bin/boost/libs/test/build" -I"/home/tk/ext_projects/boost/boost_tknapen/boost" -o "/home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/debug/unit_test_result.o" "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/unit_test_result.cpp" ...failed xlc-C++-action /home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/debug/unit_test_result.o... xlc-C++-action /home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/debug/unit_test_suite.o "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 72.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/unit_test_suite.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 72.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/unit_test_suite.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 74.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/unit_test_suite.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 74.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/unit_test_suite.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 84.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/unit_test_suite.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 84.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/unit_test_suite.cpp". xlC -c -I/home/tk/ext_projects/boost/boost_tknapen/boost -DBOOST_TEST_NO_AUTO_LINK=1 -qNOOPTimize -qnoinline -g -qfullpath -qnotempinc -qfuncsect -qeh -qrtti -I"/home/tk/cvstop/DO/bin/boost/libs/test/build" -I"/home/tk/ext_projects/boost/boost_tknapen/boost" -o "/home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/debug/unit_test_suite.o" "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/unit_test_suite.cpp" ...failed xlc-C++-action /home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/debug/unit_test_suite.o... xlc-C++-action /home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/debug/supplied_log_formatters.o "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 72.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/supplied_log_formatters.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 72.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/supplied_log_formatters.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 74.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/supplied_log_formatters.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 74.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/supplied_log_formatters.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 84.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/supplied_log_formatters.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 84.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/supplied_log_formatters.cpp". xlC -c -I/home/tk/ext_projects/boost/boost_tknapen/boost -DBOOST_TEST_NO_AUTO_LINK=1 -qNOOPTimize -qnoinline -g -qfullpath -qnotempinc -qfuncsect -qeh -qrtti -I"/home/tk/cvstop/DO/bin/boost/libs/test/build" -I"/home/tk/ext_projects/boost/boost_tknapen/boost" -o "/home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/debug/supplied_log_formatters.o" "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/supplied_log_formatters.cpp" ...failed xlc-C++-action /home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/debug/supplied_log_formatters.o... xlc-C++-action /home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/debug/test_main.o "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/test_tools.hpp", line 188.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/test_main.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/test_tools.hpp", line 188.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/test_main.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 72.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/test_main.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 72.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/test_main.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 74.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/test_main.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 74.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/test_main.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 84.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/test_main.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/unit_test_suite.hpp", line 84.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/test_main.cpp". xlC -c -I/home/tk/ext_projects/boost/boost_tknapen/boost -DBOOST_TEST_NO_AUTO_LINK=1 -qNOOPTimize -qnoinline -g -qfullpath -qnotempinc -qfuncsect -qeh -qrtti -I"/home/tk/cvstop/DO/bin/boost/libs/test/build" -I"/home/tk/ext_projects/boost/boost_tknapen/boost" -o "/home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/debug/test_main.o" "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/test_main.cpp" ...failed xlc-C++-action /home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/debug/test_main.o... ...skipped <@boost!libs!test!build/libboost_test_exec_monitor.so/vacpp/debug>libboost_test_exec_monitor-xlc-d-1_31.so for lack of <@boost!libs!test!build/libboost_test_exec_monitor.so/vacpp/debug>test_tools.o... ...skipped <@boost!libs!test!build!stage!lib>libboost_test_exec_monitor-xlc-d-1_31.so for lack of <@boost!libs!test!build/libboost_test_exec_monitor.so/vacpp/debug>libboost_test_exec_monitor-xlc-d-1_31.so... MkDir1 /home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/release xlc-C++-action /home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/release/execution_monitor.o xlc-C++-action /home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/release/test_tools.o "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/test_tools.hpp", line 188.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/test_tools.cpp". "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/test/test_tools.hpp", line 188.6: 1540-0861 (S) Too few arguments are specified for macro "BOOST_PP_IIF_0". Empty arguments are used. "/home/tk/ext_projects/boost/boost_tknapen/boost/boost/preprocessor/control/iif.hpp", line 32.10: 1540-0425 (I) "BOOST_PP_IIF_0" is defined on line 32 of "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/test_tools.cpp". xlC -c -I/home/tk/ext_projects/boost/boost_tknapen/boost -DNDEBUG -DNDEBUG -DBOOST_TEST_NO_AUTO_LINK=1 -O3 -qstrict -qinline -qnotempinc -qfuncsect -qeh -qrtti -I"/home/tk/cvstop/DO/bin/boost/libs/test/build" -I"/home/tk/ext_projects/boost/boost_tknapen/boost" -o "/home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/release/test_tools.o" "/home/tk/ext_projects/boost/boost_tknapen/boost/libs/test/build/../src/test_tools.cpp" ...failed xlc-C++-action /home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/release/test_tools.o... xlc-C++-action /home/tk/cvstop/DO/bin/boost/libs/test/build/libboost_test_exec_monitor.so/vacpp/release/unit_test_parameters.o

3 2

Re: [boost] Re: [Boost-announce] Formal Review Tribool
by Haim Cohen 01 Jun '04

01 Jun '04

Sorry if this is a repost - I am almost sure my last post did not reached out. Rob Stewart wrote: > meaning "arbitrary value." However, "indeterminate" leaves no > doubt as to the meaning of the value and doesn't depend upon > one's experience with electronics. Another possibility would be I agree. Although I see the highest potential of the library in EDA applications, the meaning of the value should not depend on any problem domain - like electronics. I guess I was little bit biased here by my problem domain. > As I've already rejected the "x" notion, that leaves > "unknown_bool" or, by extension, "indeterminate_bool." While > these names suggest that there is an unknown or indeterminate > Boolean value, they don't suggest to me a type that includes > true, false, *and* unknown/indeterminate. "tribool," OTOH, I disagree. IMHO, The name unknown_bool hints that in addition to the 2 traditional values of bool, there is also an unknown bool. I am not a native user of the English language, but this is what the name unknown_bool hints *me*. Haim -- _____________________________________________________ Haim Cohen Software Engineer haim.cohen(a)analog.com / haimcohen2002(a)hotmail.com Analog Devices

1 0

[Formal review request] policy_ptr
by David B. Held 01 Jun '04

01 Jun '04

I am formally requesting that policy_ptr be added to the review queue. The version to be reviewed is different from the version currently in the sandbox, but will be available long before the current queue is exhausted. Dave --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com) Version: 6.0.691 / Virus Database: 452 - Release Date: 5/26/2004

3 3

Boost Software License & GPL
by Alex Vinokur 01 Jun '04

01 Jun '04

<QUOTE from http://www.boost.org/more/lib_guide.htm#License> License requirements The preferred way to meet the license requirements is to use the Boost Software License. See license information. If for any reason you do not intend to use the Boost Software License, please discuss the issues on the Boost developers mailing list first. </QUOTE> I am thinking of submission some software to Boost. However I put this software in several sites under GPL. Boost requires Boost Software License. How to solve this problem? -- Alex Vinokur mailto:alexvn@connect.to http://mathforum.org/library/view/10978.html

3 3