Effects of the extern keyword on C functions

by

We have two files, foo.c and bar.c.

Here is foo.c

#include <stdio.h>

volatile unsigned int stop_now = 0;
extern void bar_function(void);

int main(void)
{
  while (1) {
     bar_function();
     stop_now = 1;
  }
  return 0;
}

Now, here is bar.c

#include <stdio.h>

extern volatile unsigned int stop_now;

void bar_function(void)
{
   if (! stop_now) {
      printf("Hello, world!\n");
      sleep(30);
   }
}

As you can see, we have no shared header between foo.c and bar.c , however bar.c needs something declared in foo.c when it’s linked, and foo.c needs a function from bar.c when it’s linked.

By using ‘extern’, you are telling the compiler that whatever follows it will be found (non-static) at link time; don’t reserve anything for it in the current pass since it will be encountered later. Functions and variables are treated equally in this regard.

It’s very useful if you need to share some global between modules and don’t want to put / initialize it in a header.

Technically, every function in a library public header is ‘extern’, however labeling them as such has very little to no benefit, depending on the compiler. Most compilers can figure that out on their own. As you see, those functions are actually defined somewhere else.

In the above example, main() would print hello world only once, but continue to enter bar_function(). Also note, bar_function() is not going to return in this example (since it’s just a simple example). Just imagine stop_now being modified when a signal is serviced (hence, volatile) if this doesn’t seem practical enough.

Externs are very useful for things like signal handlers, a mutex that you don’t want to put in a header or structure, etc. Most compilers will optimize to ensure that they don’t reserve any memory for external objects, since they know they’ll be reserving it in the module where the object is defined. However, again, there’s little point in specifying it with modern compilers when prototyping public functions.

Hope that helps 🙂

More Related Contents:

  1. What does “static” mean in C?
  2. What does double underscore ( __const) mean in C?
  3. Arrow operator (->) usage in C
  4. How do you pass a function as a parameter in C?
  5. Is unsigned integer subtraction defined behavior?
  6. Is an empty initializer list valid C code?
  7. An example of use of varargs in C
  8. Does printf(“%x”,1) invoke undefined behavior?
  9. What is the full “for” loop syntax in C?
  10. Declare main prototype
  11. Parenthesis surrounding return values in C
  12. Is the last comma in C enum required?
  13. Two semicolons inside a for-loop parentheses
  14. Bitshift and integer promotion?
  15. Standard C library in mingW
  16. No defined type of a function parameter defaults to int? Am I insane?
  17. List of platforms supported by the C standard
  18. Difference between scanf() and strtol() / strtod() in parsing numbers
  19. What does a “CALLBACK” declaration in C do?
  20. 3 plus symbols between two variables (like a+++b) in C [duplicate]
  21. Why both clang and gcc only give a warning when there is a space after backslash if C standard says that whitespace is forbidden?
  22. What does \x mean in C/C++?
  23. double negation in C : is it guaranteed to return 0/1?
  24. Can a conversion from double to int be written in portable C
  25. Which section in C89 standard allows the “implicit int” rule?
  26. C fundamentals: double variable not equal to double expression?
  27. Is a compiler allowed to add functions to standard headers?
  28. In a C function declaration, what does “…” as the last parameter do?
  29. Returning function pointer type
  30. What constitutes a “valid” C Identifier?

Leave a Comment