This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: patch to clean out savestring, copystr, mybzero and mybcopy
- To: egcs-patches at cygnus dot com
- Subject: Re: patch to clean out savestring, copystr, mybzero and mybcopy
- From: Ulrich Drepper <drepper at cygnus dot com>
- Date: 12 Jan 1999 14:24:39 -0800
- Newsgroups: cygnus.egcs.patches
- Organization: Cygnus Solutions
- References: <199901122106.QAA04969.cygnus.egcs.patches@caip.rutgers.edu>
- Reply-To: drepper at cygnus dot com (Ulrich Drepper)
ghazi@caip.rutgers.edu (Kaveh R. Ghazi) writes:
> What standards govern bzero (etc) definitions?
Unix98 (and any previous X/Open standard).
> One thing I'm wondering about, do we have to worry about prototypes
> for bzero not being consistent? Ie. on OSF4 it takes a char*
> pointer and on Solaris2, it takes a void* pointer. Does that
> matter?
It does not matter unless you redeclare the function. You might get
warnings in a high warning level but you could solve this by defining
#define bzero(ptr, n) bzero ((char *) ptr, n)
on systems which take a char *.
--
---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Cygnus Solutions `--' drepper at cygnus.com `------------------------