Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <001901c17ae3$1c5964f0$2ac627d8@dragonware.com>
From: "Steve Mertz" <steve AT dragon-ware DOT com>
To: <cygwin AT cygwin DOT com>
Subject: lib/include files and compiling...
Date: Sat, 1 Dec 2001 21:40:39 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

Hi.

Just curious as to why in /usr/include/stdio.h:
FILE *  _EXFUN(tmpfile, (void));

While many others (Linux, OpenBSD) have
extern FILE *tmpfile __P ((void));

What is the motivation behind putting the _EXFUN infront of the 'tmpfile'
instead of behind it?   I am finding that this is causing some compatibility
problems and I cannot compile things because of it.


Thanks!
-- Steve



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/