CS 334

When pass function (or procedure) parameters in stackbased languages, must also pass the equivalent of a closure. In particular must pass the environment in which the function was defined. This is accomplished by passing the appropriate static pointer with the function so that can find nonlocal variables. Usually pass the pair (ep,ip) of environment pointer and instruction pointer as the "closure" of a procedure, when it is passed as a parameter.
Returning functions from functions is harder since defining environment may go away:
program ret; function a(): function (integer): integer; var m: integer; function addm (n: integer): integer; begin return (n + m) end; begin (* a *) m := 5; return addm end; (* a *) procedure b (g: function(integer): integer); begin (* b *) writeln(g(2)) end (* b *) begin (* main *) b(a()) (* note that a() returns a function, which is then passed to b *) end.When b(a()) is called, a() returns a function which depends on the nonlocal variable m, but m has gone away by the time the function is actually applied. Hence languages (like ML) which allow functions to return functions cannot use the simple stack discipline  must keep around activation records even after their associated function or procedure has returned.
Package data structure and its operations in same module  Encapsulation
Data type consists of set of objects plus set of operations on the objects of the type (constructors, inspectors, destructors).
Want mechanism to build new data types (extensible types). Should be treated same way as builtin types. Representation should be hidden from users (abstract). Users only have access via operations provided by the ADT.
Distinguish between specification and implementation.
Method for defining data type and the operations on that type (all in same place). The definitions should not depend on any implementation details. The definitions of the operations should include a specification of their semantics.
Provides userinterface with ADT.
Typically includes
Ex:
pop(push(S,x)) = S,Data + Operations (+ possibly equations) = Algebraif not empty(S) then push(pop(S), top(S)) = S
Method for collecting the implementation details of the type and its operations (in one place), and of restricting access to these details by programs that use the data type. Provides details on all data structures (including some hidden to users) and bodies of all operations.
Note that ADT methodology is orthogonal to topdown design
Three predominant concerns in language design:
Derived from Algol 60. Simulation language. The designers, Nygaard and Dahl, were just awarded the 2001 Turing Award in Computer Science.
Provided notion of class.
class vehicle(weight,maxload); real weight, maxload; begin integer licenseno; (* attributes of class instance *) real load; Boolean procedure tooheavy; tooheavy := weight + load > maxload; load := 0; (* initialization code *) endRefer to objects through references:
ref(vehicle) rv, pickup; rv1: new vehicle(2000,2500); pickup: rv1; (* special assignment via sharing *) pickup.licenseno := 3747; pickup.load := pickup.load +150; if pickup.tooheavy then ...Notice that attributes are available to all users.
Representation not hidden.
Come back to discuss subclasses later when discussing objectoriented languages.
Abstract data type is one that is defined by group of operations (including constants) and (possibly) a set of equations. Set of values only defined indirectly as those values which can be generated by ops, starting from constructors or constants.
E.g., Stack defined by EmptyStack, push, pop, top, and empty operations and equations.
pop(push(fst,rest)) = rest, top(push(fst,rest)) = fst, empty(EmptyStack) = true, empty(push(fst,rest)) = false, etc.Key is representation is hidden.
Packages used to define abstract data types. Package together type, operations (& state) and hide rep. Provides support for parameterized packages (polymorphism)
package <packagename> is  declarations of visible types, variables, constants, and subprograms private  complete definitions of private types and constants end <packagename>; package body <packagename> is  definitions of local variables, types, and subprograms, and complete bodies for  subprograms declared in the specification part above. Code for initialization  and exception handlers end <packagename>;Sample Program:
package VECT_PACKAGE is  declarations only type REAL_VECT is array (INTEGER range <>) of float; function SUM(V: in REAL_VECT) return FLOAT; procedure VECT_PRODUCT(V1,V2 : in REAL_VECT) return FLOAT; function MAX(V: in REAL_VECT) return FLOAT; end VECT_PACKAGE ; package body VECT_PACKAGE is  details of implementation function SUM(V: in REAL_VECT) return FLOAT is TEMP : FLOAT := 0.0; begin for I in V'FIRST..V'LAST loop TEMP:= TEMP + V(I); end loop; return TEMP; end;  definitions of VECT_PRODUCT and MAX subprograms would appear here end VECT_PACKAGE ; with VECT_PACKAGE, TEXT_IO;  used to make separately compiled package visible procedure MAIN is use VECT_PACKAGE, TEXT_IO;  eliminates need for qualifiers package INT_IO is new INTEGER_IO(INTEGER); instantiation of generic packages package REAL_IO is new FLOAT_IO(FLOAT); use INT_IO, REAL_IO; K: INTEGER range 0..99; begin loop GET(K); exit when K<1; declare  start of block A : REAL_VECT(1..K);  provides subscript bounds begin for J in 1..K loop GET(A(J)); PUT(A(J)); end loop; PUT("SUM = "); PUT(SUM(A));  uses package function end;  of block end loop; end MAIN ;SOPHISTICATED (generic) STACK EXAMPLE
Stack represented internally in package (closer to objectoriented than get w/ Modula 2 below)
generic length : Natural := 100;  generic parameters type element is private;  only assignment and tests for = may be done on objects of "private" type  "limited private" is also available. package stack is procedure push (X : in element); procedure pop (X: out element); function empty return boolean; stack_error : exception; end stack; package body stack is space : array (1..length) of element; top : integer range 0..length := 0; procedure push (X : in element) is begin if full() then raise stack_error; else top := top + 1; space(top) := X; end if; end push; procedure pop (X: out element) is begin if empty() then raise stack_error; else X := space(top); top := top  1; end if; end pop; function empty return boolean is begin return (top = 0); end; function full return boolean is begin return (top = length); end; end stack;
Notice: Data structure of stack is entirely hidden from user  there is no object of type stack available to user.
How to use:
package stack1 is new stack(20,integer); package stack2 is new stack(100, character);  Note that this initializes length in both cases to 0 use stack2; stack1.push(5) if not stack1.empty() then stack1.pop(Z); endif; push('z');Note: Package definition is very much like that of a record with procedures allowed as (nonupdateable) fields. E.g.
stack = package push : procedure (X : in element); pop : procedure (X: out element); empty : function return boolean; stack_error : exception; end package;
One of two key ideas behind objectoriented programming.
Can also have package where user can manipulate objects of type stack (external representation) like in Modula2.
Advantage to external rep. is that can define array of stack, etc.
generic length : Natural := 100; type element is private;  generic parameters package stack is type stack is private; procedure make_empty (S : out stack); procedure push (S : in out stack; X : in element); procedure pop (S : in out stack; X: out element); function empty (S : stack) return boolean; stack_error : exception; private type stack is record space : array(1..length) of element; top : integer range 0..length := 0; end record; end stack; package body stack is procedure make_empty (S : out stack); begin S.top := 0; end make_empty ; procedure push (S : in out stack; X : element) is begin if full(S) then raise stack_error; else S.top := S.top + 1; S.space(S.top) := X; end if; end push; procedure pop (S : in out stack; X: out element) is begin if empty(S) then raise stack_error; else X := S.space(S.top); S.top := S.top  1; end if; end pop; function empty(S : in out stack) return boolean is begin return (top = 0); end; function full(S : in out stack) return boolean is begin return (S.top = length); end; end stack;
Biggest problem is exposure of representation of ADT in private part of package spec.
Not available to user, but must recompile if change representation.
Important difference between the two definitions is that in the first, the ADT is accessible only via operations which belong to the object. Can think of the Stack as an "agent". In the second, there is a data type called stack, and the operations act upon the passive data. In the first one must ask the ADT nicely to perform an operation that it knows how to do. In the second, the operation is imposed on the passive data.
Modula 2 is 1980 revision (influenced by Mesa at Xerox PARC) intended to synthesize systems programming with general purpose language supporting modern software engineering.
(operating system for Lilith microcomputer written in Modula 2)
Sample program
DEFINITION MODULE stackMod; IMPORT element FROM elementMod; TYPE stack; PROCEDURE make_empty (VAR S : stack); PROCEDURE push (VAR S : stack; X : element); PROCEDURE pop (VAR S : stack; X: element); PROCEDURE empty (S : stack): BOOLEAN; END stackMod. IMPLEMENTATION MODULE stackMod; TYPE stack = POINTER TO RECORD space : array[1..length] of element; top : INTEGER; END; PROCEDURE make_empty (VAR S : stack); BEGIN S^.top := 0; END make_empty ; ... END stackMod;
Opaque types (those declared without definition in Definition module) must be pointers or take no more space than pointers.
Compare and contrast Modula2 and Ada on supporting abstract data types.
Provides both packaging and hiding of representation
(cvt used to go back and forth btn external abstract type and internal representation).
May have parameterized clusters where specify needed properties of type paramenter. E.g.,
sorted_bag = cluster [t : type] is create, insert, ... where t has lt, equal : proctype (t,t) returns (bool);Abstraction facilities described in Liskov et al. paper in collection on reserve shelf.
Biggest difference from Ada and Modula2 is that cluster is a type. Therefore can create multiple copies. Elements of cluster types are held as implicit references.
Provides for encapsulation and information hiding
Example:
abstype intstack = mkstack of (int list) with exception stackUnderflow val emptyStk = mkstack [] fun push (e:int) (mkstack(s):intstack) = mkstack(e::s) fun pop (mkstack([])) = raise stackUnderflow  pop (mkstack(e::s)) = mkstack(s) fun top (mkstack([])) = raise stackUnderflow  top (mkstack(e::s)) = e fun IsEmpty (mkstack([])) = true  IsEmpty (mkstack(e::s)) = false end;
Generic stacks ADT:
abstype 'a stack = mkstack of ('a list) with exception stackUnderflow val emptyStk : 'a stack = mkstack [] fun push (e:'a) (mkstack(s):'a stack) = mkstack(e::s) fun pop (mkstack([]):'a stack) = raise stackUnderflow  pop (mkstack(e::s):'a stack) = mkstack(s):'a stack fun top (mkstack([]):'a stack) = raise stackUnderflow  top (mkstack(e::s):'a stack) = e fun IsEmpty (mkstack([]):'a stack) = true  IsEmpty (mkstack(e::s):'a stack) = false end;
Cannot get at representation of stack
Reference to mkstack(l) will generate an error message.
Only access through constants and op's.
More sophisticated support through modules, which also support separate compilation. See Ullman's text for more details.