Robert Ramey <ramey <at> rrsd.com> writes:
One small point: I had this problem many years ago which prompted me to (reluctantly) sever dependency of serialization library from that of Boost.Test. It didn't totally solve my problem because the same issue occurred to some extent with other libraries.
It appear that given your approach to test against releases, you can actually use Boost.Test if you opt to.
It was unavoidable since I was testing the serialization library with other software in the boost trunk - which by definition/custom is experimental.
I realized that the real solution was to test the serialization library changes against the rest of boost on the release branch. It permited developers of prerequisite libraries from having to deal with me.
My point exactly. Gennadiy