Xref: utzoo comp.lang.c:8607 comp.sys.ibm.pc:13791
Path: utzoo!utgpu!water!watmath!clyde!rutgers!gatech!ncsuvx!ece-csc!ncrcae!ncr-sd!crash!gryphon!sarima
From: sarima@gryphon.CTS.COM (Stan Friesen)
Newsgroups: comp.lang.c,comp.sys.ibm.pc
Subject: Re: C declaration styles
Message-ID: <3024@gryphon.CTS.COM>
Date: 27 Mar 88 23:21:11 GMT
References: <5699@watdragon.waterloo.edu> <1065@sask.UUCP> <8695@tut.cis.ohio-state.edu> <18359@sci.UUCP>
Reply-To: sarima@gryphon.CTS.COM (Stan Friesen)
Organization: Trailing Edge Technology, Redondo Beach, CA
Lines: 11

In article <18359@sci.UUCP> phil@sci.UUCP (Phil Kaufman) writes:
>      ...
>Declarations for functions are wonderful and avoid many errors but can 
>anyone tell me what the effect of the static modifier has in a function
>definition? I have often seen the following:
>       static int foofunction (int, int)

	Quite simply, it means the function is limited in scope to the
current file, it is a *private* function not visible to the rest of the
world. This is very useful for producing modular code without worrying
about name conflicts.