Re: C++ APIs

[Michael Davidsaver <mdavidsaver@gmail.com>]

Sigh... oh Andrew.  I can see that trying to discuss this via email was
a mistake.  The smallest part gets blown out of proportion.  If this were
in real time I would have had a chance to clarify myself before anyone
got too excited.  I'm not going to try to conclude anything by email, so
we will have to wait until the next meeting.

For the record, I presented my "new" client API almost a year ago.  I'm not
surprised that you don't remember as it wasn't relevant to your interests.
The reaction was positive, though mostly I think due to the concise examples.

http://epics-base.github.io/pvAccessCPP/examples_miniget.html

On 07/20/2018 03:13 PM, Andrew Johnson wrote:
> ...
> You will recall that I presented my plug-in API concept at the last
> Hangout, and the group told me "No, or don't do it like that." I could
> have just implemented my design instead and added it to libCom without
> asking, and most likely nobody would have even noticed until it was
> already being used. Instead I spent my Saturday coming up with that
> conceptual design document.

You say this as if you expect me to think that this would be a horrible
outcome, but the fact of the matter is that I trust that if you had
"just implemented" you would have discovered for yourself the areas of
concern (ABI, versioning, and dependencies), and either found solutions,
or come to the conclusion that more thought/input was needed.

As for donating Saturdays to the EPICS Collaboration... check.

> Moving your pva/server API out into a separate module might help to
> level the playing field, restore trust and alleviate some concerns about
> your future work plans. If you wanted that API/module to be included in
> future EPICS Base releases then you would need to present it to the
> group. Since the pva/client API would be much harder to unbundle at this
> point, I would like you to present that API at our meeting at ESS in
> September, and if you wanted to maintain both the client and server APIs
> in the same in-tree module you could combine the two presentations into one.

I'm not going to get into this now.  Though for the record, I had
intended to present my server API along with the other projects I've
been working on.  This is what we do at these meeting...