diff options
author | Sven Gothel <[email protected]> | 2023-07-02 00:17:02 +0200 |
---|---|---|
committer | Sven Gothel <[email protected]> | 2023-07-02 00:17:02 +0200 |
commit | be2d31199f95ddbfa02530a021c8ab9611018f27 (patch) | |
tree | 9f907a31d9fc2e646d733341a225aa2127d6845e /doc/GlueGen_Mapping.md | |
parent | 679ce37046c3c68b97e56fb70ea7b316e9dba3ad (diff) |
GlueGen JavaCallback: Emphasize all methods are thread-safe
Diffstat (limited to 'doc/GlueGen_Mapping.md')
-rw-r--r-- | doc/GlueGen_Mapping.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/GlueGen_Mapping.md b/doc/GlueGen_Mapping.md index b1cbee5..490883d 100644 --- a/doc/GlueGen_Mapping.md +++ b/doc/GlueGen_Mapping.md @@ -862,7 +862,7 @@ Please consider the following *currently enabled* constraints using JavaCallback - To remove a JavaCallback the `SetCallbackFunction` must be called with `null` for the `CallbackFunction` argument but with the same [*key arguments* (see `JavaCallbackKey`)](#javacallback-key-definition) as previously called to set the callback. - Exactly one native code-unit for the library must specify [`LibraryOnLoad libraryBasename`](#libraryonload-librarybasename-for-jni_onload-) -- `SetCallbackFunction` is thread safe +- `SetCallbackFunction`, all *maintenance* methods and the native callback dispatcher **is thread safe** - ... ### JavaCallback Example 1 |