mirror of
https://github.com/ARMmbed/mbedtls.git
synced 2025-06-24 14:20:59 +08:00
Reword slightly to be more tentative
We don't guarantee ABI stability, but we do try to maintain it where we can. Signed-off-by: David Horstmann <david.horstmann@arm.com>
This commit is contained in:
parent
235dfc2b8c
commit
20220f09b4
@ -71,7 +71,7 @@ If you were accessing structure fields directly, and these fields are not docume
|
||||
|
||||
If no accessor function exists, please open an [enhancement request against Mbed TLS](https://github.com/Mbed-TLS/mbedtls/issues/new?template=feature_request.md) and describe your use case. The Mbed TLS development team is aware that some useful accessor functions are missing in the 3.0 release, and we expect to add them to the first minor release(s) (3.1, etc.).
|
||||
|
||||
As a last resort, you can access the field `foo` of a structure `bar` by writing `bar.MBEDTLS_PRIVATE(foo)`. Note that you do so at your own risk, since such code is likely to break in a future minor version of Mbed TLS. However, in the Mbed TLS 3.6 LTS this is generally a safe way to access struct members because LTS versions try to maintain ABI stability.
|
||||
As a last resort, you can access the field `foo` of a structure `bar` by writing `bar.MBEDTLS_PRIVATE(foo)`. Note that you do so at your own risk, since such code is likely to break in a future minor version of Mbed TLS. In the Mbed TLS 3.6 LTS this will tend to be safer than in a normal minor release because LTS versions try to maintain ABI stability.
|
||||
|
||||
### Move part of timing module out of the library
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user