Path: utzoo!attcan!uunet!lll-winken!indri!larry!jwp
From: jwp@larry.sal.wisc.edu (Jeffrey W Percival)
Newsgroups: comp.lang.c
Subject: Re: declarations in include files:  how do YOU feel?
Keywords: declarations include
Message-ID: <180@larry.sal.wisc.edu>
Date: 11 May 89 17:00:29 GMT
References: <179@larry.sal.wisc.edu> <11318@bloom-beacon.MIT.EDU>
Reply-To: jwp@larry.sal.wisc.edu.UUCP (Jeffrey W Percival)
Organization: Space Astronomy Lab, Madison, WI
Lines: 15

In article <11318@bloom-beacon.MIT.EDU> scs@athena.mit.edu (Steve Summit) writes:
>In article <179@larry.sal.wisc.edu> jwp@larry.sal.wisc.edu (Jeffrey W Percival) writes:
>>Should the lib.h file contain extern declarations for everything in lib.a?
>By all means.
>I've never worried about micro-managing global scope.
>If it's extern, it's global, so any module may call it.

Thanks for the response.  Is this the general consensus?

Another question on this style:  does one include lib.h in the
subroutine files that make up lib.a?  That is, if lib.h contains
an "extern char foo()" and foo.c includes lib.h and then goes
on to define foo, is this a problem?
-- 
Jeff Percival (jwp@larry.sal.wisc.edu)