Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!uwvax!oddjob!gargoyle!ihnp4!ttrdc!levy
From: levy@ttrdc.UUCP
Newsgroups: comp.lang.c
Subject: RTFCM (was: Re: static stuff...)
Message-ID: <1985@ttrdc.UUCP>
Date: Wed, 18-Nov-87 13:14:32 EST
Article-I.D.: ttrdc.1985
Posted: Wed Nov 18 13:14:32 1987
Date-Received: Tue, 24-Nov-87 05:46:06 EST
References: <3011@sigi.Colorado.EDU>
Organization: AT&T, Skokie, IL
Lines: 19

In article <3011@sigi.Colorado.EDU>, swarbric@tramp.Colorado.EDU (SWARBRICK FRANCIS JOHN) writes:
> First, what is the significance of making a static function?

Static functions' names are only "visible" within the file that contains them.
That is, they cannot be referenced, either accidentally or on purpose, by means
of using their symbolic names in any other source file in the program.

> Second, aren't all global variables automatically static.  Is there any
> reason to explicitly call them static?
> swarbric@tramp.UUCP

Static variables declared outside a function are only "global" to the file
that contains them.  Like static functions, they cannot be accessed by name
from any other source file in the program.
-- 
|------------Dan Levy------------|  Path: ..!{akgua,homxb,ihnp4,ltuxa,mvuxa,
|         an Engihacker @        |  	<most AT&T machines>}!ttrdc!ttrda!levy
| AT&T Computer Systems Division |  Disclaimer?  Huh?  What disclaimer???
|--------Skokie, Illinois--------|