User Tools

Site Tools


api_guidelines

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
api_guidelines [2018/01/03 23:01]
Dave Thaler
api_guidelines [2018/01/04 00:43] (current)
Dave Thaler
Line 20: Line 20:
   * A public API must not be added to Iotivity if there is already a non-deprecated API that can just as easily be used (i.e., with approximately the same number of lines of code).   * A public API must not be added to Iotivity if there is already a non-deprecated API that can just as easily be used (i.e., with approximately the same number of lines of code).
   * A public API must not be added to Iotivity if the API would provide generic functionality (i.e., not inherently OCF or Iotivity specific functionality) that could be provided by an external library.   * A public API must not be added to Iotivity if the API would provide generic functionality (i.e., not inherently OCF or Iotivity specific functionality) that could be provided by an external library.
-  * All new Public C/C++ API names must start with “OC”+  * All new Public C API names must start with “OC”
 +  * All new Public C++ APIs must be under the "​OC"​ namespace.
   * All public headers must follow [[iotivity_coding_standards|IoTivity Coding Standards]].   * All public headers must follow [[iotivity_coding_standards|IoTivity Coding Standards]].
  
api_guidelines.txt · Last modified: 2018/01/04 00:43 by Dave Thaler