#Big static array in BXP
03-Nov-94 02:32:51
Sb: #132833-#Big static array in BXP
Fm: Ken Mascaro, Xing T 70703,3505
To: Gus Grubba 70673,1605
I want to "explore" the limits. Maybe I should have been a Captain of
the Enterprise.
Why do I need a 2mb static array. Well what if I have a BXP which
wants to process "optimally" by having an array which does not need
to be "alloc"ed and "free"ed for each frame. As the BXP is now
implemented, you get a terminate after EACH frame, which means that
you "may" be unloaded since 3DS/IPAS expects you to free all dynamic
objects on receipt of the Terminate. BUT if I put my big array in a
static, I don't care, since the static memory is automatically "free"
when the BXP module is unloaded. Same amount of memory, but simply a
different method of management which obtains an "optimization" not
otherwise acceptable. Now further suppose that the array for which I
speak is in need of being dynamically initiallized only once when the
BXP module is first run, and thereafter wants to retain the
initiallized data from frame to frame. Can you now see a
"situation" where the use of malloc and re-initiallization prior to
each frame would simply be non-optimal.