X-Spam-Check-By:	sourceware.org
Date:	Mon, 14 May 2007 14:12:28 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: missing functions
Message-ID:	<20070514121228.GC12259@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<loom DOT 20070502T004544-728 AT post DOT gmane DOT org>
Mime-Version:	1.0
In-Reply-To:	<loom.20070502T004544-728@post.gmane.org>
User-Agent:	Mutt/1.4.2.2i
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On May  1 22:55, Eric Blake wrote:
> I noticed a couple of functions that cause link errors even though they are 
> required by POSIX (or at least will be required by the next version of POSIX), 
> implemented by newlib, and declared in the headers:
> 
> _Exit
> dprintf
> 
> There is also a big list of integer-only and reentrant variants of *printf that 
> might be worth exporting:
> 
> asiprintf, _asiprintf, asiprintf_r, _asiprintf_r, diprintf, _diprintf, 
> diprintf_r, _diprintf_r, _dprintf, dprintf_r, _dprintf_r, fiprintf_r, 
> _fiprintf_r, fprintf_r, _fprintf_r, iprintf_r, _iprintf_r, printf_r, _printf_r, 
> siprintf_r, _siprintf_r, sniprintf, _sniprintf, sniprintf_r, _sniprintf_r, 
> snprintf_r, _snprintf_r, sprintf_r, _sprintf_r, vasiprintf, _vasiprintf, 
> vasiprintf_r, _vasiprintf_r, vdiprintf, _vdiprintf, vdiprintf_r, _vdiprintf_r, 
> vdprintf, _vdprintf, vdprintf_r, _vdprintf_r, vfiprintf_r, _vfiprintf_r, 
> vfprintf_r, _vfprintf_r, viprintf, _viprintf, viprintf_r, _viprintf_r, 
> vprintf_r, _vprintf_r, vsiprintf, _vsiprintf, vsiprintf_r, _vsiprintf_r, 
> vsniprintf, _vsniprintf, vsniprintf_r, _vsniprintf_r, vsnprintf_r, 
> _vsnprintf_r, vsprintf_r, _vsprintf_r

Why the underscore variants?  Are they covered by any standard?  If not,
we don't export these variants anymore.  The existing ones have been
originally exported to maintain some compatibility to msvcrt, but this
is a moot point for a long time.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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/

- Raw text -