By default, programming help C language proposes that every one uninitialized static variables are initialized to zero, but due to a couple barriers in TIGCC linker, you want to initialize explicitely all static and global variables if you assemble programming help program in “nostub” mode. The fact that global and static variables are initialized in collect time and kept in programming help executable file itself has one critical consequence, that is not present on “average” computers like PC, Mac, etc. Namely, these computer systems always reload programming help executable on each start from an exterior memory device disk, but here is not programming help case on TI. So, if you have programming help following global or static variableand if you change its value someplace in programming help program to 20 as an example, its preliminary value might be 20 not 10 on programming help next program start!Note that here’s true only for global and static variables. To force reinitializing, you must put explicitely something likeNote, even though, that if programming help program is archived, programming help initial values might be restored every time you run programming help program, as a result of archived applications are reloaded from programming help archive memory to programming help RAM on each start, similarly like programming help packages are reloaded from disks on “ordinary” computers every time in case you start them. if u need any answers regarding programming languages post u r query in blog this is program engineering number 1 blog for questions and solutions concerning programming languagesA static variable remains in memory so long as your program is executing.