ghostrider123
Newbie level 3
Why is it compulsory to initialize static variables during compile time only?
Welcome to EDAboard.com
Welcome to our site! EDAboard.com is an international Electronic Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
C static variables initialization
- Thread starter ghostrider123
- Start date
- Status
- Joined
- Jul 4, 2009
- Messages
- 14,598
- Helped
- 4,784
- Reputation
- 9,585
- Reaction score
- 4,565
- Trophy points
- 1,393
- Location
- Aberdyfi, West Wales, UK
- Activity points
- 124,425
It isn't usually compulsory but it makes sense to.
A static variable retains it's value between calls to the function, normally a local variable is lost when the function finishes. As such, it should hold a sensible value so the first time the function is called, it already has something in it.
Brian.
A static variable retains it's value between calls to the function, normally a local variable is lost when the function finishes. As such, it should hold a sensible value so the first time the function is called, it already has something in it.
Brian.
- Joined
- Jan 22, 2008
- Messages
- 47,875
- Helped
- 14,125
- Reputation
- 28,507
- Reaction score
- 12,809
- Trophy points
- 1,393
- Location
- Bochum, Germany
- Activity points
- 277,851
I don't understand the exact meaning of "initialize static variables during compile time". By C specification, static variables are zeroed at application startup, an action that obviously not occurs "at compile time".
What would be the alternative? I think only disabling initialization of all or part of the static variables, which is an option with some compilers.
What would be the alternative? I think only disabling initialization of all or part of the static variables, which is an option with some compilers.
- Status
