I'd like to add this this.
This is only true for functions declared after the static
object. The static object is unavailable for functions
declared before it (even though they reside in the same
source file).
-Ken
> ----------
> From: [EMAIL PROTECTED][SMTP:[EMAIL PROTECTED]]
> Reply To: [EMAIL PROTECTED]
> Sent: Friday, January 07, 2000 2:14 PM
> To: [EMAIL PROTECTED]
> Subject: Re: why we use static before a function what is the
> significanceof it
>
> objects declared at the global level (this includes procedures),
it
> means that the object in question will only be visible to other
> objects within the same source module. For objects declared within
- Re: why we use static before a function what is the signif... Eric VERGNAUD
- Re: why we use static before a function what is the s... Gaurav Palvia
- Re: why we use static before a function what is the s... Greg Winton
- RE: why we use static before a function what is the s... Richard Hartman
- Re: why we use static before a function what is the s... Mike Davis
- RE: why we use static before a function what is the s... Neil Brown
- Re: why we use static before a function what is the s... dean
- RE: why we use static before a function what is the s... Scott Maxwell
- RE: why we use static before a function what is the s... Yu, Ken
- RE: why we use static before a function what is the s... Greg Winton
