🚀 go-pugleaf

Ernst Kloecker (ernst@opal.cs.tu-berlin.de) wrote:

The C library has been pretty well handled by the other responses.
If you compile properly with IBM C Set/2 (set the multithreaded
compile option) you should be completely safe except from your
own multithreaded errors (simultaneous access of shared globals
without semaphore protection).

: Or are the only safe functions the OS-functions in 'bsedos.h' ?
: 
: Or are even those functions not completely thread-safe ?
: 
All functions declared through including os2.h (includes bse*.h,
pm*.h, etc) are safe.  They are part of or attached to the
operating system which is designed for such problems.  They are
not part of the C library.  Again, you can get into trouble due
to sharing your own variables.  But I believe that every Dos, Win, Gpi,
Mou, Kbd, Vio, etc call is atomic to the extent that anything that
it depends on in the system (such as file buffers) are modified
without the chance of another thread getting in.  However, two
DosWrite's in a row may be split by a DosWRite from another thread.