Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ames!pacbell!att!chinet!les
From: les@chinet.UUCP (Leslie Mikesell)
Newsgroups: comp.lang.c
Subject: Re: Initialization in #include files
Message-ID: <5791@chinet.UUCP>
Date: 10 Jun 88 02:45:47 GMT
References: <28400001@ntvax> <6104@sigi.Colorado.EDU> <2955@ihlpe.ATT.COM> <7948@brl-smoke.ARPA> <851@.UUCP> <1021@mit-caf.UUCP> <5776@chinet.UUCP> <8046@brl-smoke.ARPA>
Reply-To: les@chinet.UUCP (Leslie Mikesell)
Organization: Chinet - Public Access Unix
Lines: 13

In article <8046@brl-smoke.ARPA> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) ) writes:
>>But the variables are very likely to be used in every source file, ...
>
>I do hope you people know better than to design software with lots
>of pathological inter-module connections like this.

OK, where do *you* put all the things that have default values that can
be altered by options on the command line?  Do you use pathological
globals or pass about 50 parameters to every function called from main()?
What about state variables?  What about things that need to be cleaned
up in case of interrupts or error exits?  Somehow about 50% of the variables
seem to fall in one of these classes in a lot of my programs.
  
 Les Mikesell