Some parts of an activation record have the same size for all procedures Space for bookkeeping information Other parts of an activation record may remain fixed for each individual procedure Space for arguments and local data Some parts of activation record may be allocated automatically on procedure calls Storing the return address Other parts of activation record may need to be allocated explicitly by instructions generated by the compiler Local temporary space Depending on the language activation records may be allocated in different areas Fortran77 in the static area C and pascal in the stack area referred to as stack frames LISP in the heap area• Some parts of an activation record have the same size for all procedures – Space for bookkeeping information • Other parts of an activation record may remain fixed for each individual procedure – Space for arguments and local data • Some parts of activation record may be allocated automatically on procedure calls: – Storing the return address • Other parts of activation record may need to be allocated explicitly by instructions generated by the compiler: – Local temporary space • Depending on the language, activation records may be allocated in different areas: – Fortran77 in the static area; – C and Pascal in the stack area; referred to as stack frames – LISP in the heap area