acadia-newlib/winsup/cygwin/libc
Corinna Vinschen acc5f02ce8 Throughout Cygwin, use u_intN_t or uintN_t
Don't use u_char, u_short, u_int or u_long in Cygwin, unless it refers
to the Winsock types.  Use u_intN_t in BSD-based sources, unsigned char
where strings are concerned, uintN_t otherwise.  Also:

	* net.cc: Fix comment, we're not using u_long anymore.

Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
2016-03-24 16:39:15 +01:00
..
arc4random_stir.c Throughout Cygwin, use u_intN_t or uintN_t 2016-03-24 16:39:15 +01:00
base64.c Throughout Cygwin, use u_intN_t or uintN_t 2016-03-24 16:39:15 +01:00
bsdlib.cc
fnmatch.c Feature test macros overhaul: fnmatch.h 2016-03-17 21:08:54 -05:00
fts.c
ftw.c
getopt.c
inet_addr.c Throughout Cygwin, use u_intN_t or uintN_t 2016-03-24 16:39:15 +01:00
inet_network.c
minires-os-if.c Throughout Cygwin, use u_intN_t or uintN_t 2016-03-24 16:39:15 +01:00
minires.c Throughout Cygwin, use u_intN_t or uintN_t 2016-03-24 16:39:15 +01:00
minires.h
nftw.c
rcmd.cc Throughout Cygwin, use u_intN_t or uintN_t 2016-03-24 16:39:15 +01:00
rexec.cc Throughout Cygwin, use u_intN_t or uintN_t 2016-03-24 16:39:15 +01:00
strfmon.c Feature test macros overhaul: stdlib.h 2016-03-17 21:09:06 -05:00
strptime.cc Throughout Cygwin, use u_intN_t or uintN_t 2016-03-24 16:39:15 +01:00
xsique.cc