Retro video games delivered to your door every month!
Click above to get retro games delivered to your door ever month!
X-Hacker.org- The Guide To Clipper - <b>memory allocation</b> http://www.X-Hacker.org [<<Previous Entry] [^^Up^^] [Next Entry>>] [Menu] [About The Guide]
Memory Allocation


   If you do not use SET CLIPPER to alter the memory allocation, the
   Clipper program automatically allocates the available memory in the
   following sequence:

   . The executable load module is loaded into memory above DOS.

   . 24K bytes are reserved for a free memory pool.

   . Of the remaining available memory, 20 percent is allocated for
     memory variables (44K maximum).

   . Of the memory remaining, 33 percent is allocated for RUN commands
     and index buffers (16K minimum).

   . The remaining available memory is added to the previously reserved
     24K bytes, and allocated to the "free memory pool" to be used for
     program processing.  Specific uses of "free memory pool" include
     storage of character variables, arrays, and transient copies of
     database records from open database files.

   Accordingly, the absolute minimum memory required above DOS to run
   your application is the load module size, 24K for the free pool, 16K
   for index buffers, plus the allocation for memory variables.

   If Expanded Memory is present, the Clipper program automatically
   makes use of it allocating up to one megabyte, if available, for
   index buffers.  The allocation described in step 4 above will only be
   used for RUN commands.  If Expanded Memory is present, the Clipper
   program requires a minimum of 16K bytes of the Expanded Memory.


Online resources provided by: http://www.X-Hacker.org --- NG 2 HTML conversion by Dave Pearson