cpp-style: Elaborate on cases for using explicitly-sized types
Explicitly-sized types (uintX_t and friends) are sometimes specified in
non-hardware interfaces we don't control, so using such types for
variables used with such interfaces can be appropriate.
Signed-off-by: Zev Weiss <zev@bewilderbeest.net>
Change-Id: I6dd09c93b978f8bb9b8748eb4a0c39537f82f0f3
diff --git a/cpp-style-and-conventions.md b/cpp-style-and-conventions.md
index 9b4df7d..b1ad533 100644
--- a/cpp-style-and-conventions.md
+++ b/cpp-style-and-conventions.md
@@ -452,5 +452,6 @@
will do.
- Use `uint8_t`, `int16_t`, `uint32_t`, `int64_t`, etc. for types where size is
- important due to hardware interaction. Do not use them, without good reason,
- when hardware interaction is not involved; prefer size_t or int instead.
+ important due to interactions with hardware or some externally defined API/ABI
+ (such as a system call or library interface). Do not use them, without good
+ reason, when such interaction is not involved; prefer size_t or int instead.