[comp.sys.amiga.advocacy] MAC Memory VS AMIGA Memory

NJ_GOKEMEIJE@FANDM.BITNET (06/25/91)

>From:  IN%"rjc@wookumz.gnu.ai.mit.edu"  "Ray Cromwell" 24-JUN-1991 13:15:37.94

[ make takes as much as possible for each application:
  everything under finder
  predefined under multifinder (can be set by user)
  needed so the place of the stck is known (for stack is top-down,
  while heap is from bottom up
  Application cannot get more memory except with TempNewHandle()

  Mac has garbage collection in each block for that particular application.
  (not using the MMU)
]
>  It still seems strange that you have to 'limit' or tell the OS
>the maximum memory your app will need. The only thing that is close

Yes, it is a burden. Imagine running Mathematica: with Virtual Memory
under system7: You either have to declare all of the memory to be for
Mathematic, and than you cannot run anything else, or you have to guess at
what the maximum size is you will need: you have to quit than if you want
larger.

>to this on the Amiga is the need to predefine the stack size
>(this is because 68000,68010, 68020 w/o MMU cannot have dynamic
>stack growth without checking the stack constantly before pushing
>anything on it, this slows down code a lot and places burdens on the
>compiler)

>>-Sho
>>--
>>sho@physics.purdue.edu
>
> INET:rjc@gnu.ai.mit.edu     *   // The opinions expressed here do not      \

Mac stack is limited to 32K

and a question: On the 3000: does the MMU solve Memory Fragmentation?

Nils Gokemeijer (NJ_GOKEMEIJE@FANDM.bitnet)