Path: utzoo!utgpu!water!watmath!clyde!rutgers!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: initializing
Message-ID: <7140@brl-smoke.ARPA>
Date: 19 Jan 88 15:55:13 GMT
References: <303@Aragorn.dde.uucp>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 11

In article <303@Aragorn.dde.uucp> be@dde.uucp (Bjorn Engsig) writes:
>BTW, gwyn@brl-smoke.ARPA (Doug Gwyn @ Ballistic Research Lab (BRL), APG, MD.) writes:
>> Supply static initializers in some place that makes sense,
>> for example in the source code for the module that owns the data.
>This is good for statics but NOT for externals.

It's not even an issue for statics!
I disagree completely with the approach that external data should be
thought of as just one big amorphous pool of generally-accessible
information.  It is not what one would obtain by following structured
design methodologies.