From owner-freebsd-hackers Fri Feb 5 15:51:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21942 for freebsd-hackers-outgoing; Fri, 5 Feb 1999 15:51:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21937 for ; Fri, 5 Feb 1999 15:51:22 -0800 (PST) (envelope-from drew@pluto.plutotech.com) Received: (from drew@localhost) by pluto.plutotech.com (8.9.1/8.9.1) id QAA17773; Fri, 5 Feb 1999 16:51:19 -0700 (MST) (envelope-from drew) Date: Fri, 5 Feb 1999 16:51:19 -0700 (MST) From: Drew Eckhardt Message-Id: <199902052351.QAA17773@pluto.plutotech.com> To: Matthew.Alton@anheuser-busch.com Cc: hackers@FreeBSD.ORG Subject: Re: C headers In-Reply-To: <31B3F0BF1C40D11192A700805FD48BF90177670F@STLABCEXG011> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <31B3F0BF1C40D11192A700805FD48BF90177670F@STLABCEXG011> you write: >Why does printf() non need #include like the man page says? Because K&R doesn't require function prototypes and you don't use any types or pre-processor macros defined in the header. Things would be different if you used fprintf(3). In any case, including is a good idea because it allows prototypes which take advantage of gcc's printf-format string prototype extension (why doesn't do this?) to verify that the arguments match what's been passed in. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message