Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!caip!think!mit-eddie!genrad!decvax!tektronix!oresoft!randy
From: randy@oresoft.UUCP
Newsgroups: net.lang.mod2
Subject: Re: Should all opaque types be pointers? No.
Message-ID: <24@oresoft.UUCP>
Date: Wed, 22-Oct-86 22:36:19 EDT
Article-I.D.: oresoft.24
Posted: Wed Oct 22 22:36:19 1986
Date-Received: Thu, 23-Oct-86 18:55:30 EDT
References: <12248635590.12.PATTIS@WARD.CS.WASHINGTON.EDU>
Reply-To: randy@oresoft.UUCP (Randy Bush)
Organization: Oregon Software, Portland OR
Lines: 9

If one allows assignment and in/equality test of opaques, and one allows non-
pointers to be opaques, then a program may become dependent on whether a
particular implementation stuffs an integer into those n bytes, or a pointer.
The other approach would be to disallow comparison or assignment.  The latter
has its proponents among the ADT community.

An aside: Having received two strange phone calls, it should be explained
          that Charles and I know eachother, and no one was actually slurring
          the other's parent.