From Lazarus wiki
Revision as of 19:48, 24 January 2021 by Kai Burghardt (talk | contribs) (create more complete list of frames)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

A frame (frequently also referred to as block) is a language construct grouping a (possibly empty) sequence of statements (or instructions in the case of asm frames).

available types

All frames but repeat  until are terminated by the word end. Frame types are distinguished by their corresponding opening words.

  • Pascal: These frames expect Pascal statements or may contain other frames.
    This frame begins a (possibly empty) sequence of statements. In the context of routine definitions or a program it can delimit a scope.
    This frame surrounds a “catch-all”-alternative as part of a case statement.
    repeat  until
    repeat in conjunction with until is used to surround the loop body of a tail-controlled loop. It is the only frame type not ending with an end.
    This frame allows to temporarily modify the scope lookup routing.
    exception treatment
    If exceptions are supported in the current compiler mode, the following frames are available as well. These frames are in fact “double”-frames: They group two sequences at once. Neither of them can be used independently (e. g. writing finally  end; without a proper try is illegal).
    Use this to install exception handlers.
    Use this to ensure a certain code fragment is executed despite any thrown exceptions.
    unit overhead
    This double-frame designates code being executed when the corresponding unit is loaded or unloaded. Either part of this frame is optional. This frame may also delimit a scope.
    If there is no need for a finalization part, initialization can be replaced by begin.
  • Assembly language: Frames beginning with asm expect assembly language. In pure assembly routines, this kind of frame may delimit a scope, too. Note, you cannot nest other frames in asm frames.


Although not mandatory, it is customary to indent all code surrounded by frame markers by one level.


Some styles add another indentation level for nested or subordinate frame markers per se.

if apples = oranges then

technical background

Frames frequently, but not always, turn up to be (conditional) jmp targets. Some compile-time optimizations require code to be structured in a certain way, frames setting boundaries for that.