Indeed, when I said: ?C functions included under out/??
I meant: ?C functions having their prototype included in header files under out/?? Dan From: Gregg Reynolds [mailto:[email protected]] Sent: Thursday, April 6, 2017 12:39 PM To: Daniel Mihai <Daniel.Mihai at microsoft.com> Cc: Dave Thaler <dthaler at microsoft.com>; uzchoi at samsung.com; Mats Wichmann <mats at wichmann.us>; iotivity-dev at lists.iotivity.org Subject: Re: [dev] Public and Experimental Public C APIs On Apr 6, 2017 2:34 PM, "Gregg Reynolds" <dev at mobileink.com<mailto:dev at mobileink.com>> wrote: On Apr 6, 2017 2:09 PM, "Daniel Mihai via iotivity-dev" <iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>> wrote: Should we start with the following definitions? 1. All C functions included under out/<path_to_IoTivity_SDK>/ are Public APIs 2. All C functions included under out/<path_to_IoTivity_SDK>/experimental/ are Experimental Public APIs 3. When an Experimental Public API gets promoted to non-Experimental Public API, that API SHALL be moved out of out/<path_to_IoTivity_SDK>/experimental/ header files 4. Apps should expect potential breaking changes to Experimental Public APIs, but no breaking changes to non-Experimental Public APIs quibble: it's not just about functions (i think you mean function prototypes?). ie. for any header file in /out/..., everything in that header is public. which may include more than just fn prototypes. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170406/3de4d626/attachment.html>
