X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <40a670230710212258ya39bbcaua842ec5b8adcd3be@mail.gmail.com> Date: Sun, 21 Oct 2007 22:58:44 -0700 From: "Roman Mashak" To: cygwin AT cygwin DOT com Subject: Re: "man pages" for pthread_* functions In-Reply-To: <471C2998.6CAA5264@dessent.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <40a670230710212122m42027ef7pe9cfc6f309cfff4c AT mail DOT gmail DOT com> <471C2998 DOT 6CAA5264 AT dessent DOT net> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 2007/10/21, Brian Dessent : > We don't provide man pages for all functions, because nobody has written > or contributed them. The ones we do provide come from newlib, but > newlib does not implement any of the pthread code. > > Since pthreads are standardized you can find good documentation in the > SUS, e.g. > . > For a list of what portions of the various standards Cygwin supports (as > well as implementation-specific notes), consult > . > Alright, I see. Thanks. -- Roman -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/