Skip to main content
My recent experience of programming in C tell me following things:

1. ALWAYS! ALWAYS!! ALWAYS!!! initialize local variables in C.
pointer, integers, chars, user defined structures whatever it is.
Initialize. Uninitialized variables are especially dangerous in
highly recursive programs because somewhere, at some invocation
the variable assumes the 'bad' value and catastrophic results happen
somewhere down in the call stack. You can initialize local
structured data-types such as array and structures using following syntax.

Message m = { 0 } ;
This makes all the elements of the structure equal to zero.
(Message is a type definition for a struct Message_tag)

int i[5] = { 10 } ;
This will make only first element of array i equal to 10, all other will be
zero. Also note that, globals, statics are always by default initialized to
zero. This is not the case with locals. But little more typing can save you
lot of trouble.

2. Containers should hold your data, followed by local variables and lastly
local pointers. I prefer to allocated as much data on stack as possible. The language
takes care of deallocating memory for you. For example, I have a list of
messages in C. This is not a std::list<> in C++. Following way avoids
many pitfalls.

1. Declare a local variable: "Message m;"
2. Ask the list to make a copy of message to be added and store
the copy in the list. List takes care of creating a copy,
copying data. You have to implement list in that way.
3. When extracting out from the list, extract message in a local
variable again. (Use pass by reference technique) List copies the
data for you in the (reference passed) local variable. List also
takes care of deallocating the copy of message it has.

This means you are not holding your data except one local variable at
a time. This will save you especially when a recursive function is
manipulating lists.


Anonymous said…
Are these struct and array initializers part of the C standard or are they GCC extensions?
Sumant said…
Yes, it is a C standard. You can find more detailed initialization styles supported by C99 standard in section 6.7.8:Initialization Watch out for a post on incompatibilities between C and C++ initializers.

One strange extension supported by gcc is zero sized arrays. ANSI standard forbids zero sized arrays. In gcc you can still
get address of zero sized array!!
Exciting blog. Your site was amazing and will be
back again! I never get tired of looking for blogs
just like this one.
Hey son, you need to check out my 1800contacts coupon blog!
Enchanting blog. Your site was off the chain and I
will return! I peep the web for blogs just like this
Click on my 1800contacts coupon codes blog before its to late.
Fruitful blog. I favor your site and I shall
return to it! I go to sites like this when I get the
chance, and find blog just like this.
Oh please, check for the blog site with my 1800contacts coupon!
outa-time said…
Nice blog. I seen the site and I adored the work,
that I want to visit it more each day! I like
searching for blogs that have the same content like
this one!
Check out my 1800contacts coupon blog, please!
lightly-blended said…
Incredible blog. I admired your site and I will be
back once again to view it! I use much of my spare
time searching for blogs like yours.
Hey why don't you peep my coupon codes 1800contacts blog site.
Extraordinary blog. Your site was hip and fresh
and we'll visit it again! I love surfing the internet
for blogs.
Sweetie, go and search my blog for what you need.
after-while said…
Inspiring blog. I love finding blogs this good on
the internet, when I have the time. I'm going to go
back to it!
I want you to look for my 1800contacts coupon codes blog.
Excellent blog. It was so great and I bet I will
go back to it! I get to look online for blogs like
yours is a blessing.
Everyday of the month you need to peep my coupon codes 1800contacts blog.
Energizing blog. It blew me away and I loved your
site. when I have the time to surf the net, i try
finding blogs as good as your site.
Sweetie, go and search my 1800contacts coupon blog for what you need.
Fine blog. I found your site suitable for another
visit! And when I'm able to surf the web, I look for
blogs as great as your work.
You got me! I will check out your male plastic surgery blog a.s.a.p!
Creative blog.  I thought it was the best site out
and we had to go back to it! Every chance I get on the
net I search for blogs just like your site.
Check out my plastic surgery las vegas blog, please!
Exciting blog. The site out did itself and will be
back! I love surfing the internet for blogs that are
exactly like this blog.
In my spare time I will look for your plastic surgery houston blog.
Anonymous said…
Thanks you so much for sharing

golden slot mobile

Popular Content

Multi-dimensional arrays in C++11

What new can be said about multi-dimensional arrays in C++? As it turns out, quite a bit! With the advent of C++11, we get new standard library class std::array. We also get new language features, such as template aliases and variadic templates. So I'll talk about interesting ways in which they come together. It all started with a simple question of how to define a multi-dimensional std::array. It is a great example of deceptively simple things. Are the following the two arrays identical except that one is native and the other one is std::array? int native[3][4]; std::array<std::array<int, 3>, 4> arr; No! They are not. In fact, arr is more like an int[4][3]. Note the difference in the array subscripts. The native array is an array of 3 elements where every element is itself an array of 4 integers. 3 rows and 4 columns. If you want a std::array with the same layout, what you really need is: std::array<std::array<int, 4>, 3> arr; That's quite annoying for

Covariance and Contravariance in C++ Standard Library

Covariance and Contravariance are concepts that come up often as you go deeper into generic programming. While designing a language that supports parametric polymorphism (e.g., templates in C++, generics in Java, C#), the language designer has a choice between Invariance, Covariance, and Contravariance when dealing with generic types. C++'s choice is "invariance". Let's look at an example. struct Vehicle {}; struct Car : Vehicle {}; std::vector<Vehicle *> vehicles; std::vector<Car *> cars; vehicles = cars; // Does not compile The above program does not compile because C++ templates are invariant. Of course, each time a C++ template is instantiated, the compiler creates a brand new type that uniquely represents that instantiation. Any other type to the same template creates another unique type that has nothing to do with the earlier one. Any two unrelated user-defined types in C++ can't be assigned to each-other by default. You have to provide a

Unit Testing C++ Templates and Mock Injection Using Traits

Unit testing your template code comes up from time to time. (You test your templates, right?) Some templates are easy to test. No others. Sometimes it's not clear how to about injecting mock code into the template code that's under test. I've seen several reasons why code injection becomes challenging. Here I've outlined some examples below with roughly increasing code injection difficulty. Template accepts a type argument and an object of the same type by reference in constructor Template accepts a type argument. Makes a copy of the constructor argument or simply does not take one Template accepts a type argument and instantiates multiple interrelated templates without virtual functions Lets start with the easy ones. Template accepts a type argument and an object of the same type by reference in constructor This one appears straight-forward because the unit test simply instantiates the template under test with a mock type. Some assertion might be tested in