> If I'm writing a library and I'd like to use procdata, is there any
> way to safely do so, considering that applications using the library
> might be using procdata as well? Perhaps it should take a key, like
> pthread_getspecific/_setspecific?
since procdata(2) it is unused,
cd /sys/src && grep -l procdata `{find|grep '\.[ch]'}
./libthread/id.c
a first cut would be to add this to
the man page
.SH BUGS
steals
.IR procdata (2).
but i would consider it a warning flag that
there are no current users of threadata or procdata.
- erik
