Re: [boost] [Config] Support for switching between std:: andboost:: equivalents.

Subject: Re: [boost] [Config] Support for switching between std:: andboost:: equivalents.
From: Edward Diener (eldiener_at_[hidden])
Date: 2015-06-08 20:16:46

On 6/8/2015 6:44 PM, Niall Douglas wrote:
> On 7 Jun 2015 at 22:07, Edward Diener wrote:
>
>>>> I hate to re-invent the wheel.
>>>
>>> APIBind comes at the C++ 11 problem from the outside coming in. Yours
>>> comes from inside Boost going out. Like your solution, APIBind is
>>> proven working solution which should be better understood by the
>>> community soon at the end of July during the AFIO review, and there
>>> is a C++ Now presentation with 90 minutes on just APIBind, with
>>> plenty of valuable audience commentary by WG21 members and long time
>>> Boost community members.
>>
>> APIBind is not finished AFAICS and I do not even remotely understand the
>> documentation you currently have for it. If others find it usable to
>> solve this problem that is fine by me.
>
> A step by step explanation of how it works and feature organisation
> is in the slides at
> https://github.com/boostcon/cppnow_presentations_2015/raw/master/files
> /A-review-of-Cxx-11-14-only-Boost-libraries-Fiber-AFIO-DI-and-APIBind.
> pdf
>
> Rationale is at
> https://svn.boost.org/trac/boost/wiki/BestPracticeHandbook#a16.COUPLIN
> G:Considerallowingyourlibraryuserstodependencyinjectyourdependencieson
> otherlibraries
>
> What remains lacking is a step by step tutorial, but it's hardly
> difficult. I noticed at C++ Now I didn't find anyone didn't fully
> understand what was going on and how it worked, indeed Beman
> mentioned the same technique had been in use in C++ 11 standard
> library implementations for many years now.

Thanks for the links. I admit I get frustrated when documentation starts 
off explaining to me how to use XXX without telling me what XXX is about 
first.

If the only thing lacking is a step by step tutorial wouldn't it be 
better to remove the "What state is this tool in ?" in your readme.md 
which implies that what you are doing is not close to being finished ?