When should we use thread-safe "_r" library calls?
Answers were Sorted based on User's Feedback
Answer / guest
If your system provides threads, it will probably provide a
set of thread-safe variants of standard C library routines.
A small number of these are mandated by the POSIX standard,
and many Unix vendors provide their own useful supersets,
including functions such as gethostbyname_r().
Unfortunately, the supersets that different vendors support
do not necessarily overlap, so you can only safely use the
standard POSIX-mandated functions. The thread-safe routines
are conceptually "cleaner" than their stateful
counterparts, though, so it is good practice to use them
wherever and whenever you can.
| Is This Answer Correct ? | 4 Yes | 0 No |
Answer / vidya
If you compile using _REENTRANT option, the thread-safe
functions are automatically substituted for the non thread
safe function. You need not specify *_r, you only use *
| Is This Answer Correct ? | 0 Yes | 0 No |
What is Critical section?
When should we use thread-safe "_r" library calls?
What are the main families of threads?
Explain critical section?
Explain what are the main families of threads?
Explain what is scheduling?
Protection boundary??
tell me similarities between thread and process
What are threads?
HOW can I work UNIX commands on Windows XP without installing UNIX O/S in PC
Explain what is protection boundary?
Explain the architectural differences between user-space threads, and kernel-supported threads?