From: Gennadiy Rozental (gennadiy.rozental_at_[hidden])
Date: 2004-06-01 07:07:43
> 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.
For now it's internal macro used in Boost.Test internals (though it's usage
is quite straitforward and should be obvios). I did proposed to make it
common utility couple days ago.
> 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 ?
Boost.Test does not depend on anything that does not compile almost
everywhere. If needed I am using specific workarounds. Also Boost.Test
layered design allows one to use one limited dependency component to test
more widely dependant one.
In this particular case I rely on PP library. It works even on ancient
Solaris 4.2 and gcc 2.9.1. I don't know specific issies with the compiler
you are using in regards of preprocessor, so couldn't give more helpfull
information other than that PP macros are used to generate series of friend
statement in class definition:
friend class class1;
friend class class2;
friend class classN;
BOOST_CLASS_PROPERTY is used like this:
BOOST_CLASS_PROPERTY( int, (class1)(class2)...(classN) ) property;
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk