[Bug-kawa] [bug #33325] using setIndirectDefines safely

[tk]

Follow-up Comment #2, bug #33325 (project kawa):

the problem case is Environment.cloneForThread, where 
InheritingEnvironments are created in the context of 
new threads (which may happen outside of application control).

it is possible to call setIndirectDefines in application code, but
it's tedious and error prone in situations where one is passing 
in callback objects that are run in the context of a thread pool 
(e..g. i'm using kawa with the netty async i/o framework). 
To ensure that setIndirectDefines is seen early enough, it must 
be called on every potential execution path.

i agree that the proposed change feels more like a workaround 
than an actual solution -- i'll give some thought to better
ways of expressing this.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?33325>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/