I've talked with Charlie Lenahan regarding this and I'm going to do a little 
footwork to tabulate what it would take to remove the requirement for ocstack.h 
from the Public-facing C++ API. If the work is done now to remove the C++ 
public-facing API dependency on the C public-facing API, then Bill's changeset 
wouldn't be required.

I will return to this mail thread with my results to see if anyone would 
volunteer to do this work.

Thanks,

Joey

From: iotivity-dev-bounces at lists.iotivity.org 
[mailto:[email protected]] On Behalf Of Morrow, Joseph L
Sent: Thursday, April 23, 2015 11:49 AM
To: Dieter, William R; iotivity-dev at lists.iotivity.org
Subject: Re: [dev] ocstack.h in API docs

For those reading into this: Bill's concern is regarding the C++ API, and why 
it doesn't include ocstack.h in its doxygen generated documentation.

Bill,

I believe the previous reason was that it was because the C++ API had intended 
to be separate from the C API altogether. However, the case for this was never 
pointed and hence I believe that the C++ API ended up using definitions from 
within ocstack.h directly, rather than enumerating it's own OCStackResults, etc.

In short:  Including ocstack.h into the C++ API Doxygen documentation is fine. 
I will '+1' your changeset.

Thanks,

Joey



From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at 
lists.iotivity.org> [mailto:[email protected]] On Behalf 
Of Dieter, William R
Sent: Wednesday, April 22, 2015 10:02 PM
To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at 
lists.iotivity.org>
Subject: [dev] ocstack.h in API docs

Is there a reason ocstack.h should not be included in the Doxygen API docs?  
Adding it do the Doxyfile the types and values defined in ocstack.h clickable 
in the docs, and clicking takes the reader to the value and the documentation 
for it.

https://gerrit.iotivity.org/gerrit/#/c/811/3

Bill.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150423/2450ffc2/attachment.html>

Reply via email to