Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Initializing variables in C

Tags:

I know that sometimes if you don't initialize an int, you will get a random number if you print the integer.

But initializing everything to zero seems kind of silly.

I ask because I'm commenting up my C project and I'm pretty straight on the indenting and it compiles fully (90/90 thank you Stackoverflow) but I want to get 10/10 on the style points.

So, the question: when is it appropriate to initialize, and when should you just declare a variable:

int a = 0; 

vs.

int a; 
like image 476
Arthur Collé Avatar asked Nov 02 '11 01:11

Arthur Collé


People also ask

What is variable initialization in C?

Variables are names given to these memory locations. The memory location referred to by this variable holds a value of our interest. Now, these variables once declared, are assigned some value. This assignment of value to these variables is called initialization of variables.

Can we initialize variable in C?

Unlike PASCAL, in C variables may be initialized with a value when they are declared. Consider the following declaration, which declares an integer variable count which is initialized to 10. Lets examine what the default value a variable is assigned when its declared.

What are initializing variables?

Initializing a variable means specifying an initial value to assign to it (i.e., before it is used at all). Notice that a variable that is not initialized does not have a defined value, hence it cannot be used until it is assigned such a value.

What is variable initialization example?

Variable initialization in C++ Variables are the names given by the user. A datatype is also used to declare and initialize a variable which allocates memory to that variable. There are several datatypes like int, char, float etc. to allocate the memory to that variable. There are two ways to initialize the variable.


2 Answers

There are several circumstances where you should not initialize a variable:

  1. When it has static storage duration (static keyword or global var) and you want the initial value to be zero. Most compilers will actually store zeros in the binary if you explicitly initialize, which is usually just a waste of space (possibly a huge waste for large arrays).
  2. When you will be immediately passing the address of the variable to another function that fills its value. Here, initializing is just a waste of time and may be confusing to readers of the code who wonder why you're storing something in a variable that's about to be overwritten.
  3. When a meaningful value for the variable can't be determined until subsequent code has completed execution. In this case, it's actively harmful to initialize the variable with a dummy value such as zero/NULL, as this prevents the compiler from warning you if you have some code paths where a meaningful value is never assigned. Compilers are good at warning you about accessing uninitialized variables, but can't warn you about "still contains dummy value" variables.

Aside from these issues, I'd say it's generally good practice to initialize your non-static variables when possible.

like image 55
R.. GitHub STOP HELPING ICE Avatar answered Oct 22 '22 11:10

R.. GitHub STOP HELPING ICE


A rule that hasn't been mentioned yet is this: when the variable is declared inside a function it is not initialised, and when it is declared in static or global scope it's set to 0:

int a; // is set to 0  void foo() {   int b;  // set to whatever happens to be in memory there } 

However - for readability I would usually initialise everything at declaration time.

If you're interested in learning this sort of thing in detail, I'd recommend this presentation and this book

like image 30
Timothy Jones Avatar answered Oct 22 '22 11:10

Timothy Jones