Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!nike!ucbcad!ucbvax!WARD.CS.WASHINGTON.EDU!PATTIS
From: PATTIS@WARD.CS.WASHINGTON.EDU (Richard Pattis)
Newsgroups: net.lang.mod2
Subject: Opaque Types: A Misunderstanding
Message-ID: <12249380101.10.PATTIS@WARD.CS.WASHINGTON.EDU>
Date: Fri, 24-Oct-86 12:14:34 EDT
Article-I.D.: WARD.12249380101.10.PATTIS
Posted: Fri Oct 24 12:14:34 1986
Date-Received: Sat, 25-Oct-86 07:12:50 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 10

Vincent Manis misunderstands what I want.  I realize that for various reasons
one cannot allow opaque types to be represented by arbitrarily large structures
like arrays and records.  In fact, when I teach array implementations of Tables
I do it exactly as he says, with a pointer.  It is the "cursor" opaque type
that I am worried about; here I would like exactly what he describes - opaque
types that are as big as the biggest "one-word" entity.  I don't believe that
this would be too wasteful of storage.

Rich
-------