use _ and __ in C programs [duplicate]

Answer 1

Here's what the C standard says (section 7.1.3):

• All identifiers that begin with an underscore and either an uppercase letter or another underscore are always reserved for any use.
• All identifiers that begin with an underscore are always reserved for use as identifiers with file scope in both the ordinary and tag name spaces.

(The section goes on to list specific identifiers and sets of identifiers reserved by certain standard headers.)

What this means is that for example, the implementation (either the compiler or a standard header) can use the name __FOO for anything it likes. If you define that identifier in your own code, your program's behavior is undefined. If you're "lucky", you'll be using an implementation that doesn't happen to define it, and your program will work as expected.

This means you simply should not define any such identifiers in your own code (unless your own code is part of a C implementation -- and if you have to ask, it isn't). There's no need to define such identifiers anyway; there's hardly any shortage of unreserved identifiers.

You can use an identifier like _foo as long as it's defined locally (not at file scope) -- but personally I find it much easier just to avoid using leading underscores at all.

Incidentally, your example of _sqrt doesn't necessarily illustrate the point. An implementation may define the name _sqrt in <math.h> (since anything defined there is at file scope), but there's no particular reason to expect that it will do so. When I compile your program, I get a warning:

c.c:7:1: warning: implicit declaration of function ‘_sqrt’ [-Wimplicit-function-declaration]

because <math.h> on my system doesn't define that identifier, and a link-time fatal error:

/tmp/cc1ixRmL.o: In function `main':
c.c:(.text+0x1a): undefined reference to `_sqrt'

because there's no such symbol in the library.

Answer 2

It's a naming convention, this means that violating this rule will not immediately and directly lead to breaking your program, but it's a really really really really really really [ + infinite times ] a good idea to follow the convention.

The essence of the convention is to reserve :

• naming starting with _ for the language entities, which includes the standard library
• naming starting with __ for the compiler internals

it's also a really platform specific topic most of the times, many vendors respect this convention but they also have their own naming conventions and guidelines .

You can find more by search for c double underscore naming convention

Answer 3

tl; dr You got it backwards. Name your own stuff without leading underscores, unless you're writing a library for someone else. The standard library and compilers use the technique to signal that certain names are internal, and not to be used directly.

Underscores for Uniqueness

In C, there are no namespaces. In other words, all names included into a file can collide with each other. If foo.h and bar.h both define x, an error will occur when they are both included.

Now, x is a pretty common name. Collision is almost guaranteed, and the writers of foo.h and bar.h must realize that. So, in the interest of avoiding future problems for the programmers that will use their code, they change the name to _x.

Alternatives

Common names do occur. Before resorting to underscoring, try:

1. Separating private from public variables in .c and .h files. Most clashing names are private, and don't belong in the header.

2. Prefixing your code with the name of the module: foo_x and bar_x won't collide.