invalid pthread_t value?

[Samuel Thibault]

Hi,

The NSPR needs an invalid value for pthread_t, which the Hurd doesn't
officially have. I had proposed them to use -1 (since that would mean
that there are something like 2^32 threads running, which just can't
be...), but they don't seem to have accepted this (the patch seems to
have been turned into a #error instead... No actual mail feedback).

Since pthread_t is typedefed to int, maybe we can define
PTHREAD_THREADS_MAX to INT_MAX to actually set an official limit (that
limit exists anyway since above INT_MAX the comparisons in libpthread
become bogus), and then tell them they can really use -1?

Samuel