On 16 Aug 2014 at 10:05, Robert Ramey wrote:
You've stated that AFIO is a counter-example to d) above. I'm confident you'll let me know if I've got your position wrong.
I think the disagreement for the code enforcement part, not the documentation part, is probably about mechanism and intent not outcome.
This is the first time I've actually looked into the AFIO documentation. I found it very interesting. I'm going to critique it later in detail as it deserves a larger effort than I can justify right now.
I'm always very interested in constructive feedback. Do remember the API is designed to be used indirectly as part of an eventual monadic continuations framework, though direct use will always be the most efficient of course. As the tutorial demonstrates, usage fragments into bitty unmaintainable callbacks at scale if you are using the API directly. The design rationale at the front is out of date after my C++ Now 2014 presentation and I need to update it. It's not terrible though.
PS - I'll likely post this critique as a comment on the blincubator as I want to test/demo this platform for this purpose. It's very hard to get this stuff right the first time so bear with me.
I just updated AFIO's entry there to match current. Does it email me when a comment is posted? If not, do ping me when it's ready. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/