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
Date:	Tue, 17 Apr 2001 17:19:46 -0400 (EDT)
From:	Charles Wilson <cwilson AT ece DOT gatech DOT edu>
X-Sender:	cwilson AT frontal DOT ibb DOT gatech DOT edu
To:	cygwin AT sources DOT redhat DOT com
cc:	cwilson AT ece DOT gatech DOT edu
Subject:	vfscanf in newlib
Message-ID:	<Pine.GSO.4.20.0104171712130.23663-100000@frontal.ibb.gatech.edu>
MIME-Version:	1.0

I'm trying to fix the scanw() problem in ncurses (it doesn't work because
the vsscanf() function is missing).  

I've basically implemented vsscanf by setting up a fake FILE structure,
and then I want to call vfscanf() on that fake FILE.  However, I then
discovered that, although newlib contains an internal function
'__svfscanf()' which is the guts of scanf(), fscanf(), and sscanf(),
newlib does NOT contain a vfscanf().

This is wierd because vfscanf() would just be trivial wrapper around
__svfscanf().

Since newlib doesn't contain vfscanf(), cygwin doesn't contain it either
-- and cygwin doesn't export __svfscanf().

Does anybody know why newlib doesn't implement a trival vfscanf() wrapper
around __svfscanf() ?  I'd really rather not reimplement all the guts of
__svfscanf() just to get vfscanf() & vsscanf() working for ncurses'
scanw().  Or, would it be acceptable to generate a patch to cygwin that
implements vfscanf() as an exported wrapper for the non-exported
__svfscanf()?

--Chuck



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -