Xref: utzoo comp.std.c:388 comp.lang.c:12666
Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!amdcad!ames!haven!umd5!adm!smoke!gwyn
From: gwyn@smoke.ARPA (Doug Gwyn )
Newsgroups: comp.std.c,comp.lang.c
Subject: Re: C function prototyping and large projects
Message-ID: <8508@smoke.ARPA>
Date: 16 Sep 88 14:43:33 GMT
References: <24@motto.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 16

In article <24@motto.UUCP> russ@motto.UUCP (Russell Crook) writes:
>Are there conventions about where prototypes are stored -
>do you put them in '.h' files, or right in the source file, or
>somewhere else?

Prototypes don't change the recommended C practice, namely use
header files to define/declare all interface information.  The
best approach is to use separate headers (and separate source
files) for each group of functionally related capabilities.
For example, "parse.h" would declare the parsing function(s)
that are of use to other parts of the application, and it would
also define any manifest constants, data types, etc. that are
specific to parsing.  Other headers would cover other functional
areas.  And of course, a Makefile or equivalent compilation
specification could be used to limit recompilation to just the
affected sources when a change has been made.