Topic: implementation of Thesa data objects

topics > computer science > programming > Group: Thesa programming system

binding of names to objects
data types in Thesa
named constants and expressions
object-oriented objects
Thesa data model
Thesa data structures


Constants or expressions have many possible meanings. By naming constants and expressions the programmer specifies a particular meaning for what would have been a mystery number. Since literals stand for a value, they are equivalent to functions without arguments. (cbb 5/80)
Subtopic: data-driven design up

Topic: data-driven design
Quote: programming by data organization: decide on modules and partition program to hide data in modules [»stroB5_1989]

Quote: most existing databases for real-world systems require non-deletion; e.g., financial accounts [»copeG3_1980]

Subtopic: environment up

Topic: system-defined variables
Quote: Algol68 includes environment enquiries for determining implementation parameters [»vanwA_1969]
Quote: Icon provides system variables for the current state of the scanning function [»grisRE4_1979, OK]

Subtopic: name binding up

Topic: binding of names to objects
Quote: use early binding for performance and late binding when early binding becomes invalid [»oppeDC7_1983]
Quote: define macros for anything that may change; allows delayed binding for implementation of the macros [»browPJ_1974]
Quote: dynamic binding of names to addresses allows graceful adaptation to changes [»oppeDC7_1983]
Quote: a user profile contains names of mail and file servers instead of addresses; allows relocation of servers [»oppeDC7_1983]
Quote: in Euclid, can bind an identifier to part of an existing variable; e.g., bind var X to A[5] [»veneT3_1978]
Quote: data independence means maintaining data/file structures separately from programs; e.g., the size of the ZIP code field [»morgH_1980]

Subtopic: data type up

Group: type declaration
Topic: type checking by trademark

Subtopic: memory management up

Topic: memory management by garbage collection
Quote: big gain in Cedar was garbage collection; simplifies interfaces, e.g., functions which return strings [»donaJ7_1985a]
Quote: garbage collection increases flexibility of argument passing to procedure parameters and variables [»swinDC7_1985]
Quote: garbage collection allows resources to be easily shared
Quote: Cedar reference variables can be freely replicated and discarded due to garbage collection [»swinDC7_1985]
Quote: objects created by expressions and destroyed when last reference disappears; accessed by uniform reference throughout the system [»ingaDH8_1981a]
Quote: a Cedar rope is an immutable, garbage-collected, text string; widely used in all system levels [»swinDC7_1985]
Quote: Cedar ropes are immutable, garbage collected, strings; same as a value [»teitW3_1985]
Quote: with explicit storage allocation, programmer must avoid dangling references and storage leaks [»swinDC7_1985]
Quote: without garbage collection, objects must be owned; who releases a string that is queued for printing? [»swinDC7_1985]
Quote: drawback of garbage-collection is that its overhead appears only during long runs [»wolfW9_1989]
Quote: to be object-oriented, a computer must provide automatic storage management [»ingaDH8_1981a]

Related Topics up

Topic: binding of names to objects (19 items)
Topic: data types in Thesa (92 items)
Topic: named constants and expressions (21 items)
Topic: object-oriented objects (39 items)
Topic: Thesa data model (58 items)
Topic: Thesa data structures
(59 items)

Updated barberCB 7/04
Copyright © 2002-2008 by C. Bradford Barber. All rights reserved.
Thesa is a trademark of C. Bradford Barber.