Error ifndef _REENTRANT?

[Michael B Allen]

Does _REENTRANT mean that all of your code has to be reentrant? If I do:

#if __USE_UNIX98
mbstate_t mb;
...
mbrtowc(..., &mb)
#else
mbtowc(...)
#endif

Should I stick a #ifndef _REENTRANT error in there if the reentrant
version of mbrtowc isn't available? I don't know in advance that this
function will be called by multiple threads. What would you do in this
case?

Mike

[pete]

Michael B Allen wrote:

Does _REENTRANT mean that all of your code has to be reentrant?
Maybe. _REENTRANT isn't part of C.
#if __USE_UNIX98

I think you want a UNIX newsgroup.

--
pete

[Michael B Allen]

On Tue, 21 Sep 2004 08:33:04 -0400, pete wrote:

Michael B Allen wrote:

Does _REENTRANT mean that all of your code has to be reentrant?

Maybe. _REENTRANT isn't part of C.

Holy mackerel, I think you're right. I guess it's just another one of
those unwritten rules. Obviously a lot of stuff would break miserably
if standard library functions really weren't reentrant.

Yuck,
Mike

[pete]

Michael B Allen wrote:

On Tue, 21 Sep 2004 08:33:04 -0400, pete wrote:

Michael B Allen wrote:

Does _REENTRANT mean that all of your code has to be reentrant?

Maybe. _REENTRANT isn't part of C.

Holy mackerel, I think you're right. I guess it's just another one of
those unwritten rules. Obviously a lot of stuff would break miserably
if standard library functions really weren't reentrant.

Standard library functions really aren't reentrant.

N869
7.1.4 Use of library functions
[#4] The functions in the standard library are not
guaranteed to be reentrant and may modify objects with
static storage duration.
--
pete