Is the bison generated parser thread safe?
Move the new .h files into R/include.
Clean up first.
No threads as yet, just becoming thread safe.
Signals and dedicated thread.
Access to global objects (e.g. .Devices) will require synchronization - either at the S or C level.
The whole graphics event handling and location of the associated evaluator can change since we can be in a simpler sequential calls rather than asynchronous event handling.
Keep an eye on the code in unix/ and windows/

Initialization

arithmetic.c:establish_endianness()
Invoked from InitrArithmetic. Takes care of setting lw, hw and little_endian. Constant after that. So we can use a pthread_once().
naflag and lcall need to be protected for reentrance. See Removing Global Variables for possible strategies.
deriv.o: installation of the different strings - cos, sin, etc.
Call InitDerivSymbols early before second thread started. Of course install() should take care of synchronizing things also and ensuring that the same pointer is returned.
bind.c
Check the local structures and argument passing don't break some notion of persistence across calls to the do_() routines.
This is unlikely since a) it doesn't make much sense to use that cached information; b) I think the values are reinitialized in the do_() routines.

Duncan Temple Lang <duncan@research.bell-labs.com>
Last modified: Thu May 27 13:11:37 EDT 1999