OnlineWoerterBuecher.de
Internes

Lexikon


activation record


(Or "data frame", "stack frame") A data structure containing the variables belonging to one particular scope (e.g. a procedure body), as well as links to other activation records. Activation records are usually created (on the stack) on entry to a block and destroyed on exit. If a procedure or function may be returned as a result, stored in a variable and used in an outer scope then its activation record must be stored in a heap so that its variables still exist when it is used. Variables in the current scope are accessed via the frame pointer which points to the current activation record. Variables in an outer scope are accessed by following chains of links between activation records. There are two kinds of link - the static link and the dynamic link. (1995-03-07)

In addition suitable contents:
[ = ] [ ai ] [ al ] [ am ] [ an ] [ ar ] [ arc ] [ as ] [ at ] [ b ] [ be ] [ block ] [ bo ] [ by ] [ cc ] [ ch ] [ chain ] [ ck ] [ co ] [ com ] [ compiler ] [ con ] [ cr ] [ cu ] [ current ] [ data ] [ data frame ] [ data structure ] [ de ] [ du ] [ dynamic link ] [ ec ] [ ed ] [ edu ] [ ee ] [ er ] [ es ] [ et ] [ fi ] [ file ] [ fo ] [ fr ] [ frame ] [ frame pointer ] [ function ] [ gi ] [ h ] [ hat ] [ heap ] [ hr ] [ id ] [ il ] [ in ] [ int ] [ io ] [ is ] [ it ] [ ki ] [ la ] [ Lex ] [ li ] [ link ] [ links ] [ lt ] [ ly ] [ ma ] [ mo ] [ mod ] [ module ] [ mp ] [ mu ] [ na ] [ nc ] [ ne ] [ ng ] [ ni ] [ ns ] [ O ] [ om ] [ op ] [ pa ] [ pe ] [ ph ] [ point ] [ pointer ] [ pr ] [ procedure ] [ query ] [ rc ] [ re ] [ record ] [ records ] [ ro ] [ ru ] [ sc ] [ scope ] [ se ] [ so ] [ st ] [ stack ] [ stack frame ] [ static link ] [ store ] [ struct ] [ su ] [ T ] [ th ] [ to ] [ tr ] [ tw ] [ ua ] [ us ] [ V ] [ va ] [ var ] [ variable ] [ vi ] [ win ] [ ye ]






Go Back ]

Free On-line Dictionary of Computing

Copyright © by OnlineWoerterBuecher.de - (7072 Reads)

All logos and trademarks in this site are property of their respective owner.

Page Generation in 0.1077 Seconds, with 17 Database-Queries
Zurück zur Startseite