This is the mail archive of the
mailing list for the Cygwin project.
- From: "Dave Korn" <dk at artimi dot com>
- To: <cygwin at cygwin dot com>
- Date: Mon, 19 Apr 2004 15:25:39 +0100
- Subject: RE: libc
> -----Original Message-----
> From: cygwin-owner On Behalf Of Richard Campbell
> Sent: 19 April 2004 15:12
> >Libc has as a standard catgets. But catgets and catopen are
> absent from the
> >cygwin implementation and gencat and nl_types are not to be found.
> >So where can I find either the source for these or a technical spec?
> Switched to the main cygwin list.
> Cygwin uses newlib.
Also, cygwin implements a POSIX layer in compliance with the single unix
standard SUSv3. It doesn't attempt to implement all the potential
extensions. If you look up catgets in SUSv3, you'll see it's tagged with a
little "XSI" tag, which means:
" The functionality described is an XSI extension. Functionality marked XSI
is also an extension to the ISO C standard. Application writers may
confidently make use of an extension on all systems supporting the X/Open
System Interfaces Extension. "
Since cygwin uses, as you say, newlib, you'll find that you can really
only rely on the core POSIX functions being implemented. To find out what
functions are included in cygwin, see
http://cygwin.com/cygwin-api/cygwin-api.html . To find out the technical
specs for them, as well as any unimplemented extensions, see the SUSv3 at
http://www.opengroup.org/onlinepubs/007904975/ . For the sources to the
missing functions, well...... think about it........
[hint: glibc is an open source software package]
Can't think of a witty .sigline today....
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html