Lines Matching defs:API

91 - **Public API**: Any definitions and declarations under `include/libpldm`.
106   - Incorrect use of public API functions is always an error condition, and is
157 Adding APIs to a library is a difficult task. Generally, once an API is exposed
158 in the library's ABI, any changes to the API risk breaking applications already
159 making use of it. To make sure we have more than one shot at getting an API
212 use in context _before_ preventing us from making changes to the API.
228 ## Adding a new API
247 ### API design
257     requiring heap allocation in the implementation or splitting the API to
273       added to the public API.
324         context of the function call are listed in the API documentation.
360 - [ ] If my work impacts the public API of the library, then I've added an entry
368 - [ ] I've added public OEM API declarations and definitions under
374 - [ ] I've implemented the OEM API tests under `tests/oem/${OEM_NAME}/`
383 ## Stabilising an existing API
385 - [ ] The API of interest is currently marked `LIBPLDM_ABI_TESTING`
388       API
430 ## Removing an API
443         the API being marked deprecated
445 ## Renaming an API
447 A change to an API is a pure rename only if there are no additional behavioural
448 changes. Renaming an API with no other behavioural changes is really two
451 1. Introducing the new API name
452 2. Deprecating the old API name