- // Problem: But if strerror_r() isn't present, we're not thread safe!
- // Solution: Tough. It's still better than nothing. I think.
- // Check UnixMarshal.IsErrorDescriptionThreadSafe if you need to
- // know which error translator is being used.
+ // Strerror(3) will be thread-safe from managed code, but won't
+ // be thread-safe between managed & unmanaged code.