Subj : Re: "File Scope" objects
To   : comp.programming,comp.software-eng
From : Gerry Quinn
Date : Sat Aug 27 2005 02:56 am

Organization: Bindweed Entertainment Software
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
User-Agent: MicroPlanet-Gravity/2.60.2060
Lines: 16
Date: Sat, 27 Aug 2005 10:26:43 +0100
NNTP-Posting-Host: 83.71.88.20
X-Complaints-To: abuse@eircom.net
X-Trace: news.indigo.ie 1125134806 83.71.88.20 (Sat, 27 Aug 2005 10:26:46 BST)
NNTP-Posting-Date: Sat, 27 Aug 2005 10:26:46 BST
Xref: newsmst01b.news.prodigy.com comp.programming:223288 comp.software-eng:113523

In article <rfoug1dt5ngs5vi10krp7eiugcpnuvo0cq@4ax.com>, 
Chris@Sonnack.com says...

> But what does this have to do with file scope (private) variables?
> 
> One place I've thought of where they are almost necessary is when you
> have a constant data structure shared by several functions.  Say a
> translation table with two-way translation represented by two functions.
> 
> The table is a private file scope datum used by both functions in
> the module.  That seems to me a most elegant solution.

I'll admit that's an appropriate use for a file scope datum, which I 
suppose is formally a class.

- Gerry Quinn

.