Niall Douglas wrote:
And I have no problem if AFIO never enters Boost. I would think it a shame and a wasted opportunity as it solves a ton of pain points for those with such needs
Whatever happened to... > Niall Douglas wrote: > > Firstly, you don't invest the multi-year effort to get a library into > > Boost because it's superior, as it probably isn't. You do it because > > of what you will become after you succeed: a Boost library author > > who has passed the judgement of his or her peers. On a more serious note:
Totally separate to the async file i/o is the race free filesystem stuff. I would like to believe that people understand why a race free filesystem API is important.
Your documentation would be the best vehicle to convey (and prove) this. It doesn't do it for me right now. I may be the 0.0001% who doesn't need AFIO as you've currently designed it but ideally the documentation should help me understand why. Glen -- View this message in context: http://boost.2283326.n4.nabble.com/afio-AFIO-review-postponed-till-Monday-tp... Sent from the Boost - Dev mailing list archive at Nabble.com.