Good point. I have had other feedbacks of crashes that could have to do
with Liblouis not being threat safe. Making the Java bindings threat safe
is definitely something I should do.
2016-12-06 14:41 GMT+01:00 Michael Katzmann <mkat@xxxxxxxxxx>:
Yes, it would be helpful to add it in LARGE FRIENDLY LETTERS 8-)
The Java bindings (liblouis-java) could add a synchronized keyword (or
otherwise enforce a mutex).
Michael
On Tue, Dec 6, 2016 at 8:28 AM, Keith Creasy <kcreasy@xxxxxxx> wrote:
LibLouis is definitely not thread safe. It would be a significant job for
someone to make it so.
That probably should be added to the docs.
K
*From:* liblouis-liblouisxml-bounce@xxxxxxxxxxxxx [mailto:
liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] *On Behalf Of *Michael
Katzmann
*Sent:* Tuesday, December 6, 2016 8:24 AM
*To:* liblouis-liblouisxml@xxxxxxxxxxxxx
*Subject:* [liblouis-liblouisxml] liblouis thread-safe (not)
Apart from a statement in the strerror routine I cannot see any
declarations on the thread safeness of liblouis. I'm getting a crash that I
suspect is caused by liblouis not being thread safe.
Am I wrong ? ,... should I be able to access liblouis from multiple
threads safely ?
Michael
