77 lines
1.4 KiB
HolyC
Executable File
77 lines
1.4 KiB
HolyC
Executable File
//Demonstrates dynamic initialization of vars.
|
||
//Static vars are, essentually, global vars.
|
||
|
||
class Test
|
||
{
|
||
I32 time;
|
||
U8 name[8];
|
||
};
|
||
|
||
Test g1[]={
|
||
{10,"Name1"},
|
||
{(tS%10.0)*100,"Name2"}, //Dynamic initialization
|
||
{30,"Name3"}
|
||
};
|
||
|
||
D(g1,sizeof(g1));
|
||
"Time 1:%d\n",g1[1].time;
|
||
|
||
U0 Main1()
|
||
{
|
||
static Test s1[]={
|
||
{10,"Static1"},
|
||
{(tS%10.0)*100,"Static2"}, //Dynamic initialization
|
||
{30,"Static3"}
|
||
};
|
||
D(s1,sizeof(s1));
|
||
"Time 2:%d\n",s1[1].time;
|
||
}
|
||
|
||
Main1;
|
||
|
||
/*Now, we'll use the data heap glbl option
|
||
to force global vars onto the data heap.
|
||
|
||
You can turn the data heap flag
|
||
on and off within your programs, leaving
|
||
ones which need initialization on the code heap.
|
||
|
||
You can't dynamically initialize data heap
|
||
glbls--they are consts. This might be a silly
|
||
point, but might res in odd differences, perhaps
|
||
from the order things are evaluated.
|
||
|
||
Data heap glbls are good for AOT modules
|
||
because they don't take-up room in the .BIN.Z file.
|
||
*/
|
||
|
||
#ifjit
|
||
#exe {Option(OPTf_GLBLS_ON_DATA_HEAP,ON);};
|
||
|
||
Test g2[]={
|
||
{10,"name1"},
|
||
{(tS%10.0)*100,"name2"}, //No dynamic initialization--cvted to const
|
||
{30,"name3"}
|
||
};
|
||
|
||
D(g2,sizeof(g2));
|
||
"Time 3:%d\n",g2[1].time;
|
||
|
||
U0 Main2()
|
||
{
|
||
static Test s2[]={
|
||
{10,"static1"},
|
||
{(tS%10.0)*100,"static2"}, //No dynamic initialization--cvted to const
|
||
{30,"static3"}
|
||
};
|
||
D(s2,sizeof(s2));
|
||
"Time 4:%d\n",s2[1].time;
|
||
}
|
||
|
||
Main2;
|
||
|
||
#exe {Option(OPTf_GLBLS_ON_DATA_HEAP,ON);};
|
||
#endif
|
||
|
||
'\n';
|