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

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