Re: [boost] [test] boost.test owner unresponsive to persistent problems for multiple years

Subject: Re: [boost] [test] boost.test owner unresponsive to persistent problems for multiple years
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2015-01-09 05:50:14

> -----Original Message-----
> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Gennadiy
> Rozental
> Sent: 08 January 2015 17:35
> To: boost_at_[hidden]
> Subject: Re: [boost] [test] boost.test owner unresponsive to persistent
problems for
> multiple years
> 
> Paul A. Bristow <pbristow <at> hetp.u-net.com> writes:
> 
> > I'm not understanding why you can't use a separate Quickbook section
> > called "Advanced"
> > and provide the execution monitor stuff there.
> 
> I am trying to make Boost.Test UTF the interface these docs will describe
(isn't this
> what you wanted?). Thus we dropped: test execution monitor, program execution
> monitor, execution monitor from all the user's guide and advanced usage
sections.

I can't see why you want to hide these from view.  Some users may want them?

> Few components which I still want to cover I placed in reference docs. This
location
> makes most since this is really is a programmer interface with some semantic
behind
> it.
> 
> > The document size is irrelevant - what counts is finding what you want
> > to know.
> 
> Yes and No. The main intention here is to ensure that users will never get
confused
> these components as public interfaces of UTF. I intentionally want them to
look very
> different.
> 
> > The TOC is the first weapon, and the (auto-)index second, and the C++
> > reference third.
> 
> Not quite sure how index is going to help with what I am after.

The index may not help you but it should help the *user* find what he wants to
know.

It's just one tool in the navigation game.

Paul

---
Paul A. Bristow
Prizet Farmhouse
Kendal UK LA8 8AB
[phone]