quote:

---

Array of Pointers
Beginners read all records from the file into memory in one single chunk. This is primitive and has some serious drawbacks. Usually there should be a means to add and remove records, but how to do that with one single memory block?

It is much better to declare an array of pointers to single records:

Type APers = Array[1..1999] of ^TPersRec;

This needs 8kB of memory for the pointers (assumed 4 byte for each pointer).

Whenever you create a new person - record, you simply
New(APers[UU]);
obtaining memory from the heap in small chunks of record size. It needs a little more programming, but it is worth the effort for flexibility.

To access it use:
APers[nn]^.Age := 34;

---

Read(HologenicCoreFile, HologenicCore); // read contents to Cascade
               pMatrix[2, CountCascade]^:= HologenicCore;

Read(HologenicCoreFile, pMatrix[2, CountCascade]^); // read contents to Cascade
 

(9/17/09)
Major re-write to create the majority of 
the matrix memory on the "heap" instead 
of on the stack.

(9/18/09)
Failed to be able to get a derereferenced 
pointer(heap mamory) to work with the read/write 
to File functions.  Seems to need to have a 
variable that is stored on the stack...?

(9/19/09)
Removed button for initializing th ematrix 
from the app interface form.  This prevents 
the redundant creation of new matrix arrays 
on the heap.

(9/19/09)
Put the variables for functionallity control 
into the individual nodes in template.  
This is closer to being able to write the 
actual node-code.  

With dimensions of 16:IO, 32:Cerebellum, 
64:AV, and 64:Cerebrum only using 9GB of 
RAM, I am ready to either start working on 
the multithreading code or on the actual 
Node-code itself.