Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
From: "Paul K. Fisher" <pfisher AT plexware DOT com>
To: "Cygwin Developers" <cygwin-developers AT sourceware DOT cygnus DOT com>
Subject: Reason for cover functions in pthread.cc
Date: Sun, 7 May 2000 22:43:31 -0500
Message-ID: <000001bfb89f$94694120$6401a8c0@jupiter>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal

Is there a reason to keep the cover functions in pthread.cc?  These simply
call "__" prefixed versions in thread.cc, where the real implementation is
provided.

For example:
int
pthread_attr_init (pthread_attr_t * attr)
{
  return __pthread_attr_init (attr);
}


paul