• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: possibly OT: threadsafe libc
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: possibly OT: threadsafe libc


  • Subject: Re: possibly OT: threadsafe libc
  • From: Steve Checkoway <email@hidden>
  • Date: Tue, 22 Nov 2005 16:11:10 -0800


On Nov 21, 2005, at 9:45 AM, Eric Albert wrote:

It's unfortunate that we haven't yet documented the thread safety of Libc in the same way as, say, Sun does for its man pages. However, all of Libc is threadsafe except where it's explicitly documented not to be...and I can't think of any cases in which it's documented to not be threadsafe. Mac OS X uses multiple threads very extensively, so a threadsafe Libc is essentially required.

From getaddrinfo(3) and getnameinfo(3):

BUGS
     The implementation of getaddrinfo() is not thread-safe.

BUGS
     The implementation of getnameinfo() is not thread-safe.

- Steve

Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: possibly OT: threadsafe libc
      • From: Damien Bobillot <email@hidden>
References: 
 >possibly OT: threadsafe libc (From: Philip Lukidis <email@hidden>)
 >Re: possibly OT: threadsafe libc (From: Eric Albert <email@hidden>)

  • Prev by Date: Changing automatic header insert
  • Next by Date: Re: Changing automatic header insert
  • Previous by thread: Re: possibly OT: threadsafe libc
  • Next by thread: Re: possibly OT: threadsafe libc
  • Index(es):
    • Date
    • Thread