| Register | FAQ | Calendar | Search | Today's Posts | Mark Forums Read |
|
#11
| |||
| |||
| Georg Bauhaus <see.reply.to@maps.futureapps.de> writes: [...] >[*] errno is just a good example for the more general shared > variable that needs protection from concurrent access. It hadn't > always been a matter of course for a C library to be thread > safe! Actually "errno" must be a thread-local variable to make any sense. Any OS-call has to be serialized, and only after errno is "safed", thread execution can continue. Thus it's still an argument against "static" routines... Ulrich |
![]() |
| Thread Tools | |
| Display Modes | |
In an effort to better serve ads to our visitors, cookies are used on objectmix.com. For more information, check out our Privacy Policy.