Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!cbosgd!ihnp4!inuxc!pur-ee!uiucdcs!convex!ndm20!lvs
From: lvs@ndm20
Newsgroups: net.unix-wizards
Subject: Re: 'static' function?
Message-ID: <28800006@ndm20>
Date: Mon, 7-Jul-86 12:49:00 EDT
Article-I.D.: ndm20.28800006
Posted: Mon Jul  7 12:49:00 1986
Date-Received: Thu, 10-Jul-86 04:49:04 EDT
References: <131@kaist.UUCP>
Lines: 24
Nf-ID: #R:kaist.UUCP:131:ndm20:28800006:37777777600:962
Nf-From: ndm20!lvs    Jul  7 11:49:00 1986


> jhhur@kaist.UUCP writes:

>What is the meaning of 'static' function?  Does it mean that the return value
>is allocated a memory location rather than the top of C stack?  If so,
>what is the relevance of a memory location for a return value?

The act of declaring a function static in no way affects the return value of
the function.  It merely restricts the scope of the function name to the
file in which it lives.  That is, the name of the function is NOT an external
symbol and may not be referenced by functions in a seperately compiled unit.

Note that this is the only way to restrict the scope of a function name.
Without being defined 'static' all function names are external symbols.


Hope this helps,
Larry V. Streepy Jr.                        "Waiting is"
Nathan D. Maier Consulting Engineers

VOICE:  (214)739-4741
Usenet: {seismo!c1east | cbosgd!sun | ihnp4}!convex!infoswx!ndm20!lvs
CSNET:  ndm20!lvs@smu
ARPA:   ndm20!lvs%smu@csnet-relay.ARPA