5 The @code{inet_ntoa} function need not be reentrant, and consequently
6 is not required to be thread safe. Implementations of
7 @code{inet_ntoa} typically write the time stamp into static buffer.
8 If two threads call @code{inet_ntoa} at roughly the same time, you
9 might end up with the wrong date in one of the threads, or some
10 undefined string. Further, @code{inet_ntoa} is specific for
11 @acronym{IPv4} addresses.
13 A protocol independent function is @code{inet_ntop}.