From: Ian Lance Taylor <ian@cygnus.com>
To: pcg@goof.com
Cc: egcs@cygnus.com
Subject: Re: i386.c warnings cleanup
Date: Mon, 09 Feb 1998 19:49:00 -0000 [thread overview]
Message-ID: <199802100349.WAA07459@subrogation.cygnus.com> (raw)
In-Reply-To: <19980210041543.12242@cerebro.laendle>
Date: Tue, 10 Feb 1998 04:15:43 +0100
From: Marc Lehmann <pcg@goof.com>
+extern void error PVPROTO((char *s, ...));
+extern int atoi PROTO((char *));
+extern void bcopy PROTO((void *, void *, int n));
+extern void set_float_handler PROTO((jmp_buf));
+extern void free PROTO((void *));
It's safest to never declare system functions, but to instead get the
declarations from system header files. That's because on old systems
you can't predict how the functions will be declared. For example,
the SunOS <stdlib.h> declares free as returning int.
You should instead simply include the correct header files, and trust
them.
Ian
next prev parent reply other threads:[~1998-02-09 19:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-09 19:27 Marc Lehmann
1998-02-09 19:49 ` Ian Lance Taylor [this message]
1998-02-10 0:53 ` Jeffrey A Law
1998-02-10 3:34 ` Robert Lipe
1998-02-11 0:47 ` Marc Lehmann
1998-02-12 2:36 ` Jeffrey A Law
1998-02-11 0:47 ` Jeffrey A Law
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199802100349.WAA07459@subrogation.cygnus.com \
--to=ian@cygnus.com \
--cc=egcs@cygnus.com \
--cc=pcg@goof.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).