On 23 Oct 2009, at 16:57, Jeff Flinn wrote:
Olaf van der Spek wrote:
On Fri, Oct 23, 2009 at 5:04 PM, Stewart, Robert <Robert.Stewart@sig.com
wrote:
I very rarely tab-complete header file names, and I suspect most users Your usage patterns are limited to your coworkers and your environment. Mine suggests that there are a great many people who use tab completion constantly. Consequently, we can't favor one over the other if a neutral solution is possible. As a Boost dev or as a user? As user the version without /all seems better.
This user would prefer the lib/all.hpp, so that when compile times get egregious I can quickly track down the overzealous */all.hpp's and replace them with the minimal includes.
I have a project which includes the global headers for gil, variant, type_traits, thread, function, signals, any, bind and preprocessor, and with a pre-compiled header can compile small files including these headers in (just checking) < 0.25s real time, 0.13s CPU time. I find this acceptable, and saves me time have to look up what is in each header. Of course, we should not require the use of 'all' headers, but they can be useful. Chris