Harold Hallikainen wrote:
> As you and others have pointed out, the key is to make the function
> static. I've always thought the dual use of the word static was strange.
> It makes most sense to me in declaring a local variable. There, the word
> static is the opposite of the word dynamic. The memory is statically
> (permanently) allocated as opposed to being allocated just within the
> function, the deallocated.
> 
> The other use of the word static (outside a function) speaks to the scope
> of the variable (or function) instead of how the memory is allocated.
> Static here means the variable or function is visible only in this source
> file. I can't really think of why the word "static" was used here. In the
> memory allocation case, it makes sense, as static is unchanging. The
> allocation does not change. But how do we make sense of the word static
> with regard to scope? Or was this just a way of saving a little space in
> the parsing mechanism of the compiler (fewer key words to deal with - the
> meaning depends upon the location)?

Harold, I'm with you. :)



-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist