On Jan 2, 2018 7:18 PM, "Dave Thaler via iotivity-dev" < [email protected]> wrote:
Two new proposed API guidelines, please review: * A public API should 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). I don't understand this one. It seems to say you should not duplicate functionality (Principle of Parsimony?) Is that correct? Why does number of LOC matter? * A public API should 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. I guess by "API" you mean routine or function? So this rule says the Iotivity API should consist of primitives - if the proposed routine can be expressed in terms of existing (presumably primitive) routines it should be rejected. Yes? Principle of Simplicity? (Non-primitives add inessential complexity to the API.) gregg
_______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
