X-Spam-Check-By: sourceware.org Date: Mon, 14 May 2007 09:17:04 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: missing functions Message-ID: <20070514131704.GA25416@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20070514121228 DOT GC12259 AT calimero DOT vinschen DOT de> <4648549E DOT 40203 AT byu DOT net> <20070514122516 DOT GA7880 AT ednor DOT casa DOT cgf DOT cx> <46485A5F DOT 6070705 AT byu DOT net> <20070514125302 DOT GA7978 AT ednor DOT casa DOT cgf DOT cx> <46486078 DOT 30409 AT byu DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46486078.30409@byu.net> User-Agent: Mutt/1.5.11 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 On Mon, May 14, 2007 at 07:13:28AM -0600, Eric Blake wrote: >According to Christopher Faylor on 5/14/2007 6:53 AM: >>>Does cygwin care about providing reentrant versions of functions? >>>There is precedent for doing this: as an example, cygwin.din already >>>exports asprintf_r. >> >>That was probably one of many ill-conceived entries in cygwin.din, >>then. If there is no POSIX or linux version of a function there is no >>reason to export it. > >Then here's the revised list of functions I still think are worth >exporting: > >_Exit asnprintf dprintf vasnprintf vdprintf > >And seeing as how Linux does not yet provide [v]asnprintf, here are my >arguments for exporting it: > >http://sourceware.org/ml/newlib/2007/msg00403.html > >In other words, there are several existing programs ported to cygwin >that would benefit from smaller size and slightly faster execution if >asnprintf were exposed as part of cygwin1.dll, and the size impact to >cygwin1.dll to provide this nice hook is much smaller than the impact >of implementing asnprintf in program space as a less efficient wrapper >around snprintf. As long as you're relatively certain that we're not going to have to stand on our heads to provide an alternative vasnprintf which has subtly different qualities at some point, the above list looks great to me. cgf -- 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/