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.
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.
Comments
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!!
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!
will return! I peep the web for blogs just like this
one.
Click on my 1800contacts coupon codes blog before its to late.
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!
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!
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.
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.
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.
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.
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!
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.
golden slot mobile