reentrant

Edit: Both the reentrant version (gethostbyname_r) and non-reentrant one (gethostbyname) are affected (the non-reentrant one uses a fixed buffer length).

If the lexer is reentrant, it could be re-entered from any of those places.

It is a very large library that actually includes a virtual machine that has been rewritten from pascal to single-threaded non-reentrant C to reentrant C...

For every modular part in the kernel, define what it is supposed to do: are calls reentrant?

Probably a lot of highly energetic reentrant debris capable of generating a lot of atmospheric heat.

It's like calling non-reentrant strtok, some of this stuff just doesn't exactly fit into todays world.

See above WRT Gauche; from a skim of the manual, Guile's VM may be reentrant or it hides that level of detail.

I think the only way to do that would be to have a reentrant lock for each object individually.

Moreover, unless you're spectacularly terrible at programming, your parser is reentrant.

I get that not everyone can sit down and start grepping how a kernel works, how to architect database solutions, or get what it means to be reentrant in the context of parallel programming.

But it wasn't truly finished -- while the API reflected concerns of multitasking the actual implementation was non-reentrant and the OS it was layered over was a crude DOS/CP/M-like OS.

The test case seems to have it looking up an ip address as if it were a name, but it's using the reentrant version of the function - maybe only those are affected?

It's not something to "solve", either your interpreter is reentrant, or it isn't.

But I'd rather be able to use "par" at the highest level of my program, and parallelize anything from XML parsing to physics simulation, without worrying that some library call ten functions down the stack will turn out to be non-reentrant.