Alexander Nasonov <alnsn@yandex.ru> writes:
Rene Rivera wrote:
Ah, seems like a very bad idea to me. I think writing code that is so platform dependent and is commonly known to be available as the separate utility "more" will create more problems than it would solve.
I completely agree.
A better idea is to add that functionality to the configure script itself. Just have it figure out a paging program to use to send such output to.
Does it really a problem that more is unavailable? In other words, why introduce more complexity when it's enough to instruct people to use more or their favorite pager?
Because that introduces complexity into the instructions.
Personally I wouldn't add such a thing at all. I would think you would be hard pressed to find Unix users who don't know how to use "more", or use a terminal/shell window with a scroll bar.
I wouldn't do either but I can easily imagine new generation C++ developer who just installed Fedora/Ubuntu/etc, opened KDevelop or other IDE and would like to play with boost but has no idea yet how to use bash. Boost's getting started guide would be a first bash guide for them ;-)
Please, no! I want to keep the scope of the document limited, not try to teach everything under the sun. -- Dave Abrahams Boost Consulting www.boost-consulting.com