Lines Matching refs:API

97 - **Public API**: Any definitions and declarations under `include/libpldm`.
112   - Incorrect use of public API functions is always an error condition, and is
163 Adding APIs to a library is a difficult task. Generally, once an API is exposed
164 in the library's ABI, any changes to the API risk breaking applications already
165 making use of it. To make sure we have more than one shot at getting an API
218 use in context _before_ preventing us from making changes to the API.
247 ## Adding a new API
272   - [ ] The API must abstract over the platform-specific types, and there are no
283 ### API design
293     requiring heap allocation in the implementation or splitting the API to
313       added to the public API.
364         context of the function call are listed in the API documentation.
425 - [ ] I've added public OEM API declarations and definitions under
431 - [ ] I've implemented the OEM API tests under `tests/oem/${OEM_NAME}/`
440 ## Stabilising an existing API
442 - [ ] The API of interest is currently marked `LIBPLDM_ABI_TESTING`
445       API
487 ## Removing an API
500         the API being marked deprecated
502 ## Renaming an API
504 A change to an API is a pure rename only if there are no additional behavioural
505 changes. Renaming an API with no other behavioural changes is really two
508 1. Introducing the new API name
509 2. Deprecating the old API name