$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
Subject: Re: [boost] [test] boost.test owner unresponsive to	persistent	problems for multiple years
From: Gennadiy Rozental (rogeeff_at_[hidden])
Date: 2015-01-08 12:35:21
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.
>
> What is it that is so different about this that the 
> Quickbook structure etc
> cannot provide?
> 
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. 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.
Gennadiy