Explicitly disallow C++ exceptions.
PiperOrigin-RevId: 676494975
Change-Id: Ia08160709791d7f83204d2a9cb0c464775b609c2
diff --git a/api-guidelines/ndk.md b/api-guidelines/ndk.md
index 841d5fc..ff46b20 100644
--- a/api-guidelines/ndk.md
+++ b/api-guidelines/ndk.md
@@ -688,6 +688,15 @@
allows new error codes to be added that do not cause a crash on old systems
if used explicitly.
+### C++ exceptions may not cross the API boundary {.numbered}
+
+Stable API boundaries are C only (the C++ ABI is not stable), so C++ exceptions
+are not allowed to cross the API boundary. You must use an alternative method of
+error handling for your API (see above).
+
+If your implementation may raise exceptions, they must be caught and handled
+(probably by translating to error codes) at the API boundary.
+
## Callbacks <a name="callbacks"></a>
### Callbacks should be a bare function pointer. <a name="callbacks-func-pointer"></a>
