From be2d31199f95ddbfa02530a021c8ab9611018f27 Mon Sep 17 00:00:00 2001 From: Sven Gothel Date: Sun, 2 Jul 2023 00:17:02 +0200 Subject: GlueGen JavaCallback: Emphasize all methods are thread-safe --- doc/GlueGen_Mapping.html | 3 ++- doc/GlueGen_Mapping.md | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/GlueGen_Mapping.html b/doc/GlueGen_Mapping.html index aaa305b..bfe9ae8 100644 --- a/doc/GlueGen_Mapping.html +++ b/doc/GlueGen_Mapping.html @@ -2113,7 +2113,8 @@ href="#javacallback-key-definition">key arguments (see callback.
  • Exactly one native code-unit for the library must specify LibraryOnLoad libraryBasename
  • -
  • SetCallbackFunction is thread safe
  • +
  • SetCallbackFunction, all maintenance methods +and the native callback dispatcher is thread safe
  • ...
  • JavaCallback Example 1

    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 -- cgit v1.2.3