Re: [Boost-users] Boost::Test Samples?

Subject: Re: [Boost-users] Boost::Test Samples?
From: Gennadiy Rozental (rogeeff_at_[hidden])
Date: 2011-08-07 02:41:22

Jeffrey Walton <noloader <at> gmail.com> writes:
 
> It would be incredibly helpful if the project offered a few real life
> sample of things such as a program (with a `main`), a static archive,
> and a DSO (or DLL). Nothing fancy - build a DSO via a makefile with
> two source files (A.cpp and B.cpp) and test them (A-test.cpp and
> B-test.cpp). In addition, a Visual Studio project to do the same would
> help the Win32 folks.

I am not quite sure  what exactly you are looking here. If you looking for
building instructions for standalone UTF library they are covered in
documentation in general, but specifically will depend on make system you are
using. I'd recommend though to start with included usage variant to eliminate
any building/linking overhead.
 
> I've heard a lot of great things about Boost, and I am glad it has
> worked for some folks. But after a couple of days on and off with
> Boost::Test, I'm beginning to wonder if its a good choice for our C++
> project.

aside form build is there any other specific issues?
 
> The Boost::Test library lacks clear and concise documentation (the
> online documentation is fractured, lack clarity, is hard to follow,
> and has broken links). 

I'm sorry you do not like the way documentation is structured. What would you
prefer it to look like? which particular parts you find unclear?

> The library is clearly abusing macros in a C++ library 

Can you show me an example of this abuse? And how would achieve the same result
without using them?

> (where are the predicates, functors, and other things I expect
> to see from a C++ library? Bjarne would probably chuckle or laugh).

I can't claim what Bjarne is doing or would do, but I did laugh when I read your
statement above.

> And the missing samples [broken links] are really not forgivable.

I did not look at docs for quite some time. It is indeed possible some links
gone stale. I need to revive the toolchain we use to generate docs and I'll fix
these.

Gennadiy