| 
|
Topic: value as an object
topics >
computer science >
data >
variables
Topic:
data type as a set of values
Topic:
enumerated data types
Topic:
expression language
Topic:
flag computer
Topic:
immutable files and data
Topic:
named constants and expressions
Topic:
non-primitive values ;;similar
Topic:
object modification
Topic:
primitive data types of a language
Topic:
referential transparency
Topic:
types of object-oriented classes
Topic:
undefined, null, and other signal values
Topic:
value as an abstraction
Summary
Anything can be a value as long as it can be referenced symbolically, and has the same effect no matter how it was produced. Production independence allows uniform interfaces between many different descriptions and orthogonal cross-product expansion. Besides number values such as integers and reals, programming has used many other kinds of objects such as arrays, funnels, types, procedures, and APT's circles and lines. An object could have an executable value and a separate data value. Literal object values have the object as its own meaning. (cbb 5/80)
Subtopic: value vs. object
Quote: programming languages treat atomic data types as values and compound ones as objects; causes unnecessary confusion [»maclBJ12_1982] Quote: computers must represent values as objects since abstractions are not physical [»maclBJ12_1982] Quote: a data object has a name, value, mode (object reference), constant?, scope, and rule [»milgE_1972, OK] Quote: while mathematical values are independent of an encoding, values in an occurrence system or a programming language have constrained codings [»holtAW9_1968]
Subtopic: value semantics -- every object as value
Quote: values are referentially transparent while objects are referentially opaque; i.e., values do not have side effects and identical values may be substituted freely [»taivA4_1993]
Subtopic: value type
Quote: with value semantics, a variable is an object; no pointers, call by reference, or sharing; e.g., applicative programming, APL, and SETL [»cleaJC_1986] Quote: in Red, each object is its own meaning [»backJ8_1978a] Quote: treat large objects the same as small ones; easily created and moved; not treated as a static set of small objects [»pratV1_1983] Quote: the value of an expression can be a variable that holds the value; dereferencing obtains the value [»hansDR5_1978] Quote: use pointer semantics and semantically transparent types to implement value semantics; e.g., SETL
Subtopic: immutable object
Quote: balloon types are value types if only one reference exists and the type is opaque [»almePS6_1997]
Subtopic: types, operations, properties as type
Quote: Cosmos has immutable objects that are transformed into new objects by atomic actions [»walpJ6_1988]
Subtopic: naming values
Quote: types, operations, and properties are themselves objects defined by a type [»zdonSB10_1986] Quote: types, properties, operations, and constraints are objects with the corresponding type [»zdonSB11_1986]
Subtopic: do not name values
Quote: assigning a name to a value is the same as assigning a title to a person [»hehnEC_1977a] Quote: in CLU, every integer is a separate object [»liskBH2_1976, OK] Note: every value has a unique name; it is in certain places at certain times [»cbb_1990, OK] Quote: unlike abstract values, values in an occurrence system always have a time and place [»holtAW9_1968]
Subtopic: leaves as value
Quote: no value shall possess an ID that is distinct from the value per se [»dateCJ_1998]
Subtopic: value as temporary result
Quote: a data object is a named set of data objects; empty sets are references or value; non-empty are attributes [»cbb_1990, OK] Quote: represent data structures by a graph with nodes as entities, edges as selectors, and leaves as values [»earlJ10_1971, OK] Quote: the state, or value, of an object is the value of its members and the objects it references [»stroB_1991] Quote: represent a program as a tree of structure and reference nodes; a reference points to a node (its value); leaves are empty structures (atomic values); nodes have a descriptive label, e.g., "3256" for an atomic value [»edwaJ10_2005]
Subtopic: value as set or array
Quote: objects created by expressions and destroyed when last reference disappears; accessed by uniform reference throughout the system [»ingaDH8_1981a]
Subtopic: exception as value
Quote: a value should allow sets or sequences of entities, e.g., the authors of a book [»borgA1_1985] Quote: think of an array is an immutable string of integers; no different than an integer as a string of bits [»ackeWB_1979] Quote: in data flow languages, an array is a value; changing an element creates a new, slightly different array [»ackeWB_1979] Quote: once communication funnels have names, they should be treated as values [»huntJG1_1979]
Quote: Galaxy exceptions are the targets of goto's; can be assigned to variables, e.g., for jumps to outer functions [»beet5_1989]
Group: variables (10 topics, 128 quotes)
Topic: data type as a set of values (20 items)
Topic: enumerated data types (17 items)
Topic: expression language (14 items)
Topic: flag computer (2 items)
Topic: immutable files and data (59 items)
Topic: named constants and expressions (21 items)
Topic: non-primitive values ;;similar (11 items)
Topic: object modification (10 items)
Topic: primitive data types of a language (31 items)
Topic: referential transparency (26 items)
Topic: types of object-oriented classes (18 items)
Topic: undefined, null, and other signal values (34 items)
Topic: value as an abstraction
(25 items)